8000 Update docs/programs/retesting.md · dextemath/docs.hackerone.com@14726de · GitHub
[go: up one dir, main page]

Skip to content

Commit 14726de

Browse files
Update docs/programs/retesting.md
Co-authored-by: Martijn Russchen <martijn@hackerone.com>
1 parent 9166eb9 commit 14726de

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/programs/retesting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ id: "programs/retesting"
66

77
As programs receive vulnerability reports and work on deploying fixes, they need proof that their vulnerabilities have actually been fixed. Retesting is a good way to secure the protection of your asset’s data by asking hackers to verify whether a fix has been made. With retesting, you can elect to have hackers retest your vulnerabilities to verify the fixes.
88

9-
> HackerOne Response programs will have access to triage retesting, where HackerOne's triage team will retest the vulnerabilities to verify the fixes instead of hackers.
9+
> Retesting for HackerOne Response programs will be available through our triage services, where HackerOne's triage team will retest the vulnerabilities to verify the fixes instead of hackers.
1010
1111
### How it Works
1212
To have hackers retest a vulnerability:

0 commit comments

Comments
 (0)
0