Change Tracker v8.2.0 introduces native integration with Netwrix Activity Monitor for richer Windows file change attribution, generic OIDC single sign-on support for any OIDC-compliant identity provider, and interactive OpenAPI 3.0 API documentation. This release also ships device registration name prefix customization, new CIS benchmarks for Apache HTTP Server, HIPAA compliance templates for modern Windows Server versions, and a range of Hub UI and reliability improvements.
Want the full details? Click the link below!
What’s Changed in Netwrix Change Tracker 8.2.0
Activity Monitor Integration
The Gen7 Windows Agent now supports the Netwrix Activity Monitor as an alternative data source for identifying who made file changes. Instead of relying solely on the legacy kernel mini-filter driver, administrators can configure the agent to read change attribution (user identity, process name, and operation type) from the Activity Monitor’s log files.
The Activity Monitor is installed alongside the agent via the new MSI-based installer, with configuration mapped automatically from Change Tracker’s file monitoring policies. For setup instructions, see the Activity Monitor integration guide.
OIDC Authentication (SSO)
Change Tracker now supports generic OpenID Connect (OIDC) authentication, allowing customers to sign in using any OIDC-compliant identity provider. Administrators can configure the provider via Hub settings. A configurable “Sign In with SSO” button appears on the login page when OIDC is enabled. For configuration details, see the OIDC System Settings guide.
Device Registration Name Prefix Customization
Change Tracker v8.2.0 introduces two complementary prefix controls for device registration and discovery. A new Device Name Prefix field in the ESXi/vCenter discovery dialog lets administrators customize the prefix applied to discovered host names, replacing the previous hardcoded “VM Host” value so that devices follow organizational naming conventions from the moment they are discovered.
A new Custom Group Name Prefix setting also adds a validation gate to the general device registration process: when configured, a device is only registered into groups whose names begin with the specified prefix, and any device whose registration script returns no matching group is held in New Devices with an audit event identifying the misconfiguration.
For details, see ESXi/vCenter Discovery and Custom Group Name Prefix.
API Documentation
The Hub API now ships with an OpenAPI 3.0 specification and interactive documentation, available via the API Reference. Developers and integrators can browse all available endpoints, view request/response schemas, and test API calls directly.
Bug Fixes and Miscellaneous Updates
Reports & Benchmarks
- Added CIS Benchmarks for Apache HTTP Server 2.2 and 2.4 (#2515)
- Added HIPAA compliance templates for Windows Server 2019, 2022, and 2025 (#2508)
Hub - v8.2.0
Improvements
- Added quick-access links to documentation, product news, and support from the navigation bar (#2620)
- Added configurable group name filter for agent auto-registration group assignment (#2634)
- Improved mobile navigation, info panel styling, and dashboard widget appearance (#2621)
- Reduced log noise from expected agent misconfiguration states on SaaS deployments (#2613)
- Added logged-in username to the profile dropdown menu (#2561)
Bug Fixes
- Fixed blank page displayed after login instead of the Dashboard (#2653)
- Fixed logo overlap when resizing the browser window in SaaS (#2628)
- Fixed index out-of-range error when generating compliance reports for large Windows device sets (#2611)
- Fixed OIDC provisioning overwriting the system admin account when the IdP username matched a reserved account name (#2610)
- Fixed FAST Cloud connectivity failure when outbound traffic is routed through a proxy on Windows Server (#2590)
- Fixed Network Port Tracker missing from the Tracker dropdown in Planned Change Rule Sets (#2565)
- Fixed scheduled reports running indefinitely when configured with No Repeat (#1619)
Gen7 Agent - v7.3.0
Linux
Bug Fixes
- Fixed Linux Agent update task reporting success when the package install command failed (#2567)
No changes in this release
- Windows
- macOS
Express Agent - v2.1.2
No changes in this release.
Agentless
No changes in this release.
For a full list of supported platforms and packages, see the Support Matrix.
Agent compatibility: Hub v8.2.0 is backward-compatible with existing Gen7 Agent v7.x and Express Agent v2.x installations. You may upgrade the Hub independently and update Gen7 Agent and Express Agent only if the platform-specific fixes in this release are relevant to your environment.
Need help with this update?
There are many different ways to get help with our products!
| Situation | Action |
|---|---|
| If you feel the product is broken and not working as intended… | Contact Support |
| If you have a question you’d like to ask other experts… | Create a discussion in the community: Change Tracker > Discussions & Questions |
| If you have a feature request… | Let our product team know directly: Change Tracker > Ideas |
| If you have something cool to show… | Show everyone what you built: Change Tracker > Show & Tell |
What are your thoughts?
We are always happy to hear from our users on what you like, and what you hope to see in the future. Please, share your thoughts below!
