Tenable Enclave Security 2026 Release Notes

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

Tenable Enclave Security 1.8.0 Release Notes (2026-2-26)

Tenable Enclave Security 1.8 is now available, featuring horizontal reports scalability and enhanced Vulnerability Priority Rating (VPR) models.

For instructions on how to install or update Tenable Enclave Security, see:

For information about Container Security, see the Container Security User Guide.

Note: Tenable Enclave Security 1.8 introduces a new Kubernetes pod for reporting, which requires additional system resources. For more information, see the Tenable Enclave Security System Requirements.

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.

Helm Chart Deployment Options

Tenable Enclave Security 1.8 includes the ability to deploy Tenable Enclave Security to sandbox and demo namespaces via private cloud Helm Charts, providing more flexibility for testing and pre-production environments.

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 users from accessing the Exposure Response interface.