You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/programs/pentests.md
+4-49Lines changed: 4 additions & 49 deletions
Original file line number
Diff line number
Diff line change
@@ -15,54 +15,11 @@ Here are the steps outlining the process of pentests:
15
15
2. HackerOne reviews all applicants and decides which hackers meet the criteria to join the pentest community.
16
16
3. Hackers that are accepted into the pentest community are able to view available pentest opportunities from programs offering pentests.
17
17
4. When hackers find a pentest they want to partcipate in, they submit an application to participate in the pentest.
18
-
5. HackerOne looks at all applicants and forms a pentest team, which consists of 3 pentesters and 1 pentest lead.
19
-
6. Once the pentest team is formed, pentesters have 33 hours to complete the pentest.
20
-
7. After testing has been completed, the lead pentester will draft and submit a summary report of their findings.
21
-
8. Once the vulnerabilities have been fixed, the pentest team will retest the vulnerabilities to make sure they're fixed.
18
+
5. HackerOne looks at all applicants and forms a pentest team.
19
+
6. After testing has been completed, the lead pentester will draft and submit a summary report of their findings.
20
+
7. Once the vulnerabilities have been fixed, the pentest team will retest the vulnerabilities to make sure they're fixed.
22
21
23
-
### Set up
24
-
25
-
Once the feature has been enabled for your program, to set up your pentests:
26
-
1. Go to the **Pentests** tab on your program page.
27
-
2. Click **Create pentest**.
28
-
3. Fill out these pentest details:
29
-
30
-
Field | Details
31
-
----- | --------
32
-
Name | The name of the pentest.
33
-
Industry | Select the industry the pentest is associated with.
34
-
Description | The description of the pentest.
35
-
Visibility | You can choose to have your pentest be: <li>Visible in the directory<li>Not visible in the directory <br><br> Pentesters won’t be able to see and apply to your pentest until it’s visible in the directory.
36
-
Slack workspace URL | Enter your slack workspace URL that’ll click a link to your pentest, and it’ll direct them to slack where they can be directed to. <br><br>You can leave this field empty so that no links will be shown to the pentesters.
37
-
38
-
4. Set the schedule for your pentest with these fields:
39
-
40
-
Field | Details
41
-
----- | -------
42
-
Scheduled dates | Choose the dates you want the pentest to begin and end.
43
-
Timezone | The timezone you want the pentest to begin at.
44
-
45
-
5. Set the contract for your pentest with these fields:
46
-
47
-
Field | Details
48
-
----- | -------
49
-
Hour cap (per pentester) | Set the maximum hour cap for every pentester. Each pentester’s hours are capped to prevent pentesters from taking advantage.
50
-
Lead pentester reward | Set the amount you want the lead pentester to receive.
51
-
Non-lead pentester reward | Set the reward amount for the non-lead pentester reward.
52
-
53
-
6. Click **Go to next step**.
54
-
7. Click **Create asset** to add assets to your pentest scope.
55
-
8. Select **+Add to scope** for the assets you want to add to your pentest scope in the **Add assets to pentest scope section**.
56
-
9. Select a **Preferred Methodology** for each asset. The methodology you choose will apply the appropriate pentest check for the asset. You can choose from:
57
-
58
-
<li> HackerOne Web Security Checklist
59
-
<li> HackerOne iOS Security Checklist
60
-
<li> HackerOne Android Security Checklist
61
-
<li> HackerOne Executable Security Checklist
62
-
63
-
10. Click **Save changes**.
64
-
65
-
Your new pentest will be listed on the **Pentests** tab of your security page.
22
+
After pentesting has been enabled for your program, your new pentest will be listed on the **Pentests** tab of your security page.
66
23
67
24
### Edit/View Pentests
68
25
To edit or view your pentests:
@@ -78,5 +35,3 @@ Running | Pentesters are actively working on the pentest.
78
35
Report due | The testing window has finished but the report is not completed yet.
79
36
Completed | A summary report has been submitted and the pentest is finished.
80
37
Archived | A past pentest that’s no longer active.
0 commit comments