Tip: Tenable rebranded SecurityCenter as Tenable.sc. For more information, see the announcement.
You can download the update files from the Tenable.sc Downloads page.
If you are running Tenable.sc 188.8.131.52 or later, you can upgrade directly to Tenable.sc 5.16.0. If you are running a version earlier than Tenable.sc 184.108.40.206, upgrade to Tenable.sc 220.127.116.11 before upgrading to Tenable.sc 5.16.0.
Note: If your upgrade path skips versions of Tenable.sc (e.g., upgrading from 18.104.22.168 to 5.16.0), Tenable recommends reviewing the release notes for all skipped versions. You may need to update your configurations because of features and functionality added in skipped versions.
This feature introduces the ability for a Tenable.sc administrator to log in with credentials once and switch to a different user without having to enter credentials again. The first time a user logs in, they must log in as an administrator. The user can then create additional linked users tied to their administrator account. Each linked user is a Security Manager in the Full Access group. Linked user accounts can only be accessed by the user logging into their admin account first; you cannot directly log in to a linked user account. All login activity is logged for full audit reporting.
For more information, see Linked Users in the Tenable.sc User Guide.
Enhanced Tenable.sc to Lumin Connector Status Information
This feature provides the following enhancements to the Tenable.sc to Lumin Connector:
Lumin Data Metrics: The metrics on the Lumin Data page are now computed nightly for faster data retrieval. Metrics are preserved on the Lumin Data page until they are computed again.
Lumin Dashboard Link: On the Lumin data page, a link is now provided that opens the Lumin dashboard in a separate browser tab so that the user can quickly view all Lumin metrics.
Lumin History Log: The History Log on the Lumin Data page now includes the transfer duration for assets in addition to repositories.
Test Connection Button: The Lumin Configuration page now has a button for testing the connection to Tenable.io and Lumin.
Tenable.io Agent Scan Scheduling through Tenable.sc
Users in Tenable.sc can now configure, schedule, and launch basic agent scans in Tenable.sc that are run through a linked Tenable.io instance. When the agent scan completes, results are imported to an agent repository in Tenable.sc.
For more information about agent scanning in Tenable.sc, see Agent Scanning in the Tenable.sc User Guide.
SAML User Provisioning
Tenable.sc can now be configured to create and modify users automatically from either a SAML 2.0 or Shibboleth 1.3-based identity provier.
For more information, see SAML Authentication in the Tenable.sc User Guide.
Hashicorp Vault Integration
Added support for Hashicorp Vault Active Directory, Key/Values 1, and Key/Values 2 secrets engines.
For more information, see SSH Credentials, Windows Credentials, and Database Credentials Authentication Method Settings in the Tenable.sc User Guide.
IBM DataPower Gateway Integration
Added support for IBM DataPower Gateway credentials.
For more information, see API Gateway Credentials in the Tenable.sc User Guide.
|Bug Fix||Defect ID|
|Fixes memory minor memory leaking for the "List Vuln" and "Vuln Detail" tools. Reduced memory usage for the "Vulnerability Summary" tool during most cases when not VPR sorting. Fixes known segfault bug while sorting on VPR score for "Vulnerability Summary" tool.|
|Fixed an issue with displaying IPv6 addresses on the vulnerability details of agent repositories.|
|For customers using Tenable Core + Tenable.sc, upgrades of Tenable.sc were failing due to an error in calculating the amount of free disk space available for the upgrade.||01062912|
|Fixed an issue with incorrect results being returned while browsing individual scan results and using vulnerability text filtering.||01080513|
|Fixed an issue where the "Server Calculation error" icon displayed instead of "loading" icon for policy statement after adding the ARC template.|
|Fixed an issue where Stop button was incorrectly displayed on Agent Scan.|
|Fixed an issue where deleting users from large user sets could halt Tenable.sc operations for a short time.|
|Fixed an issue where users could not publish report results from the gear dropdown menu on the report result list view.|
|Fixed a longstanding bug where Intune MDM credentials were causing mobile repository syncs to fail.|
|Fixed an issue where an incorrect confirmation message would be displayed for deleting a dashboard component.|
|Fixed an issue where VPR and CVSS score was not displaying decimals.|
|Fixed an issue where the expiration for accepted risk rules did not take into account accept risk rules for agent repositories.|
|Fixed an issue where the Tenable UUID was not migrating with DHCP tracking for IPv4 repositories.|
|Fixed an issue where running a remediation scan against a Windows target caused an accurately displayed NetBios name to change to “Unknown."|
|Fixed an SQL error that occurs during upgrade from Tenable.sc 5.11.0, 5.12.0, or 5.13.0 to Tenable.sc 5.15.0 (skipping Tenable.sc 5.14.1) if the customer has duplicate users in their database.||01061736|
For more information about the API changes for this release, see the Tenable.sc API Changelog.
Filenames and Checksums
Filenames and MD5 or SHA-256 checksums are located on the Tenable.sc Downloads page.
Tenable Integrated Product Compatibility
The following table lists the Tenable product versions tested with Tenable.sc 5.16.0.
8.5.1 and later
|Tenable.ot||3.4.9 and later|
|Log Correlation Engine||5.1.1 and later|
|Nessus Network Monitor||5.9.0 and later|