Tenable Nessus Agent 2024 Release Notes
Tenable Nessus Agent 10.6.2 (2024-04-15)
Bug Fix | Defect ID |
---|---|
Prevented a scenario in which multiple simultaneous scans assigned to an agent that has not retrieved plugins yet could execute without plugins. | 01785607 |
-
If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners, Tenable Nessus Agents, Tenable Web App Scanning scanners, or Tenable Nessus Network Monitors (NNM) located in mainland China, you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.
-
New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure, we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.
-
Starting with Tenable Nessus Agent 8.1.0, Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain, they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.
- Recommended Action: 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 and all future subdomains, reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.
-
- You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.
- If your upgrade path skips versions of the Tenable Nessus Agent, Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.
Tenable Nessus Agent 10.6.1 (2024-04-05)
Bug Fix | Defect ID |
---|---|
Fixed an issue that caused agents to restart when certain DNS errors occurred. | 01851304, 01896427 |
Fixed an issue where a small subset of executable files of agents installed on Windows systems did not have digital signatures. | 01875389 |
-
If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners, Tenable Nessus Agents, Tenable Web App Scanning scanners, or Tenable Nessus Network Monitors (NNM) located in mainland China, you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.
-
New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure, we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.
-
Starting with Tenable Nessus Agent 8.1.0, Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain, they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.
- Recommended Action: 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 and all future subdomains, reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.
-
- You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.
- If your upgrade path skips versions of the Tenable Nessus Agent, Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.
Tenable Nessus Agent 10.6.0 (2024-03-28)
The following are new features included in Tenable Nessus Agent 10.6.0:
-
Tenable Nessus Agent now supports Automatic Asset Merging (an upcoming feature in Tenable Vulnerability Management) through the use of an agent identification service.
The following enhancements are included in Tenable Nessus Agent 10.6.0:
-
Offline installations now support indefinite linking attempts until successful.
-
The nessuscli install-relay command now supports proxy authentication. To view the new proxy parameters, see the install-relay description in Tenable Nessus Agent CLI Commands.
-
Improved the plugin update process to avoid partial plugin updates.
Bug Fix | Defect ID |
---|---|
Improved error handling under low memory conditions to increase scanner stability. | 01788324, 01782329, 01790186, 01778293, 01789790, 01780350 |
The following are supported platform updates made in Tenable Nessus Agent 10.6.0:
-
Added foundational support for Tencent0S, which will be available for download once plugins for the operating system are complete.
-
If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners, Tenable Nessus Agents, Tenable Web App Scanning scanners, or Tenable Nessus Network Monitors (NNM) located in mainland China, you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.
-
New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure, we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.
-
Starting with Tenable Nessus Agent 8.1.0, Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain, they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.
- Recommended Action: 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 and all future subdomains, reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.
-
- You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.
- If your upgrade path skips versions of the Tenable Nessus Agent, Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.
Tenable Nessus Agent 10.4.5 (2024-01-10)
Bug Fix | Defect ID |
---|---|
Fixed an issue that caused agents to clear profile configurations after incorrectly decompressing a profile configuration directive. | 01742389, 01741656 |
-
If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners, Tenable Nessus Agents, Tenable Web App Scanning scanners, or Tenable Nessus Network Monitors (NNM) located in mainland China, you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.
-
New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure, we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.
-
Starting with Tenable Nessus Agent 8.1.0, Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain, they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.
- Recommended Action: 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 and all future subdomains, reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.
-
- You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.
- If your upgrade path skips versions of the Tenable Nessus Agent, Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.
Tenable Nessus Agent 10.5.1 (2024-01-10)
Bug Fix | Defect ID |
---|---|
Fixed an issue that caused failing downloads to not incrementally delay correctly, which lead to repeated download attempts. | 01701708 |
-
If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners, Tenable Nessus Agents, Tenable Web App Scanning scanners, or Tenable Nessus Network Monitors (NNM) located in mainland China, you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.
-
New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure, we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.
-
Starting with Tenable Nessus Agent 8.1.0, Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain, they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.
- Recommended Action: 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 and all future subdomains, reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.
-
- You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.
- If your upgrade path skips versions of the Tenable Nessus Agent, Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.