Installation guide

/dev/sda1 101086 24455 71412 26% /boot

tmpfs 1037732 0 1037732 0% /dev/shm

# service SecurityCenter restart

Shutting down SecurityCenter services: [ OK ]

Starting SecurityCenter services: [ OK ]

Forgot login credentials

 Contact Tenable Support (support@tenable.com).

Invalid license error

 If you receive an invalid license error while attempting to log in as an Organization Head or lower, an

administrator must log in and upload a new valid license key. A user with access to the host OS and valid

permissions can also check that an up-to-date license exists in /opt/sc4/daemons. Licenses are obtained from

Tenable and copied to the daemons directory as the “tns” user.

-rw-r--r-- 1 tns tns 1942 Oct 29 12:14 license.key

Reporting does not work

 Check your Java version. Only OpenJDK and Oracle JRE are supported. The existence of another type of Java

on the system will break reporting.

LCE

LCE server does not appear to be operational:

 Log into the SecurityCenter UI as admin and confirm that the LCE server state is “Working” along with all attached

LCE clients.

 Check that you can SSH from the SecurityCenter host to the LCE host.

 Check that the LCE daemon is running on its host and listening on the configured port (TCP port 31300 by

default):

# netstat -pan | grep lced

tcp 0 0 0.0.0.0:31300 0.0.0.0:* LISTEN 30339/lced

 Check that the listening ports can be reached from the network and are not blocked by a firewall.

 If the LCE server is not operational, attempt to start the service:

# service lce start

Starting Log Correlation EngineLCE Daemon Configuration

LICENSE: Tenable Log Correlation Engine 3-Silo Key for [user]

EXPIRE: 11-10-011

REMAIN: 30 days

MESSAGE: LCE (3-silo license)

MESSAGE: Valid authorization

--------------------------------------------------------

[ OK ]

No events from an attached LCE server

 Log into the SecurityCenter UI as admin and confirm that the LCE server state is “Working” along with all attached

LCE clients.

 Confirm connectivity by checking that heartbeat events show up in the SecurityCenter UI.