TOC & Recently Viewed

Recently Viewed Topics

System Requirements

Operating System Requirements

This version of Tenable.sc is available for:

  • Red Hat Enterprise Linux 6 (RHEL 6), 64-bit
  • Red Hat Enterprise Linux 7 (RHEL 7), 64-bit
  • CentOS 6, 64-bit
  • CentOS 7, 64-bit

SELinux policy configuration is supported by Tenable in a Permissive mode.

Note: Other SELinux modes are known to work, but the required configuration varies based on policies and custom configurations that may be in place on-site. It is strongly recommended that SELinux implementation configurations are tested prior to deployment on a live network.

Secure Environment Requirements

It is assumed that organizations have the appropriate skill-set required to maintain the operating system environment in a secure manner and that they are configured and maintained with the following conditions:

  • The operating system must be configured in a secure manner to ensure that security controls cannot be bypassed.
  • The network must be configured to ensure that the Tenable.sc system resides in a secure network segment that is not accessible from the Internet.
  • Network time synchronization must be enabled to ensure that accurate time stamps are recorded in reports and log files.

    Note: The time zone is set automatically during the installation process with no user interaction. The time zone configured in php.ini must be synchronized with the system time zone in /etc/sysconfig/clock.

  • Access control mechanisms must be in place to ensure that only authorized users have access to the OS platform.

Of particular importance is the requirement to monitor system resources to ensure that adequate disk space and memory are available. If system resources are exhausted, there is a risk that audit data could be prevented from being logged due to the system becoming dysfunctional. See Tenable.sc Troubleshooting for information on how system administrators can recover the system should Tenable.sc become inoperative due to resource exhaustion. During recovery processes, actions by the system administrator may not be logged by Tenable.sc until sufficient resources have been made available.

The following resource provides details for secure administration of a Red Hat installation: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Security_Guide/index.html.

Note: Even though the security concepts from this guide are written for RHEL 6, most of the concepts and methodologies apply to earlier versions of RHEL that are supported with Tenable.sc.

Note: As with any application, the security and reliability of the installation is dependent on the environment that supports it. It is strongly recommended that organizations deploying Tenable.sc have an established and applied IT management policy that covers system administration integrity, resource monitoring, physical security, and disaster recovery.

Dependencies

Note: Either OpenJDK or the Oracle Java JRE along with their accompanying dependencies must be installed on the system along with any additional Java installations removed for reporting to function properly.

Note: Tenable does not recommend forcing the installation without all required dependencies. If your version of Red Hat or CentOS is missing certain dependencies, it will cause problems that are not readily apparent with a wide variety of functions. Tenable Support has observed different types of failure modes for Tenable.sc when dependencies are missing.

All dependencies must be installed on the system prior to installing the Tenable.sc package. While they are not all required by the installation RPM file, some functionality of Tenable.sc may not work properly if the packages are not installed.

Note: Using the latest stable production version of each package is recommended.

For a list of required packages, run the following command against the Tenable.sc RPM file:

# rpm –qp SecurityCenter-x.x.x-el6.x86_64.rpm --requires

- or -

# rpm –qp SecurityCenter-x.x.x-el7.x86_64.rpm --requires

To determine which version of a dependency is installed on your system, run the following command for each of the packages (replace “libtool” with the appropriate package):

# rpm –qa | grep libtool

If one of the prerequisite packages is missing, it can be installed using the “yum” or “rpm” package managers. For example, install Java 1.7.0 with “yum” using the command below:

# yum -y install java-1.7.0-openjdk.x86_64

Tenable.sc Communications and Repositories

The following table summarizes the components’ primary repositories and communication methods.

Tenable.sc

Installation Directory

/opt/sc

User Data

/opt/sc/orgs/<Organization Serial Number>

Repositories

/opt/sc/repositories/<Repository Number>

Admin Logs

/opt/sc/admin/logs/

Organization Logs

/opt/sc/orgs/<Organization Number>/logs/

Communication Interfaces

User Access: HTTPS

Feed Updates:

Acquired over SSL from Tenable servers directly to Tenable.sc or for offline installation. Plugin packages are secured via 4096-bit RSA digital signatures.

Copyright © 2019 Tenable, Inc. All rights reserved. Tenable, Tenable.io, Tenable Network Security, Nessus, SecurityCenter, SecurityCenter Continuous View and Log Correlation Engine are registered trademarks of Tenable, Inc.. Tenable.sc, Lumin, Assure, and the Cyber Exposure Company are trademarks of Tenable, Inc. All other products or services are trademarks of their respective owners.