Release notes

• Version: 6.5.0
• Build number: 14009
• Release date: 2025-09-19 (general availability)
• Server version: nanitor-6.5.0.14009-17262-master
• Agent version: nanitor-6.5.0.14009-17262-master
• Collector version: nanitor-6.5.0.14009-17262-master

Welcome to Nanitor v6.5.0! 🚀

This release introduces powerful new integrations, expands our vulnerability detection capabilities, and delivers a host of user-requested improvements to streamline your security operations.

We're excited to announce our new native NinjaOne integration, designed to simplify asset management and synchronization for MSPs. We've also added a Vanta integration to help you automate user compliance. To deepen our security coverage, Nanitor now detects vulnerabilities in Python packages installed via pip on Linux systems.

Beyond these highlights, you'll find significant enhancements to our Public API, new asset visibility controls, and numerous quality-of-life improvements that make managing your security posture faster and more intuitive.

Highlights

Integrate and Sync with NinjaOne

We're thrilled to introduce a native integration with NinjaOne, a leading RMM platform. This integration is designed to streamline workflows for Managed Service Providers (MSPs) and organizations that use both Nanitor and NinjaOne, enabling seamless asset synchronization and management.

Once configured, Nanitor can automatically sync and link your NinjaOne devices, ensuring your asset inventory is always up-to-date. Assets managed in NinjaOne will appear in Nanitor with the source type "NinjaOne," providing clear visibility into your entire device landscape.

Key benefits

• Unified Asset View: See all your NinjaOne-managed devices directly within the Nanitor asset inventory, simplifying management and reporting.
• Automated Asset Sync: Set up the integration once and let Nanitor automatically sync your device inventory from NinjaOne.
• Secure Authentication: The integration uses a secure and easy-to-configure OAuth2 flow to connect to your NinjaOne instance.
• Simplified MSP Workflows: Reduce manual effort and ensure consistency by managing your entire asset landscape from a single pane of glass.

How to use it

To get started, you first need to create the Nanitor app in your NinjaOne account to obtain API credentials.

Once you have your credentials, follow these steps in Nanitor:

1. Navigate to Organization Management → Integrations and select the NinjaOne card.
2. Authorize the integration by entering your NinjaOne Client ID, Secret, and Region.
3. Next, click "Connect NinjaOne account" and sign in through the secure pop-up window to grant access.
4. Enable asset discovery to begin syncing devices from NinjaOne into your Nanitor inventory. You can also trigger a manual sync at any time.

Once your assets appear in the inventory, the next step is to deploy the Nanitor Agent to them. This will provide deep visibility into their security status, including vulnerabilities and misconfigurations. To do this, follow the detailed steps in our Seamless Ninja RMM and Nanitor CTEM Integration guide.

Expanded Linux Vulnerability Coverage for Python Packages

To provide deeper visibility into potential software supply chain risks, Nanitor now discovers and inventories Python packages installed via pip on Linux systems. This enhancement closes a critical visibility gap, as packages installed outside the native OS package manager were previously untracked.

Once inventoried, Nanitor automatically cross-references these packages against our vulnerability database, which now includes advisories from the GitHub Security Advisory (GHSA) database. When a vulnerability is found, a new issue is created with detailed forensics, including the package name, version, and the specific GHSA advisory it matched.

Key benefits

• Complete Software Visibility: Gain a full picture of all software on your Linux assets, including manually installed Python libraries.
• Identify Hidden Risks: Uncover vulnerabilities in third-party Python packages that were previously invisible to system-level scans.
• Actionable Forensics: Quickly understand and remediate vulnerabilities with detailed forensics that link directly to the relevant GHSA advisory.

How to use it

This feature is enabled automatically. The Nanitor agent on your Linux devices will begin collecting pip package information during its next software inventory scan.

1. View discovered packages in the Software Inventory. You can filter the list by the "Package" software type to see only pip-installed packages.
2. Vulnerabilities found in these packages will appear as issues in Nanitor just like any other software vulnerability.
3. The Issue Detail page for these vulnerabilities will now include forensics showing the package details and the matched GHSA advisory.

Vanta Integration for Automated User Compliance

For organizations using Vanta to manage compliance, Nanitor now offers a direct integration to automate user synchronization. This integration helps you meet compliance requirements by ensuring that your Vanta instance has an up-to-date list of all Nanitor users, along with their roles and MFA status.

Key benefits

• Automate Compliance: Eliminate the manual work of tracking and providing evidence for user access controls.
• Improve Visibility: Give your compliance team a clear, auditable record of all Nanitor users, their roles, and MFA status.
• Easy Setup: Connect to Vanta in just a few clicks using a secure, token-based authentication method.

How to use it

1. Go to Organization Management → Integrations and select the Vanta tab.
2. Enter your Client ID, Client Secret, and User account resource ID to establish the connection.
3. Once configured, Nanitor will periodically sync your active Nanitor user list to Vanta.

Note: This integration only pushes Nanitor user account data into Vanta. No data is imported from Vanta into Nanitor.

Major Public API Enhancements

We've significantly expanded our Public API to give you more programmatic access to your Nanitor data. This release introduces a host of new endpoints and filtering capabilities to support deeper integrations and automated workflows.

Key Additions:

• Software Inventory Endpoints: You can now query your entire software inventory via the API. New endpoints allow you to list all software titles, versions, and publishers, as well as find which assets have a specific piece of software installed.
• Network List Endpoint: A new /networks endpoint provides a comprehensive list of all discovered networks and subnets, including details like asset count, labels, and rogue asset count.
• Query Issues by CVE: The /issues endpoint now supports filtering by a specific CVE identifier (cve_id), allowing you to directly query for assets affected by a particular vulnerability.
• Open Ports on Assets: You can now retrieve a list of open ports for an asset using the expand=open_ports parameter on the asset list endpoint.
• Filter Assets by Activity State: The /assets endpoint now supports filtering by activity_state, making it easy to find assets that are active, archived, or pending archival confirmation.

For detailed information on these and other endpoints, please see the official Nanitor API Documentation, including the new sections for Software and Networks.

Improvements

• Globally Enforce Two-Factor Authentication (2FA): System administrators can now enforce 2FA for all users with local accounts across the entire Nanitor instance. When enabled, users will be required to set up 2FA upon their next login, significantly strengthening account security.
• Updated Microsoft Intune Benchmark for Windows 11: The benchmark for CIS Microsoft Intune for Windows 11 has been updated to the latest version (v4.0.0), ensuring your Intune-managed devices are assessed against current best practices.
• View Resolved and Excluded Assets in Issue Details: The Assets tab on the Issue Detail page has been enhanced to give you a complete picture of remediation progress. A new "Resolution status" filter lets you view not only Active issues but also Resolved and Excluded ones. New columns show when an issue was resolved or excluded, and by whom, providing a full audit trail.
• Export Assets from Project and Issue Views: You can now export the list of affected assets directly from the Assets tab within any Project or Issue detail view. The exported CSV respects your active filters, making it easy to generate targeted lists for remediation teams.
• Export Custom Fields with Asset Inventory: The main asset inventory CSV export now includes all your configured custom fields. Each custom field appears as its own column, allowing you to export a complete CMDB-like view of your asset data.
• Redesigned Issue Tracker "Count" Mode: The Issue Tracker widget on the Global Dashboard has been improved. Count mode now shows a true summary with three tiles: Total Affected Issues, Total Affected Orgs, and Total Affected Assets. In Breakdown mode, you can now toggle a switch to hide empty organizations, decluttering the view and helping you focus on what matters.
• Enhanced Network Discovery Recheck Capabilities: We've made several improvements to Network Discovery. You can now request a recheck specifically for network discovery on an asset. Rechecks are now automatically triggered when network discovery is enabled for an organization or subnet, ensuring you get data faster. The asset detail page now provides detailed status markers on when discovery data was last received and processed.
• Upgraded AI Remediation Suggestions to GPT-5: Our AI-powered remediation suggestions are now generated using OpenAI's GPT-5 model. This upgrade provides more accurate, detailed, and actionable remediation advice.
• Code Signing for Active Directory Audit Scripts: To enhance security and prevent false positives from security tools, the PowerShell scripts used by the Nanitor Agent for Active Directory audits are now code-signed.
• Improved Filtering for Empty Custom Fields: Labeling rules and asset filters that check for an empty custom field now correctly handle fields inherited from a parent organization.
• Enhanced Security for Integration Secret Fields: Client secret fields on integration pages (like Jira, NinjaOne, and Vanta) are now masked by default, with an option to toggle visibility.
• Reduced Log Noise for Product Aliases: Harmless warnings related to product alias compilation during sync operations have been changed from "Warning" to "Debug" level to reduce unnecessary log noise.
• Performance and Stability: This release includes numerous backend optimizations to improve the performance and reliability of database queries, issue list maintenance, dashboard data generation, and API responses.

Bug Fixes

• Asset Inventory: Fixed a bug where archiving multiple assets at once from the asset list would only archive one of the selected assets.
• Activity Log: Ensured that a separate device_archived event is created in the activity log for each asset when multiple assets are archived simultaneously. A similar fix was applied for decommissioning events.
• Activity Log: Fixed an issue where the "Imported asset" event was not correctly associated with the asset, causing it not to appear in the asset's activity log tab.
• Benchmarks: Corrected the logic for auto-assigning the Apache Tomcat benchmark to prevent it from being assigned to devices where a Tomcat service was not actually running.
• Benchmarks: Fixed an error in the macOS benchmark script for rule 2.10.5 (macOS_show_password_hints.sh) that occurred due to a syntax error.
• Custom Fields: Corrected an issue where selecting multiple options in a "Select List (multiple choices)" custom field would only save the first selected value.
• Custom Fields: Resolved a bug in the asset inventory where filtering by a multi-select custom field would return an error if more than one option was selected.
• Dashboards & Reporting: Corrected an issue where the PII health score highlights on the dashboard could display confusing or illogical information.
• Identity Issues: Fixed a false positive in Active Directory monitoring where the built-in krbtgt account was incorrectly flagged for the issue "Identity is not protected against delegation".
• Issue List: Corrected the aggregated asset counts in the issue list's split-panel to ensure the num_issues field accurately reflects only the selected issues.
• Labeling Rules: Resolved a UI bug where users could not change the selected custom field when editing a label rule condition for "Custom field is empty".
• Network Discovery: Fixed a bug that caused Network Discovery to be unreliable in multi-tenant environments by ensuring data from different organizations is processed correctly.
• UI & UX: Addressed an issue where modal dialog backdrops could get stuck on the screen after navigating away from a page.

Known Limitations & Practical Information

In the spirit of transparency, this section lists known limitations and other practical information we are aware of in this release. Some of these items describe the current behavior of the system, while others are planned to be addressed in a future update. We recommend reviewing this list before filing a support ticket, though we are always happy to assist if you encounter any related problems.

Delay in Issue Progress Updates

• Description: As part of a significant performance optimization for issue list calculations, data related to resolved issues is now aggregated in a background task that runs every twelve hours.
• Impact: The "Progress" percentage for issues in the Issue List will now only update approximately every twelve hours. Data for currently active, unresolved issues remains real-time. (TICKETS: NAN-5284)
• Status: This trade-off was made to ensure the overall performance and responsiveness of the Issue List, especially in large environments.

AI Remediation Generation Time

• Description: Our AI-powered remediation advice has been upgraded to GPT-5 for higher quality suggestions. This more advanced model can sometimes take longer to generate a response.
• Impact: You may notice that clicking to generate AI Remediation Insights takes a few seconds longer than in previous versions. We have increased the timeout to accommodate this. (TICKETS: NAN-5407)
• Status: This is expected behavior due to the more complex model. We believe the significant improvement in the quality of the advice justifies the modest increase in generation time.

We welcome your feedback on these new capabilities. If you have thoughts on the improved AI remediation quality or other features, please don't hesitate to reach out to our support team.

Thank you for using Nanitor! For more in-depth documentation, check out the Nanitor User Guide or visit our Knowledgebase.