Note: The indexing process heavily utilizes CPU and RAM. Your Nessus UI may temporarily display a "Plugins Compiling" message, during which scanning operations are paused. Automating the Offline Process
Cause : You downloaded the wrong file type (e.g., a .zip instead of .tar.gz ) or your Nessus version is severely mismatched with the plugin pack. Solution : Verify your Nessus version ( nessuscli --version ) and ensure you download the plugin pack from the correct Tenable URL specific to that version.
This will output a unique challenge string. —you will need it on the download webpage.
On your offline Nessus host, open your command terminal and execute the management tool to register an offline asset: download nessusupdateplugins all20targz new
Think of it as your Nessus scanner's "detection dictionary." Without regularly updating this plugin set, you cannot identify the latest critical vulnerabilities like Log4Shell, Spring4Shell, or the newest zero‑days impacting your infrastructure.
Go to https://www.tenable.com/downloads/nessus Note: You need a valid Nessus license (Free/Professional/Expert).
# Restart Nessus service to trigger update (systemd example) sudo systemctl restart nessusd # Or trigger update via binary (if available) sudo /opt/nessus/sbin/nessuscli update --plugins Note: The indexing process heavily utilizes CPU and RAM
: After submitting, click the link to download the plugin archive (often labeled as all-2.0.tar.gz or similar). 2. Install the Plugins
The search query "download nessusupdateplugins all20targz new" represents the need for a reliable, version‑controlled method of keeping Nessus effective in the most challenging environments. By understanding that all-2.0.tar.gz is the complete offline plugin set, knowing how to download it directly from Tenable using your challenge code, and following the systematic nessuscli update process detailed in this guide, you ensure that your vulnerability scanner never falls behind—even without an internet connection.
: Once downloaded on a machine with internet access, the file is transferred to the offline scanner. Solution : Verify your Nessus version ( nessuscli
Navigate to the location of your all-2.0.tar.gz file and run the nessuscli update command.
Copy the tarball into the container using docker cp and run nessuscli update inside the container’s shell.