Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 8859d8f

Browse files
Merge pull request Hacker0x01#600 from Hacker0x01/brinqa-integration
Add Brinqa Integration Doc
2 parents e078da0 + e60b07d commit 8859d8f

File tree

4 files changed

+44
-0
lines changed

4 files changed

+44
-0
lines changed

docs/programs/brinqa-integration.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: "Brinqa Integration"
3+
path: "/programs/brinqa-integration.html"
4+
id: "programs/brinqa-integration"
5+
---
6+
7+
With the Brinqa integration, you can push all of your HackerOne submissions to Brinqa so that you can track all of your vulnerability reports on Brinqa.
8+
9+
The HackerOne connector requires an API ID and API Key to authenticate. Directions for creating these can be found [here](/programs/api-tokens.html).
10+
11+
Once you have created your API ID and API Key, you can begin setting up the integration with Brinqa.
12+
13+
1. Log in to your Brinqa account
14+
2. Navigate to data sources
15+
3. Create a new connector by selecting the HackerOne connector.
16+
4. Enter the API ID and Key from HackerOne in the Connector Properties
17+
5. Click Update
18+
![Connector Properties](./images/brinqa-connector-properties.png)
19+
20+
Once you have the connection set up, you can begin configuring any custom data mapping you would like to have. HackerOne data will be synced to Brinqa’s “Activity Report” by default. Use the Attribute Mappings table to add or remove attributes from the Brinqa mapping.
21+
![Attribute Mapping](./images/brinqa/attribute-mapping.png)
22+
23+
You can also set up a sync schedule and choose which data will apply.
24+
![Sync Schedule](./images/brinqa/sync-schedule.png)
25+
26+
Within Brinqa, navigate to the data sources and create a new connector by selecting the HackerOne connector.
27+
28+
### How the Integration Works
29+
After your Brinqa integration has been set up:
30+
1. Change the action picker to **Change state > Triaged** in your report.
31+
32+
![Integrations](./images/add-integration-reference.png)
33+
34+
2. Click **Add reference to issue tracker**.
35+
3. Make sure your Brinqa integration is selected.
36+
37+
![Integration](./images/issue-tracker-reference.png)
38+
39+
4. Click **Generate escalation**. You’ll be taken to your Brinqa account where the report is pre-populated.
40+
5. Submit the issue to create the report in Brinqa.
41+
6. Copy the Brinqa report issue number and paste it in the **Reference ID** field back in the HackerOne.
42+
7. Click **Create** to create a direct reference link to the issue in Brinqa.
43+
44+
Once you’ve set up the HackerOne connector and configured the integration, data will be automatically pulled from HackerOne using the schedule you configured. All reports in the New and Triaged states will be imported in the Brinqa platform as open issues. This integration will not push any updates made in the Brinqa platform back to HackerOne. When you delete the connector, all data imported by the connector will also be deleted.
Loading
Loading
326 KB
Loading

0 commit comments

Comments
 (0)