8000 Merge pull request #891 from BergenMatthias/master · csit-github/docs.hackerone.com@c837964 · GitHub
[go: up one dir, main page]

Skip to content

Commit c837964

Browse files
Merge pull request Hacker0x01#891 from BergenMatthias/master
2 parents fb2529d + a600e46 commit c837964

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/hackers/badges.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Cryptolestes | Solved a HackerOne Capture The Flag challenge
3030
Diversity | Reported bugs to 5, 20, or 50 different teams.<br><i>There are multiple stages of this badge. You receive a level of this badge whenever you report bugs to 5, 20, and 50 different teams.</i>
3131
Good Samaritan | Resolved a report with a team that doesn't pay bounties
3232
Greybeard | Submitted valid reports in 3, 6, or 12 months in a row.<br><i>There are multiple stages of this badge. You receive a level of this badge whenever you submit valid reports in 3, 6, and 12 months in a row.</i>
33-
Hack The Box Bug Bounty Hunter | [Connect your HackerOne profile with Hack The Box](https://docs.hackerone.com/hackers/external-services/hack-the-box.html) using your student ID and complete the Bug Bounty Hunter path on Hack The Box
33+
Hack The Box Bug Bounty Hunter | [Connect your HackerOne profile with Hack The Box](https://docs.hackerone.com/hackers/hack-the-box.html) using your student ID and complete the Bug Bounty Hunter path on Hack The Box
3434
Hack The World Badass | Reported 10, 20, or 50 valid issues during Hack the World.<br><i>There are multiple stages of this badge. You receive a level of this badge whenever you submit 10, 20, and 50 valid reports.
3535
Hacking Hackers | Hacked HackerOne
3636
Happy Feat | Suggested a feature that was implemented on HackerOne

docs/hackers/security-checks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ To participate in a security check:
1919
3. Click **Claim security check** when you’ve found a security check you want to work on.
2020
<ul><li> You can claim one check per program at a time (once you’ve submitted results, you can claim another check for that program). Once you’ve claimed a check, you’ll have 72 hours to complete it. For each security check, you must test all assets in scope for the relevant vulnerability type.</ul>
2121

22-
4. Go to a program’s **Security Checks** tab on their security page. Note: The **Security checks** tab is only available if the program has opted into compliance.
22+
4. Go to a program’s **Security Checks** tab on their security page. Note: The **Security Checks** tab is only available if the program has opted into compliance.
2323
5. Submit your findings by filling out the submission form.
2424

2525
![security check submission form](./images/security-checks-12.png)

0 commit comments

Comments
 (0)
0