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

Skip to content

Commit d94a659

Browse files
committed
added pentests to the progran book
1 parent dbe3069 commit d94a659

File tree

2 files changed

+80
-1
lines changed

2 files changed

+80
-1
lines changed

docs/programs/pentests.md

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
---
2+
title: "Pentest Overview"
3+
path: "/programs/pentests.html"
4+
id: "programs/pentests"
5+
---
6+
7+
In a penetration test (pentest), authorized hackers simulate a cyberattack on a specific application to test how secure the application is. HackerOne pentests are performed by select hackers with skills and experience from the HackerOne community that best match your applications in scope.
8+
9+
> **Note:** To take part in HackerOne pentests, contact your account manager.
10+
11+
### How it works
12+
13+
Hackers wanting to participate in pentests will need to apply to be pentesters through which HackerOne will review all applicants and decide which hackers meet the criteria to join the pentest community. Hackers that are a part of the pentest community will then be able to view available pentest opportunities from programs offering pentests. In order to participate in a pentest, hackers will need to apply to the specific pentest through which HackerOne will form a pentest team, which consists of 3 pentesters and 1 pentest lead.
14+
15+
Once the pentest team is formed, pentesters will have 33 hours to complete the pentest. After testing, the lead pentester will draft and submit a summary report of their findings.
16+
17+
### Set up
18+
19+
Once the feature has been enabled for your program, to set up your pentests:
20+
1. Go to the **Pentests** tab on your program page.
21+
2. Click **Create pentest**.
22+
3. Fill out these pentest details:
23+
24+
Field | Details
25+
----- | --------
26+
Name | The name of the pentest.
27+
Industry | Select the industry the pentest is associated with.
28+
Description | The description of the pentest.
29+
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.
30+
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.
31+
32+
4. Set the schedule for your pentest with these fields:
33+
34+
Field | Details
35+
----- | -------
36+
Scheduled dates | Choose the dates you want the pentest to begin and end.
37+
Timezone | The timezone you want the pentest to begin at.
38+
39+
5. Set the contract for your pentest with these fields:
40+
41+
Field | Details
42+
----- | -------
43+
Hour cap (per pentester) | Set the maximum hour cap for every pentester. Each pentester’s hours are capped to prevent pentesters from taking advantage.
44+
Lead pentester reward | Set the amount you want the lead pentester to receive.
45+
Non-lead pentester reward | Set the reward amount for the non-lead pentester reward.
46+
47+
6. Click **Go to next step**.
48+
7. Click **Create asset** to add assets to your pentest scope.
49+
8. Select **+Add to scope** for the assets you want to add to your pentest scope in the **Add assets to pentest scope section**.
50+
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:
51+
* HackerOne Web Security Checklist
52+
* HackerOne iOS Security Checklist
53+
* HackerOne Android Security Checklist
54+
* HackerOne Executable Security Checklist
55+
56+
10. Click **Save changes**.
57+
58+
Your new pentest will be listed on the **Pentests** tab of your security page.
59+
60+
### Edit/View Pentests
61+
To edit or view your pentests:
62+
1. Go to your program security page.
63+
2. Click on the **Pentests** tab.
64+
3. Select the pentest you want to view. The pentests can be in these different states:
65+
66+
State | Details
67+
----- | -------
68+
Draft | The pentest is not live and is still being written up.
69+
Scheduled | The team is selected and the pentest is scheduled to start.
70+
Running | Pentesters are actively working on the pentest.
71+
Report due | The testing window has finished but the report is not completed yet.
72+
Completed | A summary report has been submitted and the pentest is finished.
73+
Archived | A past pentest that’s no longer active.
74+
75+
4. Click **Edit pentest**.

src/pages/programs/programs-nav.yaml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -246,11 +246,15 @@
246246
items:
247247
- title: FAQs
248248
path: /programs/vpn-faqs.html
249+
- title: Pentests
250+
items:
251+
- title: Pentest Overview
252+
path: /programs/pentests.html
249253
- title: Helpful Tools
250254
items:
251255
- title: Email Forwarding
252256
path: /programs/email-forwarding.html
253257
- title: Embedded Submission Form
254258
path: /programs/embedded-submissions-form.html
255-
- title: Slack Shared Channels
259+
- title: Slack Shared Channels
256260
path: /programs/slack-shared-channels.html

0 commit comments

Comments
 (0)