Skip to main content

Rumble

Visualize runZero (previously called Rumble) organizations, users, and assets, map users to employees, discover vulnerable OS assets, and monitor changes through queries and alerts.

Installation​

info

You can configure the runZero integration using either an Account API Key or a single Export Token. The Export Token has more limited, read-only permissions, which limits the data collected in JupiterOne.

Prerequisites​

  • To use the Account API Key method, you must have a runZero Platform (Enterprise) license. The Account API provides read-write access to all account settings and organizations, and it is required to ingest organizations, users, and sites, and to enumerate per-organization export tokens for asset collection.
  • To use the Export Token method, you need an export token for the organization whose data you want to ingest. An export token is read-only and scoped to a single organization, so only that organization's sites and assets are collected.

Account API Key method​

This method is recommended when you have multiple organizations whose data you want to ingest into JupiterOne. It also ingests a larger set of entities than the Export Token method alone. It requires a runZero Platform (Enterprise) license.

Generate an Account API Key​

  1. Sign in to the runZero Console.
  2. In the left navigator, go to Account settings.
  3. In the account API tokens section, create a new Account API token.
  4. Copy the token. You will provide it in JupiterOne as the Rumble Account API Key.

Generate an export token for each organization​

When you use the Account API Key method, the integration automatically collects each organization's export token to ingest that organization's assets. Organizations without an export token will not have their assets ingested.

  1. Sign in to the runZero Console.
  2. In the left navigator, go to Organizations.
  3. Click the organization for which you want to create an export token to open its details page.
  4. Click Edit organization, scroll to the export tokens section, and generate the token.
  5. Repeat for every organization whose assets you want to ingest.

Export Token method​

This method is typically used when you have a single organization whose data you want to populate in JupiterOne. Because an export token is read-only and scoped to one organization, this method ingests only that organization's sites and assets.

Generate an Export Token​

  1. Sign in to the runZero Console.
  2. In the left navigator, go to Organizations.
  3. Click the organization for which you want to create an export token to open its details page.
  4. Click Edit organization, scroll to the export tokens section, and generate the token.
  5. Copy the token. You will provide it in JupiterOne as the Rumble Export Token.

Configuration in JupiterOne​

To install the runZero integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select runZero. Click New Instance to begin configuring your integration.

Creating an instance requires the following:

  • The Account Name used to identify the runZero account in JupiterOne.

  • A Description to help identify the integration instance, if desired.

  • A Polling Interval sufficient for your monitoring needs. You can leave this as DISABLED and run the integration manually.

  • Depending on your authentication preference, provide one of the following credentials:

    • Rumble Account API Key — the Account API Key for the runZero Account API. Skip this field if you are integrating using an Export Token.
    • Rumble Export Token — the Export Token for integrating using only the Export API. Skip this field if you are integrating using an Account API Key.

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.