Tenable Vulnerability Management 2024 Release Notes
These release notes are listed in reverse chronological order.
April 23, 2024
The following is not supported in Tenable FedRAMP Moderate environments. For more information, see the Tenable FedRAMP Moderate Product Offering.
Tenable is pleased to announce key features and content that enhance how you work with compliance findings in Tenable Vulnerability Management. This release includes hundreds of new compliance-focused report templates, dashboards, and widgets as well as new findings filters.
-
Report template categories — In a previous release, Tenable introduced report template categories. On the Reports page, new categories now contain new templates. Review the categories in Create a Report.
-
Dashboard templates — On the Dashboards page, click New Dashboard > Template Library to choose from new dashboards in categories under Host Audits. Review the categories in Create a Dashboard.
-
Dashboard widgets — On the Dashboards page, click Widget Library to add new widgets from categories under Host Audits.
-
Custom widgets — When adding a custom widget, you can now include host audit data, as described in Create a Custom Widget.
-
Findings filters — On the Findings workbench in the Host Audits tab, new benchmarking and compliance filters now appear, as described in Findings Filters.
April 3, 2024
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.
For more information, see Info-level Reporting and Basic Settings in the Tenable Vulnerability Management User Guide.
April 2, 2024
Tenable has updated the Findings workbench and Findings Details page with two new fields that enable you to run more accurate findings reports and measure SLA compliance for scanned vulnerabilities.
The new fields are:
-
Time Taken to Fix — How long it took to fix a vulnerability found on a scan, in hours or days. Only applicable to Fixed vulnerabilities. Now appears as a Findings Details field, a Findings workbench filter, and a Findings workbench column.
-
Last Fixed — The last time a previously detected vulnerability was scanned and noted as no longer present on an asset. Now appears as a Findings workbench column and a Findings Details field. Tenable added the filter in a previous release.
To learn more, see Vulnerability Details and Findings Filters.
March 20, 2024
Tenable has updated Findings workbench reports and templates in the Act > Reports section as follows:
-
Password protection for Findings reports — When you generate a report on the Findings workbench, add a password that uses AES 128-bit encryption. To learn more, see Generate a Findings Report.
-
Report categories in the Reports section — When you create a report in the Act > Reports section, choose a template from new categories that better organize Tenable Vulnerability Management's many templates. Tenable will add new categories in the coming days. To learn more, see Create a Report.
March 14, 2024
In Tenable Vulnerability Management's Remediation section, use a new Asset Tags filter and Asset Tags column to identify which tags are associated with your remediation projects and goals.
For more information, see Remediation.
March 6, 2024
On the License Information page, the Cloud Security section now displays your licensed Tenable cloud assets instead of your billable cloud resources so you can easily see how much of your license you are using.
Tip: In the new version of Tenable Cloud Security, your licensed asset count may be calculated by multiplying your Compute, Serverless, and Container Repository assets against a ratio and then adding your Container Images (if you use Tenable Container Security). If a ratio is applied, it now appears in the Cloud Security section, in the new License Ratio field. To learn more, contact your Tenable representative.
Tenable has made the following updates to the License Information page:
-
Cloud Security section — A new tooltip explains how your licensed cloud assets are calculated. Your ratio, if any, appears in the new License Ratio field. If you have no ratio, 1 appears.
-
Compute — Now displays your licensed cloud computing assets. Hover on the number to view your billable resources (the number of resources before any ratio is applied).
-
Serverless — Now displays your licensed serverless assets. Hover on the number to view your billable resources.
-
Container Repositories — Now displays your licensed container repositories. Hover on the number to view your billable resources.
-
Container Images (Legacy Container Security) — This field’s new name clarifies that Tenable Container Security is a legacy application.
To learn more, see License Information.
The Findings and Assets workbenches now support multiple browser tabs.
The following enhancements support this change:
-
Findings workbench tabs — Right-click a tab (for example, Cloud Misconfigurations) to open it in a new browser tab, active filters included.
-
Details panes — On the findings or assets details panes, in the upper right corner, right-click See All Details to open the corresponding details page in a new browser tab.
-
Workbench context menus — On the Findings or Assets workbenches, right-click a row and then click View All Details or View all Details in New Tab to open the corresponding details page in the current tab or a new one.
-
Grouped findings — On the Findings workbench, right-click a finding grouped by Plugin and then click View Plugin Details or View Plugin Details in New Tab to review the plugin on Tenable's website.
-
Workbench action menus — On the Findings or Assets workbenches, in the () menu, click View All Details or View all Details in New Tab to open the corresponding details page in the current tab or a new one.
To learn more, see Use the Context Menu in the Explore section of the Tenable Vulnerability Management User Guide.
February 28, 2024
Bug Fix |
Defect ID |
---|---|
Fixed an issue in the Scans section where web application scans failed with an Insufficient scope error. |
01769832, 01769765, 01768766, 01768764, 01769400, 01770252, 01769478, 01769538, 01770915, 01769177, 01771942, 01772182, 01772321 |
Fixed an issue where some assets were automatically added to tag exclusion lists. |
01728823, 01739470, 01735561, 01731375, 01756024 |
Fixed an issue on the Findings workbench where searches with the CVE filter did not return new results. |
01779775, 01780299, 01778390, 01782808, 01784618 |
Fixed an issue where scans using plugin 84239 did not generate output | 01518718, 01757216 |
February 12, 2024
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.
February 6, 2024
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 1.41.4.2.
For more information about Sensor Proxy, see the Sensor Proxy User Guide.
January 30, 2024
Bug Fix |
Defect ID |
---|---|
Fixed an issue on the Assets workbench where using the CISA KEV Due Date filter caused an error to appear. |
01761164, 01761011, 01761653, 01760891 |
Fixed an issue on both the Findings and Assets workbenches where exporting findings or assets intermittently failed with an error. |
01730886, 01739220, 01730892 |
Fixed an issue on the Findings workbench where two users saw different findings when using the same filters. |
01763398, 01762034, 01763507 |
Fixed an issue on the Findings workbench where the Host Audits tab failed to load. | 01730539 |
January 23, 2024
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.
January 18, 2024
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.
January 16, 2024
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.
January 12, 2024
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.
January 4, 2024
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.