10000 retest updates · lanahkomputer/docs.hackerone.com@db17723 · GitHub
[go: up one dir, main page]
Skip to content

Commit db17723

Browse files
stacyspivastacyspiva
committed
retest updates
1 parent 3e93bda commit db17723

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

‎docs/programs/retesting.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -16,15 +16,15 @@ Once your program manager has enabled the feature, to have hackers retest a vuln
1616
1. Choose a resolved report in your inbox that you want to assign hackers to retest.
1717
2. Change the action picker to <b>Request retest</b>.
1818

19-
![retest-1](./images/retesting-1.png)
19+
![choosing request retest in dropdown](./images/retesting-1.png)
2020

2121
3. Click <b>Request retest</b>.
2222

23-
![retest-2](./images/retesting-2.png)
23+
![request retest button](./images/retesting-2.png)
2424

2525
4 random hackers participating in your program will be invited to retest the report through email.
2626

27-
![retest-3](./images/retesting-3b.png)
27+
![email to see retest invitation](./images/retesting-3b.png)
2828

2929
In addition, the hacker that originally submitted the report will also be invited to participate in the retest.
3030

@@ -36,32 +36,32 @@ When the hacker clicks <b>View retest invitation</b> in the email, they’ll be
3636

3737
Upon acceptance, participating hackers will be able to familiarize themselves with the vulnerability report and check to see that the vulnerability is properly fixed. After they’ve tested the vulnerability, they can click the <b>answer these questions</b> link in the report banner to submit their findings.
3838

39-
![retest-4](./images/retesting-4.png)
39+
![answer these questions link in banner](./images/retesting-4.png)
4040

4141
The hacker will be asked to answer the following questions:
4242
* Are you able to reproduce the vulnerability?
4343
* Are you able to identify a bypass to the fix?
4444

45-
![retest-5](./images/retesting-5b.png)
45+
![retest questionnaire](./images/retesting-5b.png)
4646

4747
If they were able to identify a bypass, they can can submit a new vulnerability report and enter the report ID in the questionnaire.
4848

49-
![retest-6](./images/retesting-6b.png)
49+
![submitting a new report through retest](./images/retesting-6b.png)
5050

5151
Hackers are also asked to provide a short summary of how they retested the vulnerability, and are also able to upload any attachments of their validations.
5252

5353
![summary and screenshots](./images/retesting-6c.png)
5454

5555
Upon submission of the questionnaire, you’ll be notified that a hacker has completed a retest of your report within the report timeline and also through email.
5656

57-
![retest-7](./images/retesting-7.png)
57+
![notification that hacker completed retest](./images/retesting-7.png)
5858

5959
Click on <b>View results</b> to see the status and findings of the retest efforts. If the hacker was able to find a bypass to the vulnerability, you can view the new vulnerability report.
6060

61-
![retest-8](./images/retesting-8.png)
61+
![retest results popup](./images/retesting-8.png)
6262

6363
Hackers that completed the retest will automatically be awarded $100. The payment is a regular bounty payment and the transaction for retesting will show in your billing overview statement.
6464

65-
![retest-9](./images/retesting-9.png)
65+
![billing notification](./images/retesting-9.png)
6666

6767
><i>There’s currently no effect to reputation for verifying vulnerability fixes and there’s also no time limit for hackers to complete the retest.</i>

0 commit comments

Comments
 (0)
0