Forum Discussion
Tenable Research Release Highlight Nessus Agent Reset...
Tenable Research Release Highlight
Nessus Agent Reset Plugin and Scan Template
Summary
Tenable Research has released a Credentialed Scan plugin and Scan Template “Nessus 10.8.0 / 10.8.1 Agent Reset” in support of addressing the issues in the Nessus Agent 10.8.0 and 10.8.1.
Change
- New Scan Template: “Nessus 10.8.0 / 10.8.1 Agent Reset”
- Pre-requisite: Ensure that the agent version is set to 10.8.2 or 10.7.x in Agent Profile (for TVM) and Nessus Manager (for TSC).
This Scan Template and Credentialed Scan plugin will run OS specific scripts to remotely reset the agent plugins on Windows, Mac OS or ‘Nix based Nessus Agent host machines on 10.8.0 or 10.8.1. These scripts and the permissions level each script requires are detailed in the Nessus Agent 10.8.2 Release Notes (https://docs.tenable.com/release-notes/Content/nessus-agent/2025.htm#10.8.2) under the [Perform a plugin reset] section.
Notes:
- The Nessus Agent Reset plugin will only run from the provided Scan Template and will not reset Nessus Agents when run from any other Scan Template.
- For Ubuntu/Debian Unix credentials, please ensure that only one set of privilege escalation credentials are provided with the required permissions level for the OS script to execute.
- 13 JAN 2025 UPDATE: Please note that triggering a plugin reset will result in a large spike in network traffic.
Impact
Without this script, customers would have to logon to each Nessus Agent host and run the appropriate Nessus Agent Reset script for that host OS. Using this Scan Template and Credentialed Scan plugin, customers can run the Nessus Agent Reset scripts on each updated Nessus Agent from a Remote Credentialed Scan, with the necessary credentials and permissions, using Nessus, Nessus Manager, T.VM, and T.SC (released 08 JAN).
Target Release Date
07 JAN 2025
17 Replies
Is there any thought to developing plugin that can be used to relink and agent that is unlinked from nessus manager? Restart the service if not runnings etc .. That would be really helpful.....
Is there a video that shows how to configure the 10.8.0/10.8.1 scan? I am clueless about the credential part.
So just to confirm, if someone can please... If I update to 10.8.2, or down to 10.7.3, will that alone fix everything, or do i still need to run a credentialed scan and run that plugin reset scan job?
- phillip_kimConnect Contributor
Hello! Quick question, how does Tenable refresh the plugin for the listed versions if the scanners are appearing offline on the platform? In short, how does it still communicate with the agent? Thank you.
- chinmay_kulkarnConnect Contributor
I believe, from experience, that if teams and organizations have deployed and are running Nessus agents on servers and workstations, they will not have accounts for Nessus scanners to run credentialed scans.
- arkanterConnect Contributor
tested as well-- here are the two results I got from running this credentialled scan on ten pilot machines:
result 1: agents remained at 10.8.1 and offline
The Tenable Nessus Agent installed at C:\Program Files\Tenable\Nessus Agent was unsuccessfully reset:
Nessus Agent Service not currently running. Unable to continue.
result 2: agent remained at 10.8.1 and online
The Tenable Nessus Agent installed at C:\Program Files\Tenable\Nessus Agent was successfully reset:
Plugin Reset process completed successfully.
- sean_sparksConnect Contributor
These scripts and the permissions level each script requires are detailed in the Nessus Agent 10.8.2 Release Notes
I cannot seem to locate the permission level and script details in the linked release notes?
- mitangi_k_mehtaConnect Contributor
We tested a network scan using a Nessus (Cluster) Manager and it does work.
- steve_j_ketchumConnect Contributor
The plugin for Nessus Agent 2025 Refresh is now available. It is Nessus Plugin number 213497. Might be a good idea to do a manual active plugin update.
Still don't know how beneficial it will be without agents being online and able to receive the plugin database update.
- stephane_grundsConnect Contributor
The only way I think this can be useful, is if you have a remote nessus scanners (not an agent), and perform a credentialled scan. This will be able to log in, and reset the plugins.
- gerron_thurmanConnect Contributor
Similar situation. We're using agents to avoid credential scans for thousands of VMs. I hope a security vendor doesn't assume all clients have the same credentials across thousands of environments.
Corrected.
Changed
- Without this script, customers would have to logon to each Nessus Agent host and run the appropriate Nessus Agent Reset script for that host OS after upgrading to 10.8.2.
To
- Without this script, customers would have to logon to each Nessus Agent host and run the appropriate Nessus Agent Reset script for that host OS .