If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners, Tenable Nessus Agents, or Tenable Nessus Network Monitors (NNM) located in mainland China, you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.
Removed the ability to specify a Java executable path from the Tenable Nessus user interface to prevent undesired changes. Administrators can now specify a Java executable path with a nessuscli command: nessuscli fix --set path_to_java (for more information, see Fix Commands).
The most important field is the Nessus Linking Key (nessusLinkingKey, required). It is always required. This document explains where to find it: Retrieve the Tenable Nessus Agent Linking Key (Tenable Nessus Agent 10.4). In the PowerShell interface, specify nessusLinkingKey under -ProtectedSettings so that it will be encrypted by Azure. All other fields are passed unencrypted through -Settings.
You can choose whether to link with Nessus Manager or Tenable.io. In the command-line interface, this is done by setting nessusManagerApp (nessusManagerApp, required) to cloud, or to local. Those are the only two choices.
If you choose Nessus Manager, you must provide the Nessus Manager host (nessusManagerHost) and port number (nessusManagerPort). The extension accepts an IP address or fully qualified domain name.
df19127ead