Collector Requirements

In order to set up a collector the following requirements should be met. If you do not meet these requirements before attempting to set up a collector it may not operate properly. Read the following sections and understand their importance to determine if deploying a collector is right for your organization.

General Requirements and Recommendations

Consider the following before choosing a Collector host:

• DO NOT install a Collector on a host that already runs a Security Console or Scan Engine.
  • Security Consoles and Scan Engines will not function properly if a Collector is present on the same host.
• Only install one Collector per machine, whether physical or virtual.
  • Additionally, Rapid7 recommends that the host be entirely dedicated to the Collector’s use to maximize resource availability.
• Your Collector host must be configured with a Fully Qualified Domain Name (FQDN).

Hardware Requirements and Recommendations

You can install a Collector on a network server or virtual machine that meets the following minimum hardware requirements:

• 2 CPU cores with 2GHz+ on each core
• 8 GB RAM
• 60 GB available disk space

For optimal performance, Rapid7 recommends the following hardware specifications:

Supported Operating Systems

Refer to these tables to view the OS versions that the Collector currently supports and the End-Of-Life (EOL) schedule for each.

Supported Browsers

You need to access your InsightVM web interface in order to retrieve the installer and complete the activation process. To do so, use either of the following supported web browsers:

• Mozilla Firefox (latest stable version)
• Google Chrome (latest stable version)

Networking Requirements

Implementing Collectors for the InsightVM use case requires the following connectivity.

Collector communication with Insight Agents

Since InsightVM implements Collectors as intermediaries between your deployed Insight Agents and the Insight Platform, your Collectors must allow different kinds of traffic from your agents on the following ports:

Collector communication with the Insight Platform

All Collectors must be able to establish outbound connectivity on port 443 to *.endpoint.ingress.rapid7.com and communicate with the domains shown in the Data and Storage (S3) columns of the following table according to your geographic region. For example, for InsightVM subscribers that elect to store their data in Australia, Collectors must be able to communicate with the following endpoints using port 443:

• *.endpoint.ingress.rapid7.com
• au.data.insight.rapid7.com
• s3-ap-southeast-2.amazonaws.com

If you intend to deploy token-based Insight Agents through your Collectors, you also need to allow outbound connectivity from each Collector on port 443 to the endpoint that provides the agent's configuration files. Just like the Data and Storage endpoints in the previous table, you can configure your firewall rules to allow your Collectors to connect to a region-specific version of the Deployment endpoint to meet this requirement:

Collector communication for InsightVM-specific data

Finally, your Collectors must be able to reach out on port 443 and communicate with one of the following InsightVM-specific endpoints according to your geographic region. This endpoint is responsible for displaying your vulnerability assessment data and powers several InsightVM features: