Visualize BigID data sources, finding objects, and users, map BigID users to employees, and monitor changes through queries and alerts.
- Installation guide
- Big ID data model
For this integration, you will need to create an API Token within BigID. During creation, set the desired expiration period for the token, and copy the token for use within JupiterOne.
For more information on BigID API Token generation, see their documentation.
Configuration in JupiterOne
To install the Rumble integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Rumble. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
The Account Name used to identify the Rumble 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.
Lastly, depending on your authentication preference, input either of the following credentials:
- For configuring the integration with an Account API Key then put the key in the Rumble Account API Key field.
- For configuring the integration with an Export Token, provide the token in the Export Token field.
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 |
The following mapped relationships are created:
|Source Entity ||Relationship ||Target Entity ||Direction|