System Requirements
The following system requirements are necessary to ensure you have the best experience.
Hardware requirements
The Security Console and Scan Engine hardware requirements are different because the Security Console uses significantly more resources.
The Security Console does not support running in a container. However, the Scan Engine is available as a container image on Docker Hub.
Reserved Memory on Virtual Machines
If you intend to deploy to a virtual machine, ensure that you provision the virtual machine with sufficient reserved memory according to the system requirements. The reserved memory value must match the allocated memory. For example, if you've allocated 32GB, set the reserved memory to 32GB. Configuring a virtual machine with shared memory may cause negative performance impact including out of memory events.
Security Console requirements:
At this time, we only support x86_64 architecture.
| Asset volume | Processor | Memory | Storage |
|---|---|---|---|
| 5,000 | 4 cores | 16 GB | 1 TB |
| 20,000 | 12 cores | 64 GB | 2 TB |
| 150,000 | 12 cores | 128 GB | 4 TB |
| 400,000 | 12 cores | 256 GB | 8 TB |
Scan Engine requirements:
At this time, we only support x86_64 architecture.
| Asset volume per day | Processor | Memory | Storage |
|---|---|---|---|
| 5,000 assets/day | 2 cores | 8 GB | 100 GB |
| 20,000 assets/day | 4 cores | 16 GB | 200 GB |
Operating Systems
We require an English operating system with English/United States regional settings.
64-bit versions of the following platforms are supported:
| Platform | Versions |
|---|---|
| Linux |
|
| Microsoft Windows |
|
| RedHat |
|
| CentOS |
|
Browsers
We support the most recent version of the following browsers:
- Google Chrome (Recommended)
- Mozilla Firefox
- Mozilla Firefox ESR
- Microsoft Edge
Firewall requirements
Security Console firewall requirements:
You must configure your firewall rules to allow outbound connectivity using Port 443. This ensures you can successfully upload data from the Security Console to the Insight Platform.
| Region | Region URL | S3 (Agent Downloads only) |
|---|---|---|
| United States - 1 | us.api.endpoint.ingress.rapid7.com us.deployment.endpoint.ingress.rapid7.com us.exposure-analytics.insight.rapid7.com | s3.amazonaws.com |
| United States - 2 | us2.api.endpoint.ingress.rapid7.com us2.deployment.endpoint.ingress.rapid7.com us2.exposure-analytics.insight.rapid7.com | s3.us-east-2.amazonaws.com |
| United States - 3 | us3.api.endpoint.ingress.rapid7.com us3.deployment.endpoint.ingress.rapid7.com us3.exposure-analytics.insight.rapid7.com | s3.us-west-2.amazonaws.com |
| Europe | eu.api.endpoint.ingress.rapid7.com eu.deployment.endpoint.ingress.rapid7.com eu.exposure-analytics.insight.rapid7.com | s3.eu-central-1.amazonaws.com |
| Canada | ca.api.endpoint.ingress.rapid7.com ca.deployment.endpoint.ingress.rapid7.com ca.exposure-analytics.insight.rapid7.com | s3.ca-central-1.amazonaws.com |
| Japan | ap.api.endpoint.ingress.rapid7.com ap.deployment.endpoint.ingress.rapid7.com ap.exposure-analytics.insight.rapid7.com | s3-ap-northeast-1.amazonaws.com s3.ap-northeast-1.amazonaws.com |
| Australia | au.api.endpoint.ingress.rapid7.com au.deployment.endpoint.ingress.rapid7.com au.exposure-analytics.insight.rapid7.com | s3-ap-southeast-2.amazonaws.com s3.ap-southeast-2.amazonaws.com |
For additional IP addresses for each region see Connectivity requirements.
You must also allow the Security Console to make outbound connections to updates.rapid7.com on Port 443. The Security Console connects to updates.rapid7.com regularly to check for new product versions (every 6 hours) and vulnerability/policy content (every 2 hours). With every connection, the console uploads a JSON file containing license and usage information that helps Rapid7 understand how the Security Console is being used. This upload does not contain any vulnerability assessment data from your assets or any other sensitive information on your environment.
Scan Engine firewall requirements:
If firewalls are present on your network, make sure you whitelist the necessary ports for your Security Console and Scan Engine host according to the communication method of your choice. Consult the following table for port whitelist requirements.
| Source | Destination | Port | Protocol | |
|---|---|---|---|---|
| Console-to-Engine | Console | Scan Engine | 40814 | TCP |
| Engine-to-Console | Engine | Console | 40815 | TCP |
Ports
The ports shown in this table are the default ports used by the Security Console and Scan Engine. If you modify these default ports during the deployment procedure, make sure your firewall rules match your port modifications.