TOC & Recently Viewed

Recently Viewed Topics

Tenable Core + Tenable.sc

To install and run Tenable Core + Tenable.sc, your system must meet the following requirements established for Tenable.sc. For more information about Tenable.sc requirements, see Tenable.sc (Formerly SecurityCenter).

Tenable Core + Tenable.sc Hardware Requirements

Use the following physical hardware recommendations for Tenable.sc as a guide when preparing your environment. Tenable.sc is not supported in cloud-based environments.

Storage Requirements

You must install Tenable.sc on direct-attached storage (DAS) devices. Tenable.sc does not support storage area networks (SANs) or network-attached storage (NAS) configurations.

Disk Space Requirements

Enterprise networks can vary in performance, capacity, protocols, and overall activity. Resource requirements to consider for deployments include raw network speed, the size of the network being monitored, and the configuration of the application. Processors, memory, and network cards will be heavily based on the former. Disk space requirements will vary depending on usage based on the amount and length of time data is stored on the system.

Tenable.sc Full Safe + Local Checks

Version

# of Hosts Managed by Tenable.sc

CPU Cores

Memory

Disk Space used for Vulnerability Trending

5.x

2,500 active IPs

4 2GHz cores

8 GB RAM

90 days: 125 GB

180 days: 250 GB

10,000 active IPs

8 3GHz cores

16 GB RAM

90 days: 450 GB

180 days: 900 GB

25,000 active IPs

16 3GHz cores

32 GB RAM

90 days: 1.2 TB

180 days: 2.4 TB

100,000 active IPs

32 3GHz cores

64 GB RAM

90 days: 4.5 TB

180 days: 9 TB

Tenable.sc Full Safe + Local Checks + 1 Configuration Audit

Version

# of Hosts Managed by Tenable.sc

CPU Cores

Memory

Disk Space used for Vulnerability Trending

5.x

2,500 active IPs

4 2GHz cores

8 GB RAM

90 days: 225 GB

180 days: 450 GB

10,000 active IPs

8 3GHz cores

16 GB RAM

90 days: 900 GB

180 days: 1.8 TB

25,000 active IPs

16 3GHz cores

32 GB RAM

90 days: 2.25 TB

180 days: 4.5 TB

100,000 active IPs

32 3GHz cores

128 GB RAM

90 days: 9 TB

180 days: 18 TB

Other Considerations

In addition to the above guidelines, please consider the following suggestions:

  • If the Nessus scanner is deployed on the same system as Tenable.sc, there will be less CPU and memory available during scans, causing slower performance. Use multi-core and/or multiple CPU servers to alleviate this. Placing the scanner on a secondary machine will alleviate performance bottlenecks.
  • If one or more NNM are in use, use multi-core and/or multiple CPU servers to increase performance.
  • Use the aggregate of the individual software product resource requirements to determine total hardware system requirements.
  • If Nessus or NNM is deployed on the same server as Tenable.sc, consider configuring the server with multiple network cards and IP addresses.

For more Tenable.sc requirements, see Hardware Requirements and System Requirements in the Tenable.sc User Guide.

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.