HackerOne
Visualize HackerOne bounty programs and findings, and monitor changes through queries and alerts.
- Installation guide
- HackerOne data model
Installation
To use this integration JupiterOne requires an API key, API key name, and the Program handle of your HackerOne program.
HackerOne provides detailed instructions on creating an API token within your HackerOne account. When selecting the programs and groups you want to add, choose Admin
.
Configuration in JupiterOne
To install the HackerOne integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select HackerOne. Click New Instance to begin configuring your integration with the following settings:
Account Name by which you want to identify this HackerOne account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when Tag with Account Name is selected.Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLED
and manually execute the integration.Select a Polling Interval that you feel is sufficient for your monitoring needs. You can leave this as
DISABLED
and manually execute the integration.Enter the API Key and API Key Name to authenticate with HackerOne.
Enter the Program Handle or name of your HackerOne program.
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 |
---|---|---|
Finding | hackerone_report | Finding |
Service | hackerone_program | Service, Assessment |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
hackerone_program | HAS | hackerone_report |
Mapped Relationships
The following mapped relationships are created:
Source Entity _type | Relationship _class | Target Entity _type | Direction |
---|---|---|---|
hackerone_report | HAS | *cve* | FORWARD |
hackerone_report | HAS | *cwe* | FORWARD |