System Requirements
Supported Kubernetes Environments
-
Kubernetes versions: 1.28 to 1.30 in any of the following environments:
-
Standalone Kubernetes
-
Amazon Elastic Kubernetes Service (EKS)
-
AzureKubernetes Service (AKS)
-
Google Kubernetes Engine (GKE)
-
-
Helm versions: 3.11 and later
Note: Tenable Enclave Security is compatible with OpenShift. Please contact your Tenable Support representative for additional information.
For requirements specific to Tenable Security Center and Container Security, see the following topics:
-
Cloud Requirements in the Tenable Security Center user guide.
-
System Requirements in the Container Security user guide.
Note: Tenable recommends using an empty Kubernetes cluster for Tenable Enclave Security deployments. These requirements assume that the Kubernetes cluster where you install Tenable Enclave Security has nothing else installed.
Tenable strongly recommends using high-performance disks when you deploy Tenable Enclave Security in a Kubernetes cluster. Tenable Enclave Security 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 Enclave Security deployment.
Requirements When Running Basic Network Scans + Local Checks
# of Hosts Managed by Tenable Enclave Security |
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 Enclave Security |
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 |