Download Nessus-update-plugins All-2.0.tar.gz [exclusive] -
The file all-2.0.tar.gz is a compressed archive containing all current Tenable Nessus plugins, typically used for offline updates in environments without direct internet access. 1. Download Process
To download the all-2.0.tar.gz file, you must first generate a specific link from Tenable, as the download URL is unique to your license and challenge code.
Generate Challenge Code: Run the command /opt/nessus/sbin/nessuscli fetch --challenge on your offline Nessus system.
Obtain Download Link: Visit the Tenable Offline Registration page and enter your Challenge Code and Activation Code.
Direct Link Format: Once submitted, you will receive a custom link similar to https://plugins.nessus.org/get.php?f=all-2.0.tar.gz&u=[UNIQUE_ID]&p=[UNIQUE_ID]. 2. Manual Installation Steps
Once you have downloaded the file and moved it to your offline system, you can install it using the Command Line Interface (CLI) or the User Interface (UI). Via Command Line Interface (CLI)
Using the nessuscli tool is often the most reliable method for large plugin updates. Linux: # /opt/nessus/sbin/nessuscli update all-2.0.tar.gz.
Windows: Run an Administrator command prompt and execute "C:\Program Files\Tenable\Nessus\nessuscli.exe" update all-2.0.tar.gz.
macOS: # /Library/Nessus/run/sbin/nessuscli update all-2.0.tar.gz. Via User Interface (UI)
Log in to your Nessus Professional or Nessus Manager instance. Navigate to Settings > Software Update. Click Manual Software Update.
Select Upload your own plugin archive, choose the all-2.0.tar.gz file, and click Continue. 3. Usage in Tenable Security Center Perform an Offline Nessus Plugin Update
How to Manually Update Nessus Plugins: A Guide to nessus-update-plugins all-2.0.tar.gz
Nessus, Tenable’s industry-standard vulnerability scanner, relies on regularly updated plugins to detect the latest security flaws. While most Nessus installations update automatically (with a valid subscription), air-gapped networks or systems with restricted internet access require a manual update. download nessus-update-plugins all-2.0.tar.gz
This article walks you through downloading and applying the nessus-update-plugins all-2.0.tar.gz package.
Note: The filename nessus-update-plugins all-2.0.tar.gz implies an all-in-one plugin bundle (version 2.0 format). Tenable’s actual plugin feed filenames may vary (e.g., all-2.0.tar.gz). Always verify the filename from your Tenable account.
6. Verify plugin count via web UI or CLI
/opt/nessus/sbin/nessuscli --version
If the file is actually a raw plugin feed (all-2.0.tar.gz), the command simplifies to:
sudo /opt/nessus/sbin/nessuscli update /path/to/all-2.0.tar.gz
What’s Inside the Tarball?
Extracting the archive reveals:
plugins/ — Directory containing hundreds or thousands of .nasl (Nessus Attack Scripting Language) files.plugin_feed_info.inc — Metadata including version, release date, and plugin set hash.version.txt or plugins-version.txt — Plaintext file with the plugin revision number.nessus-update-plugins — A shell script (optional) that automates the process.
A sample nessus-update-plugins script might look like:
#!/bin/bash
NESSUS_HOME="/opt/nessus"
PLUGIN_TAR="all-2.0.tar.gz"
echo "Stopping Nessus..."
$NESSUS_HUB/sbin/nessusd stop
echo "Extracting plugins..."
tar -xzf $PLUGIN_TAR -C $NESSUS_HOME/var/nessus/plugins/
echo "Restarting Nessus..."
$NESSUS_HOME/sbin/nessusd start
echo "Update complete."
Important Security Considerations
- Source Trust — Only obtain plugin updates from Tenable directly or a verified mirror. A malicious
nessus-update-plugins script could inject backdoors.
- Checksum Verification — Always compare MD5/SHA256 hashes against Tenable’s published values.
- Version Compatibility — A plugin tarball from an older Nessus version might break newer installations. Ensure the plugin feed matches your Nessus major version.
- Backup — Before applying a manual update, backup
/opt/nessus/var/nessus/plugins/.
Comparison to Modern Nessus Update Methods
| Method | Command | Internet Required |
|--------|---------|-------------------|
| Online update (official) | nessuscli update | Yes |
| Offline update (official) | nessuscli update nessus-updates-<date>.tar.gz | No |
| This custom wrapper | ./nessus-update-plugins all-2.0.tar.gz | No |
Troubleshooting Common Issues
- “Permission denied” — The
nessus-update-plugins script may lack execute permissions. Fix: chmod +x nessus-update-plugins.
- “nessuscli not found” — Ensure the Nessus binary directory is in your PATH or use full path
/opt/nessus/sbin/nessuscli.
- “Invalid plugin feed” — The tarball may be corrupted or for a different architecture. Re-download and verify checksum.
- Plugins not loading after update — Check logs:
/opt/nessus/var/nessus/logs/nessusd.log. Look for errors like “failed to parse plugin”.
Conclusion
The file nessus-update-plugins all-2.0.tar.gz represents a manual, offline approach to updating Nessus vulnerability detection rules. While modern Nessus versions rarely require such manual intervention except in air-gapped environments, understanding this process is valuable for security professionals managing legacy systems or highly restricted networks. Always prioritize official Tenable update channels, but keep this method in your toolkit for when the network is silent.
If you encounter this file in your environment, treat it with care: verify its origin, understand its contents, and test the update on a non-production Nessus scanner first.
Title: How to Manually Update Nessus Plugins: A Guide to nessus-update-plugins and all-2.0.tar.gz
If you are a Nessus user, you know that keeping your plugin feed updated is critical for detecting the latest vulnerabilities. Usually, Nessus handles this automatically in the background. However, if you are working in a secured environment, an air-gapped network, or troubleshooting a sync error, you might find yourself searching for a specific command:
nessus-update-plugins all-2.0.tar.gz
This command is the "old school" way to manually force an update using a downloaded archive. In this post, we will explain what this file is, how to use it, and the modern alternative you should probably be using today.
Section 3: Official Methods to Download nessus-update-plugins-all-2.0.tar.gz
Tenable provides several official pathways to obtain this file. Below are the three primary methods, ranked from most convenient to most manual.
6. Troubleshooting Common Issues
If you are trying to use this command and running into issues, check the following:
- Permissions: You must run this as
root or using sudo. The plugins are installed in system directories restricted to standard users.
- Proxy Settings: If your network requires a proxy to reach the internet,
nessus-update-plugins will fail unless you configure the proxy settings in the Nessus GUI (under Settings > Proxy) or via the CLI configuration.
- License Expiration: If your Tenable subscription has lapsed, the utility will connect but refuse to download
all-2.0.tar.gz. It will typically return an error regarding feed registration.
- Plugin Architecture: Ensure the
all-2.0.tar.gz file matches the Nessus version. Trying to load a plugin set meant for Nessus 10.x onto a legacy Nessus 6.x scanner will likely fail due to script incompatibility.
Section 8: Frequently Asked Questions (FAQ)
Q1: I downloaded nessus-update-plugins-all-2.0.tar.gz, but my Nessus version is 10.2. Will it work?
Yes. The plugin bundle is version-agnostic for Nessus 5.x through 10.x. However, always check Tenable’s release notes – very old engines may require a specific format.
Q2: How often should I download this file?
Tenable releases new plugins daily (sometimes multiple times per day). For critical vulnerabilities (e.g., Log4Shell), update immediately. Otherwise, weekly is standard. The file all-2
Q3: Can I use this file to update multiple Nessus scanners?
Absolutely. Copy the same tarball to each offline scanner. The license per scanner must be valid and separate.
Q4: Why doesn't Tenable call it exactly nessus-update-plugins-all-2.0.tar.gz anymore?
Newer naming convention includes a timestamp: nessus-update-plugins-all-2.0-YYYY-MM-DD.tar.gz. Your automation should use wildcards or rename.
Q5: Is there an alternative for Windows offline updates?
Yes. The same tarball works on Windows Nessus. Use nessuscli update nessus-update-plugins-all-2.0.tar.gz from Command Prompt as Administrator.
4. Run the update script (if present)
sudo ./nessus-update-plugins
Step-by-Step Installation
Step 1 – Transfer the file to the offline scanner
Use a USB drive, SCP over a jump server, or a secure CD-ROM. Copy the tarball to a temporary directory, e.g., /tmp/.
Step 2 – Locate the Nessus CLI
Nessus installations typically place the update tool here:
- Linux:
/opt/nessus/sbin/nessuscli
- Windows:
C:\Program Files\Tenable\Nessus\nessuscli.exe
- macOS:
/Library/Nessus/run/sbin/nessuscli
Step 3 – Apply the update
sudo /opt/nessus/sbin/nessuscli update /tmp/nessus-update-plugins-all-2.0.tar.gz
You will see output similar to:
[info] Extracting plugins...
[info] Plugins extracted successfully.
[info] Compiling plugins...
[info] Update complete. Restart Nessus to apply changes.
Step 4 – Restart Nessus
sudo systemctl restart nessusd # Linux systemd
sudo /etc/init.d/nessusd restart # SysV init
net stop "Tenable Nessus" && net start "Tenable Nessus" # Windows
Step 5 – Verify the update
Log into the Nessus web UI (port 8834). Go to Settings → About → Plugins. The “Plugin Date” should reflect the timestamp from your tarball.
