Security Center in Tenable Enclave Security System Requirements

Tenable Security Center in Kubernetes Requirements

Note: Tenable recommends using an empty Kubernetes cluster for Tenable Security Center deployments. These requirements assume that the Kubernetes cluster where you install Tenable Security Center has nothing else installed.

Tenable strongly recommends using high-performance disks when you deploy Tenable Security Center in a Kubernetes cluster. Tenable Security Center is a disk-intensive application and using disks with high read/write speeds (for example, SSDs or NVMe SSDs) results in the best performance. The requirements in the following tables are based on AWS M5 or better processor specifications. Using slower processors, like those found in AWS M5a instances, will impact performance for your Tenable Security Center in Kubernetes deployment.

For supported Kubernetes environments and installation instructions, see Tenable Security Center in Kubernetes.

Requirements When Running Basic Network Scans + Local Checks

# of Hosts Managed by Tenable Security Center

CPU

Memory

Disk Space used for Vulnerability Trending

1 to 2,500 active IPs

8000 m

32 GiB

90 days: 125 GB

180 days: 250 GB

2,501 to 10,000 active IPs

16000 m

64 GiB

90 days: 450 GB

180 days: 900 GB

10,001 to 25,000 active IPs

32000 m

128 GiB

90 days: 2.4 TB

180 days: 5 TB

25,001 to 50,000 active IPs

48000 m

192 GiB

90 days: 4.5 TB

180 days: 9 TB

Requirements When Running Basic Network Scans + Local Checks + 1 Configuration Audit

# of Hosts Managed by Tenable Security Center

CPU

Memory

Disk Space used for Vulnerability Trending

1 to 2,500 active IPs

16000 m

64 GiB

90 days: 225 GB

180 days: 450 GB

2,501 to 10,000 active IPs

32000 m

128 GiB

90 days: 900 GB

180 days: 1.8 TB

10,001 to 25,000 active IPs

32000 m

128 GiB

90 days: 4.5 TB

180 days: 9 TB

25,001 to 50,000 active IPs

48000 m

192 GiB

90 days: 9 TB

180 days: 18 TB