Nessus 8.13.0 Release Notes - 2020-12-07
The following are the new features included in Nessus 8.13.0:
Ability to deploy Nessus as a Docker image for a container – Users can now access an official Docker image for Nessus to deploy as a container. You can run Nessus offline or online, and the deployment includes plugin support.
For more information, see Deploy Nessus as a Docker Image in the Nessus User Guide.
Additional operating system support – Nessus is now supported on Amazon Linux 2 and Apple macOS Big Sur (11).
- Agent Remote Configuration – You can configure some agent settings remotely from Nessus Manager, rather than having to configure the setting directly on the agent.
For more information, see Modify Remote Agent Settings in the Nessus User Guide.
New Predefined Reports for Nessus Professional– Added three new predefined reports for Nessus Professional customers, allowing users to create HTML or PDF reports that preconfigure the most useful summaries for vulnerability management.
Users can create:
A report summarizing a list of IPs with what vulnerabilities were found in the scan.
A report summarizing all known/default accounts found on systems during the scan.
A report for vulnerabilities older than one year, which gives insight on when the vulnerabilities were initially reported to be exploitable.
For more information, see Create a Scan Report in the Nessus User Guide.
Changed Functionality and Performance Enhancements
The following additional enhancements are included in Nessus 8.13.0:
Nessus updated to use OpenSSL 1.1.1h.
Updated the Nessus user interface to use jQuery v3.5.1, to address a vendor-reported cross-site scripting vulnerability. For more information, see the Tenable Product Security Advisory.
Prevented downgrading to prior versions if a master password is configured in order to prevent the DB from getting into a corrupted state.
Increased the default time before Agents are required to relink in Nessus Agent clustering configurations if the parent node is down or unreachable.
Added capability for Nessus cluster child nodes to link to the Nessus Manager parent node through a proxy.
Added in-report data descriptions for Nessus Professional pre-defined reports, as well as visual markings to identify Live Results.
Updated build artifacts to create a separate build for Amazon Linux 2.
|Bug Fix||Defect ID||Applies to|
|Updated Nessus to use the same username validation for all user creation methods, including mkcert-client||01081253||All Nessus versions|
|Fixed an issue that could cause filtered compliance scan results to not export correctly||01078705||All Nessus versions|
|Fixed an issue that could cause Nessus Manager with clustering enabled to create very large, fragmented DB files||01101123||Nessus Manager|
|Fixed a potential issue with viewing Agent scan results in Nessus Manager for Agents with multiple NICs configured||01081048||Nessus Manager|
|Fixed a condition that was causing a benign but misleading error log message for Tenable.io linked scanners||01075254||Tenable.io cloud scanners|
|Added cleanup of orphaned scan policy files on Nessus scanners generated from Tenable.sc launched scans||01064111||Managed scanners|
|Added a setting to allow global disabling of gzip compression for any responses from the Nessus web server.||N/A||All Nessus versions|
- You can upgrade to the latest version of Nessus from any previously supported version.
- If your upgrade path skips versions of Nessus, Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.
Tenable.io-linked scanners receive the latest software update starting one week after the Nessus general availability (GA) date.
- If you want your scanners to automatically update to the newest version prior to that date, set your Nessus Update Plan to Opt in to Early Access releases.
- If you want to manually update your scanners to the latest version prior to that date, disable automatic updates so the scanner does not automatically downgrade to the previous version.
For Nessus 8.8.0 and later running on Windows, you must install Visual C++ Redistributable for Visual Studio 2015 on the host operating system. The following Windows versions require a minimum Service Pack to be installed:
- Windows 7 SP1
- Windows Server 2008 SP2
- Windows Server 2008 R2 SP1