The following are the new features included in Agent 8.2.0:
Staggered Scan Start - Users can now set a staggered scan start time for agent scans in Tenable.io and Nessus Manager. Agents deployed in that scan will delay starting the scan for a random number of minutes up to the maximum delay time set by the user. This is helpful in reducing load in environments with shared resources, such as virtual machine CPU, because agents will not all begin scanning at once.
Note: Nessus 8.12.0 or later is required to leverage this functionality in Nessus Manager.
OS Support Updates - In our ongoing efforts to support as many operating system variants as possible for our customers, we have extended Nessus Agent support for the following operating systems:
- Ubuntu 20.04
- SUSE Enterprise Server 15
- Kali Linux 2018, 2019 & 2020
Changed Functionality and Performance Enhancements
The following functionality was added or updated in Agent 8.2.0:
- Operating System & Library Pre-Upgrade Checks - Nessus Agent will now check that the host system is running a supported operating system version as well as any required libraries before upgrading to a new Agent version. For more information on supported operating systems, see Software Requirements in the Nessus Agent Deployment and User Guide.
Windows Dependency Update - Nessus Agent 8.2.0 and later requires Windows host systems to be running the Universal Microsoft C Runtime Library (UCRT) (for more information, see Microsoft Documentation). This means that some older versions of Microsoft Windows will require a minimum update to work with Nessus Agent 8.2.0 and later. Current Windows Agent installations that do not meet these requirements will not automatically upgrade past Agent 8.1.0.
The following lists the Windows variants and their minimum upgraded state. Users should experience no functional difference as a result of this change.
- Windows 7 SP1
- Windows 8.1 with April 2014 update
- Windows Server 2008 R2 SP1
- Windows Server 2008 SP2
- Windows Server 2012R2 with April 2014 update
|Bug Fix||Defect ID|
|Resolved an issue where Windows Agents could potentially use excessive CPU in a socket failure scenario.||01077419|
|Resolved an issue where reinstalling a new Agent was unexpectedly restoring the backup from a previously uninstalled agent version.||01062064|
|Added a timeout for Windows WMI calls within Agent scans, to prevent scans from stalling if the WMI API never returns.||00997983|
|Resolved an issue where some Windows systems were experiencing java.exe being deleted if it existed in the Agent startup directory||01084260|
Users upgrading agents via Nessus Manager will not upgrade to 8.2.0 and later unless Nessus Manager is already updated to 8.12.0 or higher.
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.