C1 provides identity governance and just-in-time provisioning for Rapid7. Integrate your Rapid7 instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.
This connector works with Rapid7 products available on the Command Platform API (formerly Insight Platform API). Products that use a separate local API — such as the InsightVM console — are not supported.
Configuring the connector requires you to pass in information from Rapid7. Gather these configuration details before you move on.
A user with administrator permissions in Rapid7 must generate the API key. The connector requires a personal API key (user key), not an organization API key. Organization keys only provide access to Rapid7 capability APIs and will cause the connector to fail with permission errors.
Here’s the information you’ll need:
API Key
Region
See the Rapid7 docs for information on how to acquire credentials: View the documentation
The Connector Administrator or Super Administrator role in C1
Access to the set of Rapid7 configuration information gathered by following the instructions above
Cloud-hosted
Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Integrations > Connectors and click Add connector.
2
Search for Rapid7 and click Add.
3
Choose how to set up the new Rapid7 connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
4
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
5
Click Next.
6
Find the Settings area of the page and click Edit.
7
Enter the configuration information from the previous section.
8
Click Save.
9
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
That’s it! Your Rapid7 connector is now pulling access data into C1.
Follow these instructions to use the Rapid7 connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.
In C1, navigate to Integrations > Connectors > Add connector.
2
Search for Baton and click Add.
3
Choose how to set up the new Rapid7 connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
4
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
5
Click Next.
6
In the Settings area of the page, click Edit.
7
Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.
Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
2
Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the rapid7 connector to. rapid7 data should be found on the Entitlements and Accounts tabs.
That’s it! Your Rapid7 connector is now pulling access data into C1.
