Tenable Vulnerability Management 2024 Release Notes
These release notes are listed in reverse chronological order.
This update enables custom role users to access Tenable Vulnerability Management Scan Management. It also enables administrators to leverage custom roles to manage access to Tenable Vulnerability Management Scan Management tasks, such as viewing and managing scans, exclusions, scan templates, managed credentials and target groups.
The Sensor Proxy 1.0.9 release includes the following updates:
Added minor features to support the Tenable Core + Sensor Proxy early access release.
Updated OpenSSL to version 3.0.12.
Updated openresty to version 126.96.36.199.
For more information about Sensor Proxy, see the Sensor Proxy User Guide.
Tenable is pleased to announce the redesigned License Information page, which streamlines how you view cloud license details on the Tenable platform.
On the License Information page, you can:
In Tenable One only, use visual overviews by product or time period to spot trends.
View license information for all Tenable products in your cloud container.
View license usage snapshots, such as total assets or available assets.
View license resource counts for all your cloud products.
The License Information page is available to all users. To learn more, see License Information.
Note: This beta feature is available to a limited pilot group and will be rolled out to a wider audience in the coming months.
Tenable has added the new Info-level Reporting scan setting to Nessus Agent vulnerability scan templates. Configuring this setting can help minimize your scan processing times by decreasing the number of unchanged Info-severity findings that Tenable Vulnerability Management processes after every agent scan.
Tenable's redesigned License Information page now supports the new version of Tenable Cloud Security.
If your organization has upgraded to this version, the following new fields appear under Cloud Security:
Compute — Non function-like cloud resources, such as virtual machines or cloud storage.
Serverless — Function-like cloud resources such as AWS Lambda or Azure Functions.
In these fields, view your organization's scanned cloud resources. To learn more, see License Information.
The Tenable Vulnerability Management header has been restyled to better align with Tenable’s latest branding and visual design guidelines. It also makes it much easier for users to access their personal profile and product and platform settings from any page in Tenable Vulnerability Management.
For more information, see Navigate Tenable Vulnerability Management.
Tenable Vulnerability Management now supports a single-line command installation and linking method for Tenable Nessus scanners and Tenable Nessus Agents. You can specify the sensor name and group assignment within the single-line command.
For more information, see Link a Sensor in the Tenable Vulnerability Management User Guide.
Tenable Vulnerability Management changed how it processes fully qualified domain names (FQDNs) for assets. All FQDNs will be normalized to lowercase and then the duplicates will be merged.
For example, where asset1 would previously have three FQDNs: ["VeryImportantAsset.local", "veryimportantasset.local", "externalimportantasset.local"], after the change asset1 will have two FQDNs: ["veryimportantasset.local", "externalimportantasset.local"].
This change streamlines the Host Assets view in the Assets Workbench in the user interface, prevents assets from registering as duplicates, and enables users to better focus on the assets that need their attention.