Visualize Bugcrowd bounty programs and submitted findings, and monitor changes through queries and alerts.
- Installation guide
- Bugcrowd data model
The JupiterOne Bugcrowd integration currently only supports the legacy v3 Bugcrowd APIs. You will need to provision API credentials for Bugcrowd's Legacy API version, which is done by adjusting the Default version value to
Legacy. See their documentation for more information.
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
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.
Your Bugcrowd Legacy API Token configured for read access generated from your Bugcrowd account.
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/mapped:
|Source Entity ||Relationship ||Target Entity |