The search for reflects a real operational need: keeping Nessus effective in disconnected environments. The correct modern approach involves generating a challenge code and fetching the signed tarball from Tenable’s offline portal. While the legacy all-2.0.tar.gz file name persists in forums and documentation, the principles remain the same – get the latest plugin bundle, validate it, and apply it carefully.
The terminal is highly reliable because it handles large data archives smoothly without web browser timeout errors. Open your terminal as a root or administrative user.
If you prefer the terminal, move the file to the scanner and run the following update command: /opt/nessus/sbin/nessuscli update /path/to/all-2.0.tar.gz download nessusupdateplugins all20targz new
Tenable is gradually moving toward a model where even offline scanners use a signed update package that doesn’t require the old all-2.0.tar.gz mono-file. However, as of 2025, the challenge-code + tarball method remains fully supported, especially for air-gapped deployments.
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 The search for reflects a real operational need:
Last updated: To align with "new" – check Tenable’s download page daily for plugin refresh dates.
Before executing the command, the following prerequisites must be met: The terminal is highly reliable because it handles
Under your Nessus version, look for: Nessus-<version>-ubuntu-<arch>.tar.gz ? No — the plugins bundle is separate. Actually correct path: https://plugins.nessus.org/v2/offline.php (requires license key)