Big ID
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
Installation
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
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 | bigid_account | Account |
Data Source | bigid_datasource | DataCollection |
PII Object | bigid_pii_object | Record |
User | bigid_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
bigid_account | SCANS | bigid_datasource |
bigid_account | HAS | bigid_user |
bigid_datasource | HAS | bigid_pii_object |
Mapped Relationships
The following mapped relationships are created:
Source Entity _type | Relationship _class | Target Entity _type | Direction |
---|---|---|---|
bigid_account | SCANS | *aws_s3_bucket* | FORWARD |
bigid_datasource | IS | *aws_s3_bucket* | FORWARD |
bigid_pii_object | HAS | *aws_s3_bucket* | REVERSE |