Nessus Agent 8.1.0 Release Notes - 2020-09-08

Note: Tenable recommends upgrading to Nessus Agent 8.1.1 or Nessus Agent 8.2.0, which include a fix for a potential vulnerability. For more information, see the Tenable Product Security Advisory.

New Features

The following are the new features included in Agent 8.1.0:

  • Configure Scan and Plugin Compilation Performance and CPU Usage - Using the nessuscli, users can set the performance mode separately for scans and for plugin compilation, which affects the amount of CPU utilized by the Nessus Agent during those processes. Users can set performance to high (default), medium, or low. Low performance slows down scans or plugin compilation, but reduces the agent's CPU consumption. Setting the performance to medium or high means that scans or plugin compilation completes more quickly, but the agent consumes more CPU. For more information on this feature, see Advanced Settings in the Nessus Agent User Guide.

Changed Functionality and Performance Enhancements

The following functionality was added or updated in Agent 8.1.0:

  • Added extended operating system and library dependency checking to ensure Nessus Agents that update automatically meet the necessary dependencies as a prerequisite to upgrading.

Bug Fixes

Bug Fix
Resolved an issue with Debian based install packages where the Agent service did not automatically restart after upgrade.

Upgrade Notes

  • New Tenable.io Domain - As a part of continuous security and scalability improvements to Tenable infrastructure, we have added a new sensor.cloud.tenable.com domain that Tenable.io-linked agents communicate with.

    • Starting with Agent 8.1.0, Tenable.io-linked agents communicate with Tenable.io using sensor.cloud.tenable.com. In case agents are not able to connect to the new domain, they fall back to using cloud.tenable.com. Agents with earlier versions will continue to use the cloud.tenable.com domain.

    • Recommended Action: If you use domain allow lists for firewalls, Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains, reducing operational overhead. Please contact your network administrator for assistance with making necessary changes to your allow list..
  • You can upgrade to the latest version of Nessus Agent from any previously supported version.
  • If your upgrade path skips versions of Nessus Agent, Tenable recommends reviewing the release notes for all skipped versions. You may need to update your configurations because of features and functionality added in skipped versions.
  • Tenable.io-linked Agents now support the ability to choose your Agent update plan:

    • By default, the Agent update plan is set to update to the generally available (GA) version .

    • If you want to manually update your Agents to the newest version when it is made available for Early Access (EA), first disable automatic updates so the agent does not automatically downgrade to the previous version (GA).

    • If you want your Agent to automatically update to the newest version, set your Agent update plan to ea.

  • Nessus Agents 7.7.0 and later support the capability to downgrade from a later version:

    • Tenable.io-linked Nessus Agents support automatically downgrading via the Agent update plan setting. To automatically revert a Tenable.io-linked Nessus Agent to the previous version, set your Agent update plan to stable. Your agent will always remain on an earlier version than the latest GA version until you change your update plan.

    • To manually downgrade a Nessus Agent to a previous version (7.7.0 or greater), first disable automatic updates, then obtain the Agent package from Tenable Support and install it over your current version.