Bugcrowd
Visualize Bugcrowd bounty programs and submitted findings, and monitor changes through queries and alerts.
- Installation
- Data Model
Installation
To install the Bugcrowd integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Bugcrowd. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
-
The Account Name used to identify the Bugcrowd 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. -
Your Bugcrowd API Token configured for read access. To generate an API token, log into your Bugcrowd account, navigate to the API Credentials page, specify a descriptive name, and click Create credentials. API tokens are automatically pinned to major version v1. See Bugcrowd's API documentation for more information.
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.
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
Account | bugcrowd_account | Account |
Bounty | bugcrowd_bounty | Program, Control |
Service | bugcrowd_service | Service, Control |
Submission | bugcrowd_submission | Finding |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
bugcrowd_account | PROVIDES | bugcrowd_service |
bugcrowd_account | HAS | bugcrowd_bounty |
bugcrowd_bounty | HAS | bugcrowd_submission |
bugcrowd_service | MANAGES | bugcrowd_bounty |