Cloud Requirements
The primary method to deploy Tenable Security Center in a cloud environment is with Tenable Core + Tenable Security Center. For more information, see the Tenable Core User Guide.
However, you can install Tenable Security Center in vendor-supported version of your cloud environment that meets the operating system requirements to run Tenable Security Center.
The following guidelines can help you install Tenable Security Center in an Amazon Elastic Compute Cloud (Amazon EC2) cloud-based environment or an Azure Virtual Machine (Azure Virtual Image) cloud-based environment, but they do not cover all deployment scenarios or cloud environments. For assistance with a different cloud environment, contact Tenable Professional Services.
For recommended cloud instance types and sizing, see Hardware Requirements.
Supported Amazon Machine Images (AMIs)
Tenable provides an AMI for Tenable Core, but not for other cloud deployments without Tenable Core. Tenable supports using the following Amazon Marketplace AMI for Tenable Security Center without Tenable Core:
Configuration considerations:
-
These AMIs may not include Java, but Tenable Security Center requires OpenJDK or the Oracle Java JRE to export PDF reports.
You must install OpenJDK or the Oracle Java JRE onto your AMI before hosting Tenable Security Center. For more information, see Dependencies.
-
These AMIs may configure an SELinux enforcing mode policy, which requires customization to be compatible with Tenable Security Center.
You must use the SELinux sealert tool to identify errors and solutions. For more information, see Customize SELinux Enforcing Mode Policies for Tenable Security Center.
-
You must confirm these AMIs meet all other standard requirements for operating systems. For more information, see Operating System Requirements.
Supported Azure Machine Images
Tenable provides an Azure image for Tenable Core, but not for other cloud deployments without Tenable Core. Tenable supports using the following Azure images for Tenable Security Center:
Configuration considerations:
-
These images may not include Java, but Tenable Security Center requires OpenJDK or the Oracle Java JRE to export PDF reports.
You must install OpenJDK or the Oracle Java JRE onto your image before hosting Tenable Security Center. For more information, see Dependencies.
-
These images may configure an SELinux enforcing mode policy, which requires customization to be compatible with Tenable Security Center.
You must use the SELinux sealert tool to identify errors and solutions. For more information, see Customize SELinux Enforcing Mode Policies for Tenable Security Center.
- You must confirm these images meet all other standard requirements for operating systems. For more information, see Operating System Requirements.
Requirements for Tenable Security Center Services in Tenable Enclave Security
| Service |
# of Hosts Managed by Tenable Security Center |
CPU per pod | Memory per pod | Default pod replicas | Disk space |
|---|---|---|---|---|---|
|
Reporting pod |
1 to 2,500 active IPs |
4 cores | 8 GiB | 1 per report (max 4) | Uses cluster storage dedicated for the pod until report completion |
|
2,501 to 10,000 active IPs |
8 cores | 16 GiB | |||
|
10,001 to 25,000 active IPs |
16 cores | 32 GiB | |||
|
25,001 to 50,000 active IPs |
24 cores | 48GiB | |||
| Job manager pod |
1 to 50,000 active IPs |
4 cores | 4 GiB | 1 | N/A |
External PostgreSQL Requirements
You can install Tenable Security Center configured to work with a PostgreSQL instance managed by you. PostgreSQL is required for certain features. For more information about connecting a PostgreSQL database, see Connect an External PostgreSQL Server.
This is a required configuration if you have more than 100K hosts.
If you set up your PostgreSQL instance in a cloud environment, the following are guidelines for choosing your instance size. Note that the disk space in the following table is only for PostgreSQL data, and does not include any other OS or other dependencies you have.
|
# of Hosts Managed by Tenable Security Center |
AWS |
Azure | Google Cloud Platform (GCP) |
Minimum Disk Space Required for PostgreSQL Data |
|---|---|---|---|---|
|
1 to 2,500 active IPs |
m6g.xlarge |
D4s_v3 |
t2a-standard-4 |
20 GB |
|
2,501 to 10,000 active IPs |
m6g.2xlarge |
D16s_v3 |
t2a-standard-8 |
50 GB |
|
10,001 to 25,000 active IPs |
m6g.4xlarge |
D32s_v3 |
t2a-standard-16 |
100 GB |
|
25,001 to 100,000 active IPs |
m6g.8xlarge |
D48s_v3 |
t2a-standard-32 |
400GB |
|
100,001 to 250,000 active IPs |
m6g.16xlarge |
D64s_v3 |
t2a-standard-48 |
1 TB |