Download Nessus 8.10.1

Nessus is a security scanner that can scan a network for known exploits and open services. Results can then be displayed in various reports to be displayed. The software can also integrated with other packages, such as CyberArk for credential management and MDM software from Microsoft, Apple, MobileIron and AirWatch. Nessus comes in three different flavors: the free-to-use Home edition, and the paid Professional and Manager editions. Tenable has released Nessus 8.10.1 with the following changes:

New Features

The following are the new features included in Nessus 8.10.1:

• Added Option to Force Stop a Scan Job – Added the ability to force a scan job to stop. For more information, see Stop a Running Scan in the Nessus User Guide.

Changed Functionality and Performance Enhancements

• Increased time window for marking an agent as offline – Improved the determination of when an agent should be considered offline.
• Upgraded Nessus to use OpenSSL 1.1.1g.
• Streamlined application of large cloud-based exclusion lists to improve scan performance.

Bug Fixes

• Fixed an issue with target scanning access not being enforced consistently for Tenable.io scans.
• When a recast rule is used for an emailed report the recast rule was ignored.
• Resolved an issue where scans run on the first of the month filled-up the disk space with verbose log detail for certain customers.
• When using the “CVSS Vector Contains” filter in Nessus Pro, results did not match the filter.
• Email notification for agent scans did not send when clustering is enabled.
• For Agent scans in clustered environment, the “plugin_set” value was not available in .nessus exports.
• Resolved issue when processing large exclusion lists that caused delays in starting scans.
• Exported HTML/PDF did not display enumerated service names.
• Agent scan in clustered environment was reporting in pending state rather than running.
• Improved the determination of when an Agent should be considered offline.
• Fixed an issue where Agent blackout windows were not enforced for Agents in a clustering configuration.