Link to Tenable.io
During initial installation, you can install Nessus as a remote scanner linked to Tenable.io. If you choose not to link the scanner during initial installation, you can link your Nessus scanner later.
Note: 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, which the scanner uses to communicate with Tenable.io.
Note: Once you link Nessus to Tenable.io, it remains linked until you unlink it.
Before you begin:
- Configure Nessus as described in Configure Nessus.
- If the Nessus scanner is or was previously linked to Tenable.io, Tenable.sc, or Nessus Manager, you need to unlink the scanner or run the nessuscli fix --reset-all command (for more information, see Fix Commands).
To link Nessus to Tenable.io from the Nessus user interface:
-
On the Welcome to Nessus screen, select Link Nessus to another Tenable product.
-
Click Continue.
The Managed Scanner screen appears.
-
From the Managed by drop-down box, select Tenable.io.
- In the Linking Key box, type the linking key of your Tenable.io instance.
-
Click Continue.
The Create a user account screen appears.
- Create a Nessus administrator user account that you use to log in to Nessus:
- In the Username box, enter a username.
In the Password box, enter a password for the user account.
Note: Passwords cannot contain Unicode characters.
-
Click Submit.
Nessus finishes the configuration process, which may take several minutes.
-
Using the administrator user account you created, Sign In to Nessus.
To link Nessus to Tenable.io from the command-line interface (CLI):
If you registered or linked Nessus previously, you need to reset Nessus before linking to Tenable.io.
Run the following commands to reset Nessus and link to Tenable.io based on your operating system. To retrieve the linking key needed in the following commands, see Link a Sensor in the Tenable.io user guide.

-
Open the Linux CLI.
-
Run the following commands in the listed order:
# service nessusd stop# cd /opt/nessus/sbin# ./nessuscli fix --reset-all# ./nessuscli adduser -
Do one of the following:
-
If you are linking to a Tenable.io FedRAMP site, run the following link command:
# /opt/nessus/sbin/nessuscli managed link --key=<key> --host=fedcloud.tenable.com --port=443 -
If you are not linking to a FedRAMP site, run the following link command:
# ./nessuscli managed link --key=<LINKING KEY> --cloud
-
-
Run the following linking command:
# service nessusd start

-
Open the Windows CLI.
-
Run the following commands in the listed order:
> net stop "tenable nessus"> cd C:\Program Files\Tenable\Nessus> nessuscli fix --reset-all> nessuscli adduser -
Do one of the following:
-
If you are linking to a Tenable.io FedRAMP site, run the following link command:
> \opt\nessus\sbin\nessuscli managed link --key=<key> --host=fedcloud.tenable.com --port=443 -
If you are not linking to a FedRAMP site, run the following link command:
> nessuscli managed link --key=<LINKING KEY> --cloud
-
-
Run the following command:
> net start "tenable nessus"

-
Open Terminal.
-
Run the following commands in the listed order:
# launchctl unload -w /Library/LaunchDaemons/com.tenablesecurity.nessusd.plist# /Library/Nessus/run/sbin/nessuscli fix --reset-all# /Library/Nessus/run/sbin/nessuscli adduser -
Do one of the following:
-
If you are linking to a Tenable.io FedRAMP site, run the following link command:
# /opt/nessus/sbin/nessuscli managed link --key=<key> --host=fedcloud.tenable.com --port=443 -
If you are not linking to a FedRAMP site, run the following link command:
# /Library/Nessus/run/sbin/nessuscli managed link --key=<LINKING KEY> --cloud
-
-
Run the following command:
# launchctl load -w /Library/LaunchDaemons/com.tenablesecurity.nessusd.plist