Release notes - 3.6.0

Key objectives

As we continue to strive to make vulnerability management easy, this versions key objective was to improve the usability of Nanitor.

The main features in that aspect are a simplified asset lifecycle, a complete redesign of our filtering mechanism in the UI, the ability to have agents update automatically after a new version of Nanitor is released and an updated collector page to give a better overview of what the collectors are doing.

New Features

NAN-2599: Filter redesign

We've redesigned the filter experience to improve usability and simplify the filtering process. Previously, filters were located in a sidebar, but now they are placed at the top of pages where filtering is available in a new filter bar.

Open

In addition, filters have been categorized to simplify the view of the filter bar with the most used filters always being present in the bar but others are now available by clicking the 'More' button. Previously, all filters were visible all the time in the sidebar, which could be overwhelming on pages with a lot of filters. With this new design, users can easily find the filters they need and quickly apply them to refine their search results.

Open

An issue we had before was that if a user wanted to edit multiple filters they had to wait for a new data request every time a single filter was changed. This could take a lot of time, especially for larger customers.

The functionality has now been changed by adding an 'Apply' button to make the filters take effect. Makes it much easier to apply multiple filters to a page.

This update improves the overall user experience and makes filtering more intuitive and user-friendly.

NAN-2653: Agent auto upgrade

Related tickets: NAN-2654

A new agent auto update feature allows users to opt-in to automatically update their agents to the latest version when it becomes available. The next time the agent performs a check-in to the server after a newer version has been released, the server will notify the agent to try to update itself. This should happen within the hour after a new version is released for active agents.

This feature can be configured with a setting in the general settings tab under organization management settings.

With this new feature, users no longer need to manually update their agents, ensuring that they always have access to the latest features and improvements.

NAN-2832: Simplified asset states

Related tickets: NAN-2833, NAN-2834, NAN-2839

The asset state lifecycle has been simplified. Previously, there were 9 different states for an asset, but we've removed 3 to make the asset lifecycle simpler.

The removed states are:

• New

  • Instead a 'new' badge is displayed next to the asset state for 24 hours after an asset is added to Nanitor.

• Ghost

  • This state meant that a manually archived device was checking in again, instead of being its own state this is now indicated with a warning triangle symbol next to the assets state

• Stale

  • This state meant that a device is being discovered through network discovery by other assets but not checking in itself. Instead of being its own state this is now also indicated with the warning triangle symbol next to the assets state.

The Undiscovered state has also been renamed to Unmonitored and Decommissioned/Expired have been unified to Archived.

NAN-2803: Collector UI improvements

Related tickets: NAN-2804

A problem users had before with the collector UI was that it did not display enough information about what the collectors were doing and in what state they are.

This has been rectified in this version by adding a couple of additional columns to the collectors table.

The new columns are:

• Last collection

  • If the collector is not connected this column will say 'Not connected' with information about the last collection if it has performed a previous collection.

  • If the collector is connected but not currently collecting this column will say 'Idle' along with the last collection results.

  • If the collector is currently collecting from an asset this column will say 'Collecting' along with information on the current collection (started on, number of assets collected)

• Next collection

  • Displays the date of next collection.

For older collectors these columns will say ‘Unknown'.

NAN-2342: Issue endpoint added to Nanitor system api

Users fetching information from our system api can now utilize a new issue endpoint ,/issues, to fetch information about issues in the system.

To get more information about how the endpoint works and what parameters are available please refer to the api’s swagger documentation.

Improvements

Benchmarks

These benchmarks have been upgraded.

For more information on supported benchmarks visit the documentation of our benchmarks space.

Fixes

NAN-2558 Fixed health dashboard timeout error

NAN-2261 Fixed collector UI sending duplicate requests

NAN-2277 Fixed setting collected asset’s port to blank not working

NAN-2595 Fixed missing activity log message mappings

NAN-2644 Fixed customized table configurations not persisting after a page reload

NAN-2735 Fixed label counts in patch status report not matching with actual results

NAN-2735 Fixed error when removing multiple issue exceptions

NAN-2766 Fixed MacOS 13 benchmark http server disabled check

NAN-2794 Fixed incorrect Firefox version being reported

NAN-2823 Fixed issue trend metrics report page server error

NAN-2853 Fixed collector version sometimes not updating in the UI after a collector is updated

NAN-2880 Fixed hostname and OS filtering not working on assets table in affected assets tab

NAN-2882 Fixed asset duplication bug

NAN-2907 Removed duplicated filters

NAN-2915 Fixed benchmark filter on the technical policy changes report page

NAN-2917 Fixed zero archive days for manual archival rules bug

NAN-2919 Fixed not found error in network tab on the asset detail page

NAN-2921 Fixed guest users not being able to access benchmark rule list pages

NAN-2927 Fixed broken links in notification emails

NAN-2831 Fixed broken access to version information page