Recently Viewed Topics
This document describes many of the changes that are included in SecurityCenter 5.3.1, as well as significant enhancements and notes for upgrading. A PDF file of these release notes is also available here.
Before You Upgrade
If you are planning an upgrade from SecurityCenter 4.x, due to the many enhancements and changes made in the SecurityCenter 5 solution, Tenable strongly encourages you to install and test the latest version of SecurityCenter in a pre-production environment prior to upgrading in your production environment to ensure the new workflows and enhancements are compatible with your current workflows. To receive an evaluation key that will allow you to install SecurityCenter in a pre-production environment for evaluation, log in to the Tenable Support Portal and click “Activation Codes”. Under SecurityCenter, you will see a link to download a demo key for the SecurityCenter 5 solution.
SecurityCenter 5.3.1 supports the following direct upgrade paths:
- 4.8.1+ > 5.3.1
- 5.0+ > 5.3.1
Installations running previous versions of SecurityCenter 4.x must upgrade to at least 4.8.1 prior to upgrading to SecurityCenter 5.3.1. For more information about upgrading to SecurityCenter 5.3.1, refer to the SecurityCenter User Guide.
If you are using Nessus agents, SecurityCenter 5.3.1 requires Nessus Cloud or Nessus Manager 6.5 or later. If you are not using Nessus agents, SecurityCenter requires Nessus Scanner 6.3 or later. SecurityCenter requires the Passive Vulnerability Scanner 4.0 or later. If SecurityCenter Continuous View uses the Log Correlation Engine (LCE) for log processing, SecurityCenter requires LCE 4.2 or later for complete feature compatibility.
Note: Due to changes in API architecture, all APIs created using SecurityCenter 4.x have been deprecated. For more information about SecurityCenter 5 API, refer to the SecurityCenter 5 API Documentation.
The command syntax for an RPM upgrade is as follows:
# rpm -Uvh [RPM Package File Name]
File Names & MD5 Checksums
In this release we have resolved a condition where users could see errors in the logs regarding the update of the plugin distribution. Additionally, updates were made to the security of the application. Details can be found in the Security Advisory.