Visualize Rapid7 users, devices, scanners, findings, and vulnerabilities, map Rapid7 users to employees, and monitor changes through queries and alerts.
- Installation guide
- Rapid7 data model
For this integration, you will need to acquire and provide the following within JupiterOne:
- The InsightVM Security Console Socket Address: The publicly-accessible socket (host:port) of your InsightVM Security Console. e.g.
- An InsightVM Username and Password: You will need to use an existing user or create a user that has the Global Administrator Role.
For more information for InsightVM user management, see Rapid7's documentation.
Configuration in JupiterOne
To install the Rapid7 integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Rapid7. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
The Account Name used to identify the Rapid7 account in JupiterOne. Ingested entities will have this value stored in
AccountNametoggle is enabled.
Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration.
Your InsightsVM Security Console Socket Address which is publicly accessible.
The InsightsVM Username and InsightsVM Password of an admin user in the security console.
Click Create once all values are provided to finalize the integration.
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
The following entities are created:
|Resources||Entity ||Entity |
The following relationships are created:
|Source Entity ||Relationship ||Target Entity |