Install Tenable Security Center Director

Tenable Security Center Director is a Linux-only application, and this topic assumes a basic understanding of Linux. To deploy Tenable Security Center as a preconfigured virtual appliance in a Windows-centric virtual environment, see the Tenable Core documentation.

For information about new features, resolved issues, third-party product updates, and supported upgrade paths, see the release notes for Tenable Security Center Director6.5.x.

Before you begin:

• Complete system prerequisites, as described in Before You Install.

• Connect an external PostgreSQL database if your Tenable Security Center Director installation meets any of the following criteria:

  • Your Tenable Security Center Director instance has over 100,000 assets.

  • Your Tenable Security Center Director instance is a non-rpm installation.

• Download the installation RPM file from the Tenable Security Center downloads page. If necessary, depending on the operating system of the host, move the installation RPM file onto the host.

• Confirm the integrity of the installation RPM file by comparing the download checksum with the checksum on the Tenable Security Center downloads page, as described in the knowledge base article.

• If your organization requires Tenable Security Center to use /dev/random instead of /dev/urandom to generate random number data for secure communication functions, modify the random data source as described in Use /dev/random for Random Number Data Generation.

To install Tenable Security Center Director:

1. On the host where you want to install Tenable Security Center Director, open the command line interface (CLI).

2. In the CLI, run one of the following commands to install the RPM:

   Caution: When you perform a sudo install, use sudo –i to ensure the proper use of environmental variables.

   Run the following command to install the RPM, where the file name is the RPM that you downloaded from the Tenable Security Center downloads page:

   Copy

   # dnf install SecurityCenter-x.x.x-el9.x86_64.rpm

   Output similar to the following appears:

   # dnf install SecurityCenter-6.x.x-el9.x86_64.rpm

   Preparing...                ########################################### [100%]

      1:SecurityCenter         ########################################### [100%]

   Installing Nessus plugins ... complete

   Applying database updates ... complete.

   By default, SecurityCenter will listen for HTTPS requests on ALL available interfaces. To complete your installation, please point your web browser to one of the following URL(s):

   https://x.x.x.x

   Starting SecurityCenter services

   [  OK  ] SecurityCenter services: [  OK  ]

   #

   Tenable Security Center Director installs the package into /opt/sc and attempts to start all required daemons and web server services.

   Caution: During the installation process, Tenable Security Center produces a log file in a temporary location: /tmp/sc.install.log. Once the installation process finishes, the file is stored here: /opt/sc/admin/logs/install.log. Do not remove or modify these files; they are important for debugging in case of a failed installation.

   Tip: In rare cases, you must restart the system after installation to start all services. For more information, see Start, Stop, or Restart Tenable Security Center Director.

What to do next:

• If you manage more than 10,000 active IPs, update the Apache configuration file before you use Tenable Security Center Director.