8000 Error corrections · Somnn/docs.hackerone.com@d525e6e · GitHub
[go: up one dir, main page]

Skip to content

Commit d525e6e

Browse files
committed
Error corrections
IBM Resilient is now known as IBM Security SOAR. Menu path for proof of compliance changed
1 parent 4c53227 commit d525e6e

File tree

5 files changed

+35
-35
lines changed

5 files changed

+35
-35
lines changed

docs/programs/ibm-resilient-integration.md

Lines changed: 0 additions & 30 deletions
This file was deleted.
Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
title: "IBM Security SOAR"
3+
path: "/programs/ibm-security-soar.html"
4+
id: "programs/ibm-security-soar"
5+
---
6+
7+
With the IBM Security SOAR web URL integration, you can push all of your HackerOne submissions to Security SOAR so that you can track all of your vulnerability reports on Security SOAR.
8+
9+
In order to configure the IBM Security SOAR integration for your team, [contact HackerOne](https://support.hackerone.com/hc/en-us/requests/new) with the following information:
10+
11+
* The base URL
12+
* The fields
13+
14+
With all of the provided information, HackerOne will be able to set up your request integration. You’ll get an email notification letting you know that your integration has been set up within 1-2 business days.
15+
16+
### How the Integration Works
17+
After your Security SOAR integration has been set up:
18+
1. Change the action picker to **Change state > Triaged** in your report.
19+
20+
![integrations](./images/add-integration-reference.png)
21+
22+
2. Click **Add reference to issue tracker**.
23+
3. Make sure your Security SOAR integration is selected.
24+
25+
![integration](./images/issue-tracker-reference.png)
26+
27+
4. Click **Generate escalation**. You’ll be taken to your Security SOAR account where the report is pre-populated.
28+
3. Submit the issue to create the report in Security SOAR.
29+
4. Copy the Security SOAR report issue number and paste it in the **Reference ID** field back in the HackerOne.
30+
5. Click **Create** to create a direct reference link to the issue in Security SOAR.

docs/programs/proof-of-compliance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ These are some of the security standards that can be met with the statement of a
1414
If you’re a federal program that needs to comply with CISA BOD 20-21, you can choose to download the Program performance per asset CSV file and input the data into CyberScope.
1515

1616
To generate your proof of compliance report:
17-
1. Navigate to **Program Settings > Program > Customization > Proof of Compliance**.
17+
1. Navigate to **Program Settings > Program > Reports > Proof of Compliance**.
1818
2. Select the dates that you would like the report to reflect.
1919
3. Select the documents you want to include in the report. You can choose from:
2020

docs/programs/supported-integrations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,11 +53,11 @@ HackerOne currently supports these integrations:
5353
</div>
5454
<div class="logo-text">HackEDU</div>
5555
</a>
56-
<a class="integration-button" href="ibm-resilient.html">
56+
<a class="integration-button" href="ibm-security-soar.html">
5757
<div class="logo">
5858
<img src="./images/ibm_resilient_logo.png" />
5959
</div>
60-
<div class="logo-text">IBM Resilient</div>
60+
<div class="logo-text">IBM Security SOAR</div>
6161
</a>
6262
</div>
6363

src/pages/programs/programs-nav.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -171,8 +171,8 @@
171171
path: /programs/gitlab-integration.html
172172
- title: HackEDU
173173
path: /programs/hackedu-integration.html
174-
- title: IBM Resilient
175-
path: /programs/ibm-resilient.html
174+
- title: IBM Security SOAR
175+
path: /programs/ibm-security-soar.html
176176
- title: Jira
177177
path: /programs/jira-integration.html
178178
items:

0 commit comments

Comments
 (0)
0