Sensor Proxy 2025 Release Notes

Tip: You can subscribe to receive alerts for Tenable documentation updates.

These release notes are listed in reverse chronological order.

(Early Access) Sensor Proxy 1.2.0 (2025-04-09)

The following are new features included in Sensor Proxy 1.2.0:

  • Added support for FIPS compliance in Sensor Proxy for Enterprise Linux 8 and 9 environments.

The following enhancements are included in Sensor Proxy 1.2.0:

  • Updated Go to version 1.22.9 on Enterprise Linux 8 and 9.

  • Updated OpenSSL for OpenResty and Nginx to 3.0.16 on Enterprise Linux 8 and 9.

  • Updated OpenSSL for OpenResty and Nginx to 3.0.15 on Enterprise Linux 7.

  • Sidecar now uses the version of OpenSSL provided by the operating system. The version number may vary over time with operating system updates, even on a particular installation. At the time of this release, the latest OpenSSL and FIPS module version numbers for each supported platform are as follows:

    • Enterprise Linux 7—Not applicable (FIPS mode is not supported)

    • Enterprise Linux 8—OpenSSL and FIPS module 1.1.1k

    • Enterprise Linux 9—OpenSSL 3.2.2, FIPS module 3.0.7

The following are security updates included in Sensor Proxy 1.2.0:

  • Fixed an incorrect privilege assignment issue in Enterprise Linux 8 and 9 environments.

Bug Fix Defect ID
Fixed an issue that produced a log error in the command line output when an invalid ca-path was provided. 02165284
Fixed a link issue that truncated the sidecar response and returned 0 bytes. 02174228, 02211594
Fixed a race condition with sidecar’s client, which caused linking and connectivity issues. 02188553
  • 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.

  • 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.

    • 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.