Rumble
Visualize Rumble organizations, users, and assets, map users to employees, discover vulnerable OS assets, and monitor changes through queries and alerts.
- Installation guide
- Rumble data model
Installation
For this integration, you can configure the Rumble integration using either an Account API Key or a single Export Token. The Export Token has more limited read-only permissions which will limit the data that is collected in JupiterOne.
API Key method
This method is recommended for instances where there are multiple organizations that you wish to ingest data into JupiterOne. It also provides a larger set of ingested entities than solely using an Export Token. You must have a Rumble Enterprise License to utilize this method.
To configure this integration via API key, follow the below instructions:
Account API Key Generation
- Navigate to the Rumble Console.
- In the navigation bar, go to
Account
. - On the Account page under the Account API keys section, click Generate API Key.
- A new Account API Key will be created. Copy this key as it will be used in JupiterOne.
Export Token Generation
Next, you'll need to generate an export token for each organization whose assets, services, and wireless data you want to include in the JupiterOne graph. The integration will automatically collect these tokens if they are present. Organizations without export tokens will not have assets, services, or wireless data ingested.
- Navigate to the Rumble Console
- In the navigation bar, go to
Organizations
- Click on the organization in which you want to create an
Export Token
- Press the Generate Export Token button.
- Repeat for all organizations whose data you want to ingest.
Export Token method
This method is typically suggested if there is only a single organization for which you intend to populate data into JupiterOne.
If you wish to utilize an Export Token rather than use API credentials, ensure that you have admin access to the Rumble organization and follow the below steps for obtaining your Export Token for use with JupiterOne.
To generate the Export Token:
- Navigate to the Rumble Console
- In the navigation bar, go to
Organizations
- Click on the organization in which you want to create an
Export Token
- Press the Generate Export Token button.
- Copy your
Export Token
for use in JupiterOne
Finalize 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
tag.AccountName
when theAccountName
toggle 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
DISABLED
and 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.
Next steps
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.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
Account | rumble_account | Account |
Asset | rumble_asset | Device |
Organization | rumble_organization | Organization |
Site | rumble_site | Site |
User | rumble_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
rumble_account | HAS | rumble_organization |
rumble_account | HAS | rumble_site |
rumble_account | HAS | rumble_user |
rumble_organization | HAS | rumble_site |
rumble_site | HAS | rumble_asset |
rumble_user | ASSIGNED | rumble_organization |