TOC & Recently Viewed

Recently Viewed Topics

Hardware and Software Requirements

Before deploying LCE, confirm that the prerequisite software and hardware requirements have been met and that you have an operational instance of Tenable.sc. Depending on the size of your organization and the way you deploy LCE, the hardware requirements for LCE change. All deployments have a common set of minimum software requirements.

This section contains the following:

Software Requirements

All deployments of LCE require the following:

  • An active LCE license
  • RHEL/CentOS 5.x, 6.x, or 7.x, 64-bit
  • Elasticsearch 2.3.3 to 2.4.6
  • Java Runtime Environment (JRE) 1.8 update 20 or later

Additionally, while LCE is active, it requires exclusive access to certain ports. The only services that are required to support remote users are SSH and the LCE interface (lce_wwd). If other services are active on the system, conflicts should be avoided on the following default ports:

Ports LCE Receive (Listen) On
Port Description
162/UDP SNMP
514/UDP  Syslog
22/TCP SSH, for requests from Tenable.SC
601/TCP Syslog
1243/TCP Vulnerability detection, if enabled in Tenable.SC
6514/TCP Encrypted syslog
8836/TCP LCE Administrative Web UI
31300/TCP Events from LCE Clients
 
Ports LCE Sends On
PortDescription
514/UDPSyslog (forwarded)
443/TCPPull requests to the plugins feed at plugins.nessus.org
601/TCPSyslog (forwarded)
 
Ports LCE uses over Loopback Interface
PortDescription
7091/TCPInternal communication, showids to lce_queryd
7092/TCPInternal communication, lce_tasld to lced
 

Caution: The system running the LCE can operate a syslog daemon, but the syslog daemon must not be listening on the same port(s) that the LCE server is listening on.

Hardware Requirements

The hardware requirements for LCE change based on the number of events being processed.

Estimating Events

The following table provides the estimated average number of events from various sources.

Devices

Number of Estimated Events

1 workstation/laptop

0.5 events/sec

1 web-facing app server

20 events/sec

1 web-facing firewall/IDS/IPS

75 events/sec

1 internal application server (low volume)

5 events/sec

1 internal application server (high volume: IIS, Exchange, AD)

20 events/sec

1 internal network device

2 events/sec

To convert your event rate to bytes per day, it is recommended that you multiply your total events/second by 250 bytes/event and multiply by 86,400 seconds/day.

Tip:You can use the following calculator to determine the total number of events per second as well as the bytes per day.

Workstations

Web-facing Application Servers

Web-facing Firewalls/IDS/IPS

Internal Application Servers (low volume)

Internal Application Servers (high volume: IIS, Exchange, AD)

Internal Network Devices

events/second * 250 bytes/event * 86,400 second/day = 0 bytes/day

System Specification

The following table specifies the system requirements based on the number of events the LCE server is processing.

Installation scenarioRAMProcessorHard diskHard disk space
One LCE server with Elasticsearch processing less than 5,000 events per second 16 GB 8 cores10,000 RPM HD, or SSD of equiv. IOPS capability; RAID 0/10 configuration 2x Licensed storage size
One LCE server with Elasticsearch processing between 5,000 and 20,000 events per second 32 GB 16 cores15,000 RPM HD, or SSD of equiv. IOPS capability; RAID 0/10 configuration
One LCE server with Elasticsearch processing greater than 20,000 events per second 64 GB or more 24 cores or moreSSD of IOPS capability at least equiv. to a 15,000 RPM HD; RAID 0/10 configuration

Note: To query an archived Elasticsearch database , it will need to be restored. The recommended hard disk space does not include optional archiving of logs that exceed the licensed limit.

The LCE server requires a minimum of 20 GB of storage space to continue running and storing logs. If less than 1 GB is available, the Log Engine (lced) process will stop gracefully and refuse to store additional logs. The current system disk space is visible on the Health and Status page of the LCE interface.

File System Recommendations

Placing your activeDb on a networked file system (e.g. NFS) will result in inadequate system performance. Tenable recommends that you use EXT3, EXT4, XFS, or ZFS; and that you pay close attention to the mount options. Here are the mount options that Tenable suggest using, and the mount options Tenable suggest staying away from:

If your file system is: It is recommended that you use:It is not recommended to use:
EXT3, EXT4, XFSnoatimeatime or strictatime or relatime or diratime or No *atime at all.
EXT3 barrier=0barrier=1
EXT4barrier=0 or nobarrierbarrier=1 or barrier
XFSnobarrierbarrier
EXT3, EXT4data=writebackdata=journal or data=ordered or No data=* at all.
ZFSatime=offatime=on or relatime=on or No *atime at all.
ZFSHardware-dependent

compression=gzip or compression=gzip-N or compression=zle

compress=gzip or compress=gzip-N or compress=zle

ZFSlogbias=throughputlogbias=latency or No logbias at all.
ZFSprimarycache=metadataprimarycache=all or primarycache=none or No primarycache=* at all.
ZFSHardware-dependentrecordsize=512 or recordsize=1024 or recordsize=2048 or recordsize=4096

Licenses

There is no licensed limit to the number of events or IPs that the LCE can be configured to monitor.

There are different licenses available for LCE based on the total amount of storage used by LCE. The licenses are based on 1 TB, 5 TB, and 10 TB storage sizes. A license for LCE is provided as a part of Tenable.sc Continuous View. There is no difference in the LCE software that is installed, just the maximum storage size that can be used by LCE. The size limit of the Elasticsearch databases can be configured via the LCE interface. Data that exceeds your license limit will be archived.

Supported Platforms

If you are using an AWS instance in conjunction with LCE, it is required that you use an Elastic Network Interface (ENI). More information about using an ENI with an AWS instance can be found here.

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.