Tenable Enclave Security 2026 Release Notes

Apply the patch to a Tenable Security Center running on Tenable Enclave Security:

1. Download the patch from the Tenable Security Center Downloads page to Tenable Security Center. You can save the files in any location (for example, /tmp).

2. Copy the patch file to the Tenable Security Center pod of your namespace, where [patch file name] is the name of the .tgz patch file you downloaded:

   kubectl cp [patch file name] [namespace]/[sc-pod]:[patch file name]

3. Log in to the Tenable Enclave Security runtime container with the following command:

   kubectl exec -it tenable-security-center-0 -n [namespace] -- /bin/sh

4. Run the following command to untar the patch file:

   tar zxf [patch file name]

5. Run the following command to change the directory to the extracted directory, where [directory] is the extracted directory:

   cd [directory]

6. Stop the Tenable Security Center service with the following command:

   /scbase/SC.sh stop

7. Run the following command to begin the installation:

   sh ./install.sh

8. Run the following command to start Tenable Security Center:

   /scbase/SC.sh start

What to do next:

• (Optional) Confirm the patch successfully applied to Tenable Security Center, as described in the knowledge base article.

All versions:

• install.sh

• Analysis.php

• defines.php

• Files.php

• Users.php

• AuthenticationLib.php

• ConfigurationLib.php

• LCELib.php

• ReportChartingLib.php

• ReportFileReceiverLib.php

• ReportGenerateLib.php

• ScanDBLib.php

• ScanResultLib.php

• Utility.php

• VulnLib.php

• customPassivePluginUpload.php

• customPluginUpload.php

• IDSSignatures.php

• passivePluginUpdate.php

• pluginUpdate.php

• wasPluginUpdate.php

• ParseNessusFileTool.php

• ParseScanDBFileTool.php

• rest.php

Tenable Security Center 6.8.0 only:

• ScEncClient.php

Filenames and MD5 or SHA-256 checksums are located on the Tenable Security Center Downloads page.

Tenable Enclave Security

• API Gateway

  Tenable Enclave Security 1.9 introduces a platform-level API gateway that handles external traffic routing, TLS termination, and blade proxying for all Tenable Enclave Security products. The gateway offloads this work from the Tenable Security Center pod to improve performance and reliability under heavy load, and provides a central point for rate limiting and security controls across the platform.

  For more information, see Configure Customer Certificates for Tenable Enclave Security and Tenable Enclave Security System Requirements in the Tenable Enclave Security User Guide.

• Licensing Service

  Tenable Enclave Security 1.9 introduces a standalone licensing service that manages licensing centrally across blades, including Tenable Security Center and Container Security. Consolidating licensing into a shared service provides consistent license status and expiration handling across Tenable Enclave Security products.

  For more information, see License Requirements in the Tenable Enclave Security User Guide.

Tenable Enclave Security

• Licensing API Endpoint Deprecated

  The /tes/config/license/register API endpoint used to register Tenable Enclave Security licenses is deprecated as of Tenable Enclave Security 1.9 and will be removed in a future release. Use the new /api/v1/license (PUT) endpoint to register licenses. The /rest/file/upload endpoint for uploading license key files is not affected.

  For more information, see the API documentation.

• Fixed an issue in the Container Security agent where distroless and other reproducible-build images that use EPOCH as their build timestamp were silently excluded by the build-time filter. These images are now correctly discovered and scanned.

• Fixed an issue where installing or running Tenable Security Center on Tenable Enclave Security generated PHP warning messages related to file_get_contents() calls for Tenable Enclave Security system user configuration files.

• In Container Security-only deployments, Container Security reports may fail to generate. This issue will be resolved in a future release. If you are affected, contact Tenable Support.

The following table lists the Tenable product versions available with Tenable Enclave Security 1.9.0.

For information about EOL dates and policies for Tenable products, see the Tenable Software Release Lifecycle Matrix and Policy.

Apply the patch to a Tenable Security Center running on Tenable Enclave Security:

1. Download the patch from the Tenable Security Center Downloads page to Tenable Security Center. You can save the files in any location (for example, /tmp).

2. Copy the patch file to the Tenable Security Center pod of your namespace, where [patch file name] is the name of the .tgz patch file you downloaded:

   kubectl cp [patch file name] [namespace]/[sc-pod]:[patch file name]

3. Log in to the Tenable Enclave Security runtime container with the following command:

   kubectl exec -it tenable-security-center-0 -n [namespace] -- /bin/sh

4. Run the following command to untar the patch file:

   tar zxf [patch file name]

5. Run the following command to change the directory to the extracted directory, where [directory] is the extracted directory:

   cd [directory]

6. Stop the Tenable Security Center service with the following command:

   /scbase/SC.sh stop

7. Run the following command to begin the installation:

   sh ./install.sh

8. Run the following command to start Tenable Security Center:

   /scbase/SC.sh start

What to do next:

• (Optional) Confirm the patch successfully applied to Tenable Security Center, as described in the knowledge base article.

All versions [6.6.4, 6.7.5, 6.8.0]:

• install.sh

• httpd

• openssl

• php

• pg_ctl

• postgres

• psql

Tenable Security Center 6.7.5 and 6.8.0 only:

• redis-server

Filenames and MD5 or SHA-256 checksums are located on the Tenable Security Center Downloads page.

Reports Scalability Enhancements

Tenable Enclave Security 1.8 introduces significant architectural improvements to the reporting engine. These changes allow for faster generation of large-scale reports and improved stability when handling high-volume datasets within enclave environments.

Vulnerability Priority Rating (VPR) v2

Tenable Enclave Security 1.8 integrates the latest version of Tenable's VPR algorithm. VPR v2 provides more dynamic and accurate risk scoring by incorporating real-world threat intelligence and exploitability data, allowing you to prioritize remediation based on actual risk to your specific environment.

Enhanced Reporting Workspace

Tenable Enclave Security 1.8 updates the Reporting tile and workspace interface to provide a more intuitive experience for creating and managing reports related to your Tenable Enclave Security deployment.

Migration Streamlining

Updated and optimized steps for migrating Tenable Security Center RPM installations to Tenable Enclave Security.

Infrastructure Reliability

Updated internal Go library versions for the Tenable Enclave Security operator to improve service stability and security.

• Fixed an issue where the license expiration check did not correctly prevent blade installation when a license was expired.

• Resolved an error in Exposure Response that prevented data retrieval when sorting by the Plugin Count field in the My Affected Assets view.

• Resolved a scheduling error where the last day of the month was calculated incorrectly for February during leap years, which previously caused monthly scan failures.

• Fixed a critical deployment issue where fresh installs of Tenable Security Center failed if a PostgreSQL port was not explicitly defined.

• Resolved an issue where the backup and restore process did not account for containerized database environments.

• Fixed an issue where installation logs were moved to a temporary location, making troubleshooting difficult during failed installations.

• Corrected the text in scan settings to accurately reflect "exclude all" for scan exclusions.

• Fixed an issue in the Assets > Images view where sorting functionality was unavailable for the Registry Type column.

• Resolved a bug that occasionally prevented access to the Exposure Response interface.