Hardware Requirements
You can run Tenable Security Center on hardware, with or without Tenable Core. For more information about Tenable Core, see the Tenable Core User Guide.
Note: Tenable strongly discourages running Tenable Security Center or Tenable Core + Tenable Security Center in an environment shared with other Tenable applications.
Note: Complex deployments require more resources. For example, deployments with large numbers of organizations or application objects. For more information, see Performance in the Tenable Security Center Large Deployment Guide.
Storage Requirements
Tenable recommends installing Tenable Security Center on direct-attached storage (DAS) devices (or storage area networks [SANs], if necessary) with a storage latency of 10 milliseconds or less.
Tenable does not support installing Tenable Security Center on network-attached storage (NAS), including network filesystems such as NFS.
CPU and Memory Requirements
The CPU core and memory values in the following tables are minimum recommendations for the number of active IPs that Tenable Security Center manages. The disk space tables in the following section do not include CPU or memory.
Note: Tenable Security Center recommends a minimum of 16 GB RAM for all installations. Tenable Security Center will not operate with less than 8 GB (8192 MiB) RAM. See the following tables for recommended CPU and memory by deployment size.
Requirements When Running Basic Network Scans + Local Checks
| # of Hosts Managed by Tenable Security Center | CPU Cores | Memory |
|---|---|---|
| 1 to 2,500 | 8 2GHz cores | 16 GB RAM |
| 2,501 to 10,000 | 16 3GHz cores | 32 GB RAM |
| 10,001 to 25,000 | 32 3GHz cores | 64 GB RAM |
| 25,001 to 100,000 | 48 3GHz cores | 96 GB RAM |
Requirements When Running Basic Network Scans + Local Checks + 1 Configuration Audit
| # of Hosts Managed by Tenable Security Center | CPU Cores | Memory |
|---|---|---|
| 1 to 2,500 | 8 2GHz cores | 16 GB RAM |
| 2,501 to 10,000 | 16 3GHz cores | 32 GB RAM |
| 10,001 to 25,000 | 32 3GHz cores | 64 GB RAM |
| 25,001 to 100,000 | 48 3GHz cores | 128 GB RAM |
Factors That Increase CPU and Memory Requirements
Complex deployments require more CPU and memory than the values in the tables. Consider the following factors when sizing your deployment:
-
The number of organizations
-
The number of reports that run concurrently
-
The number of scans that run concurrently
-
Scan result retention and trending depth
-
The number of application objects, such as dashboards, reports, assets, and scan policies
For deployments that exceed 100,000 active IPs, you must use an external PostgreSQL instance. For more information, see External PostgreSQL Requirements.
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 are heavily based on the former. Disk space requirements vary depending on usage based on the amount and length of time data is stored on the system.
Disk requirements for Tenable Security Center 6.9 and later are primarily driven by scan result storage.
Estimation only: Many factors influence actual disk usage, including scan plugin selection, the number and types of findings per host, scan concurrency, the number of repositories, organization count, and configured retention periods. The values in this section are high-water-mark estimates intended for capacity planning purposes. Actual usage will vary. Monitor disk utilization after deployment and adjust retention settings as needed.
Tenable recommends installing Tenable Security Center on direct-attached storage (DAS) or a SAN with latency of 10 milliseconds or less. NAS and NFS are not supported. High-performance disks (SSDs) are strongly recommended. The /opt partition should reside on a dedicated disk or partition separate from the operating system.
Disk Space Components
| Component | Size | Notes |
|---|---|---|
| Scan result storage | Scales with host count, scan frequency, and retention | Dominant driver. See sizing tables below. |
| Repository data |
~1.1 MB per host (with local checks) ~2.3 MB per host (with local checks and 1 compliance audit) |
Stored both in files on disk and in the local PostgreSQL database. |
| OS, plugins, and application databases | ~25 GB | Base install included in the sizing tables below. |
| Active scan temp space | 150 GB baseline (peak; scales with deployment) | Ephemeral. Required under /opt during active scans. |
| Upgrade temp space |
~10 GB |
Required in /tmp during upgrades. |
Scope and Assumptions
The sizing tables in this section depend on the following conditions:
-
Nessus scanners are directly attached and scan attachments are disabled. If you use linked scanners or enable plugin attachments, see Linked Scanners or Enabling Plugin Attachments.
-
Scans run weekly with a 60-day retention period (9 scans stored).
-
Each host has a high-water mark of 250 findings per scan.
-
The 150 GB of active scan temp space is a baseline, not a ceiling. Large scans and multiple concurrent scans can use more.
Scan Result Sizing
The following tables show total disk requirements for the scope and assumptions above. A host with 250 findings corresponds to roughly 500 KB of scan result data. The tables use 30 MB per 50 hosts per scan (0.6 MB per host) to leave a small buffer. Each row is sized at the upper bound of its host range. For example, the 1 to 2,500 row is sized for 2,500 hosts.
Basic Network Scans + Local Checks (Credentialed)
| # of Hosts Managed by Tenable Security Center | Repository Data | Scan Results (9 scans) | Base Install | Minimum Total Disk Required |
|---|---|---|---|---|
| 1 to 2,500 | 2.75 GB | 13.5 GB | 25 GB | 41 GB |
| 2,501 to 10,000 | 11 GB | 54 GB | 25 GB | 90 GB |
| 10,001 to 25,000 | 27.5 GB | 135 GB | 25 GB | 188 GB |
| 25,001 to 50,000 | 55 GB | 270 GB | 25 GB | 350 GB |
| 50,001 to 100,000 | 110 GB | 540 GB | 25 GB | 675 GB |
Basic Network Scans + Local Checks + 1 Configuration Audit
| # of Hosts Managed by Tenable Security Center | Repository Data | Scan Results (9 scans) | Base Install | Minimum Total Disk Required |
|---|---|---|---|---|
| 1 to 2,500 | 5.75 GB | 40.5 GB | 25 GB | 72 GB |
| 2,501 to 10,000 | 23 GB | 162 GB | 25 GB | 210 GB |
| 10,001 to 25,000 | 57.5 GB | 405 GB | 25 GB | 488 GB |
| 25,001 to 50,000 | 115 GB | 810 GB | 25 GB | 950 GB |
| 50,001 to 100,000 | 230 GB | 1.62 TB | 25 GB | 1.88 TB |
Note: Add at least 150 GB of additional headroom for active scan temp space. The 150 GB figure is a baseline, not a ceiling: large scans and multiple concurrent scans can require more. This space is reclaimed after scans complete but must be available on the /opt partition during scanning.
Adjusting for Scan Frequency and Retention
The tables above assume weekly scans with a 60-day retention period. To calculate disk requirements for different configurations, use the following approach:
-
Scan results per year: (scans per week) × 52 × (assets ÷ 50) × 30 MB
-
Retention adjustment: Multiply by (scans retained ÷ (scans per week × 52)). Scans retained is the number of scans stored within your retention period, rounded up from your retention days. For example, 60 days of retention at one scan per week is 9 scans retained, and 63 days of retention at two scans per week is 18 scans retained. The result equals scans retained × (assets ÷ 50) × 30 MB.
-
Compliance audit adjustment: For environments running basic network scans plus one configuration audit, use 90 MB per 50 assets per scan instead of 30 MB (1.8 MB per host per scan). Audit results carry more content per finding and grow as audit files add checks.
Note: The tables in this section use 60-day retention as the sizing example (9 weekly scans stored). At the default retention of 365 days, multiply the scan result storage figures by approximately 6× (52 scans stored instead of 9). Reducing retention from the default is the most effective way to control disk consumption.
Linked Scanners or Enabling Plugin Attachments
When using linked scanners or when plugin attachments are enabled, scan results take up significantly more disk space than the directly attached baseline. Use the following per-host estimates when sizing scan result storage:
-
Credentialed vulnerability scans: 4 MB per host per scan
-
Configuration audits: 2 MB per host per scan
For example, a weekly scan of 2,500 hosts with 60-day retention (9 scans) requires approximately 90 GB of scan result storage for credentialed vulnerability scans. Multiply by your host count, scan frequency, and configured retention period to determine total allocation.
For a combined credentialed vulnerability scan and one configuration audit, use 6 MB per host per scan (4 MB + 2 MB); a weekly scan of 2,500 hosts with 60-day retention (9 scans) requires approximately 135 GB of scan result storage. Multiply by your host count, scan frequency, and configured retention period to determine total allocation.
Amazon EC2 Instance Type Sizing Tables
Requirements When Running Basic Network Scans + Local Checks
|
# of Hosts Managed by Tenable Security Center |
EC2 Instance Type |
vCPU |
RAM |
|---|---|---|---|
|
1 to 2,500 |
m5.2xlarge |
8 |
32 GB |
|
2,501 to 10,000 |
m5.4xlarge |
16 |
64 GB |
|
10,001 to 25,000 |
m5.8xlarge |
32 |
128 GB |
|
25,001 to 50,000 |
m5.12xlarge |
48 |
192 GB |
|
50,001 or more |
For assistance with large enterprise deployments greater than 50,000 active IP addresses, contact your Tenable representative. |
||
Requirements When Running Basic Network Scans + Local Checks + 1 Configuration Audit
|
# of Hosts Managed by Tenable Security Center |
EC2 Instance Type |
vCPU |
RAM |
|---|---|---|---|
|
1 to 2,500 |
m5.2xlarge |
8 |
32 GB |
|
2,501 to 10,000 |
m5.4xlarge |
16 |
64 GB |
|
10,001 to 25,000 |
m5.8xlarge |
32 |
128 GB |
|
25,001 to 50,000 |
m5.12xlarge |
48 |
192 GB |
|
50,001 or more |
For assistance with large enterprise deployments greater than 50,000 active IP addresses, contact your Tenable representative. |
||
Supported Azure Instance Types
You can install Tenable Security Center in an Azure Virtual Machine (Azure Virtual Image) cloud-based environment that meets all of the following requirements. Tenable recommends the following virtual machine instance types based on your Tenable Security Center deployment size. You may need to increase the storage allocated to the virtual machine instance depending on usage.
Requirements When Running Basic Network Scans + Local Checks
|
# of Hosts Managed by Tenable Security Center |
Virtual Machine Instance |
vCPU |
RAM |
|---|---|---|---|
|
1 to 2,500 |
D8s_v6 |
8 |
32 GB |
|
2,501 to 10,000 |
D16s_v6 |
16 |
64 GB |
|
10,001 to 25,000 |
D32s_v6 |
32 |
128 GB |
|
25,001 to 50,000 |
D48s_v6 |
48 |
192 GB |
|
50,001 or more |
For assistance with large enterprise deployments greater than 50,000 active IP addresses, contact your Tenable representative. |
||
Requirements When Running Basic Network Scans + Local Checks + 1 Configuration Audit
|
# of Hosts Managed by Tenable Security Center |
Virtual Machine Instance |
vCPU |
RAM |
|---|---|---|---|
|
1 to 2,500 |
D8s_v6 |
8 |
32 GB |
|
2,501 to 10,000 |
D16s_v6 |
16 |
64 GB |
|
10,001 to 25,000 |
D32s_v6 |
32 |
128 GB |
|
25,001 to 50,000 |
D48s_v6 |
48 |
192 GB |
|
50,001 or more |
For assistance with large enterprise deployments greater than 50,000 active IP addresses, contact your Tenable representative. |
||
Supported Google Cloud Platform (GCP) Instance Types
You can install Tenable Security Center in a GCP cloud-based environment that meets all of the following requirements. Tenable Security Center uses a balance of networking and compute resources and requires persistent storage for proper operation. Tenable recommends the following GCP instance types based on your Tenable Security Center deployment size.
Requirements When Running Basic Network Scans + Local Checks
|
# of Hosts Managed by Tenable Security Center |
GCP Instance Type |
vCPU |
RAM |
|---|---|---|---|
|
1 to 2,500 |
c4a-standard-8 |
8 |
32 GB |
|
2,501 to 10,000 |
c4a-standard-16 |
16 |
64 GB |
|
10,001 to 25,000 |
c4a-standard-32 |
32 |
128 GB |
|
25,001 to 50,000 |
c4a-standard-48 |
48 |
192 GB |
|
50,001 or more |
For assistance with large enterprise deployments greater than 50,000 active IP addresses, contact your Tenable representative. |
||
Requirements When Running Basic Network Scans + Local Checks + 1 Configuration Audit
|
# of Hosts Managed by Tenable Security Center |
GCP Instance Type |
vCPU |
RAM |
|---|---|---|---|
|
1 to 2,500 |
c4a-standard-8 |
8 |
32 GB |
|
2,501 to 10,000 |
c4a-standard-16 |
16 |
64 GB |
|
10,001 to 25,000 |
c4a-standard-32 |
32 |
128 GB |
|
25,001 to 50,000 |
c4a-standard-48 |
48 |
192 GB |
|
50,001 or more |
For assistance with large enterprise deployments greater than 50,000 active IP addresses, contact your Tenable representative. |
||
External PostgreSQL
Deployments exceeding 100,000 active IPs require an external PostgreSQL instance. Repository data, trending results, and configuration data are stored in PostgreSQL. Size the external PostgreSQL instance using the External PostgreSQL Requirements table, and account for growth as scan and configuration data accumulates over time. The disk totals in this section cover the Tenable Security Center host only and do not include the external PostgreSQL instance.
Disk Partition Requirements
Note: When you upgrade to or install Tenable Security Center version 6.10.x and run the RPM from the /tmp folder, you must have at least 10 GB of space in the /tmp folder if the /tmp folder is in its own partition. If the /tmp folder does not have enough space, the installation or upgrade fails.
Tenable Security Center installs into /opt/sc. Tenable highly recommends that you create the /opt directory on a separate disk partition. If you want to increase performance, consider using two disks: one for the operating system and one for the system deployed to /opt.
Tenable strongly recommends using high-performance disks. Tenable Security Center is a disk-intensive application and using disks with high read/write speeds, such as SSDs, results in the best performance.
If required disk space exists outside of the /opt file system, mount the desired target directory using the command mount –-bind <olddir> <newdir>. Make sure that the file system is automatically mounted on reboot by editing the /etc/fstab file appropriately.
Note: Tenable Security Center does not support using symbolic links for /opt/sc/. You can use symbolic links within /opt/sc/ subdirectories if instructed by Tenable Security Center documentation or Tenable Support.
Deploying Tenable Security Center on a server configured with RAID disks can also dramatically boost performance.
Tip:Tenable does not require RAID disks for even our largest customers. However, in one instance, response times for queries with a faster RAID disk for a customer with more than 1 million managed vulnerabilities moved from a few seconds to less than a second.
Network Interface Requirements
You can install Tenable Security Center in externally connected or air-gapped environments. For more information about special considerations for air-gapped environments, see Considerations for Air-Gapped Environments.
Gigabit or faster network cards are recommended for use on the Tenable Security Center server. This is to increase the overall performance of web sessions, emails, and other network activities.