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

Skip to content

Commit 68b0977

Browse files
committed
hackerone clearance
1 parent 997191e commit 68b0977

File tree

4 files changed

+25
-2
lines changed

4 files changed

+25
-2
lines changed

docs/hackers/hackerone-clearance.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
title: "HackerOne Clearance"
3+
path: "/hackers/hackerone-clearance.html"
4+
id: "hackers/hackerone-clearance"
5+
---
6+
7+
#### What is HackerOne Clearance?
8+
HackerOne Clearance is a pool of hackers that have satisfied strict background and identity checks, and are also active and high-performing members of the HackerOne community.
9+
10+
#### What are the benefits of having HackerOne Clearance?
11+
Having HackerOne Clearance makes you eligible to participate in:
12+
* HackerOne Clear programs (programs that require you to have Clearance in order to participate in)
13+
* Live hacking events that require clearance
14+
* [Retesting](/hackers/retesting.html)
15+
16+
#### How does a hacker get HackerOne Clearance?
17+
To obtain HackerOne Clearance, you need to be a member of the HackerOne community that produces high quality findings, acts responsibly and behaves professionally (zero [Code of Conduct](https://hackerone.com/disclosure-guidelines) violations). You’ll specifically be invited to obtain HackerOne Clearance through which you’ll need to agree to a stricter set of terms called the H1 Clear Finder Additional Terms. (These terms build on our regular hacker terms but have stricter confidentiality terms and higher expectations around professional conduct.)
18+
19+
After agreeing to the terms, you’ll need to pass a criminal background check. When the background check comes back without any red flags, you’ll be awarded your Clearance.
20+
21+
><b>Note:</b> The background check is repeated on an annual basis and is required to retain your Clearance.

docs/hackers/retesting.md

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

77
As programs receive vulnerability reports and work on deploying fixes, they need proof that their vulnerabilities have actually been fixed. Asking hackers to verify whether a vulnerability has been fixed is a good way to secure the protection of data. Programs can elect to invite you and other hackers to retest your vulnerabilities to verify fixes.
88

9-
><i>This is a new feature that is currently in the beta phase and only select programs are testing this feature out. If you’re a part of those programs, you may be invited to retest the vulnerability fixes. There’s currently no effect to reputation for participating in the retest. Although there’s no time limit, we recommend you to complete the retest within 24 hours after accepting the invitation.</i>
9+
><i>This is a new feature that is currently in the beta phase and only select programs are testing this feature out. If you’re a part of those programs with [HackerOne Clearance](/hackers/hackerone-clearance.html), you may be invited to retest the vulnerability fixes. There’s currently no effect to reputation for participating in the retest. Although there’s no time limit, we recommend you to complete the retest within 24 hours after accepting the invitation.</i>
1010
1111
If you’re invited to retest a vulnerability, you’ll receive an invitation in your email to retest the report.
1212

docs/programs/retesting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Once your program manager has enabled the feature, to have hackers retest a vuln
2222

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

25-
4 random hackers participating in your program will be invited to retest the report through email.
25+
Four random hackers with HackerOne Clearance participating in your program will be invited to retest the report through email.
2626

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

src/pages/hackers/hackers-nav.yaml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,8 @@
3030
path: /hackers/payments-faqs.html
3131
- title: Manage Notifications
3232
path: /hackers/manage-notifications.html
33+
- title: HackerOne Clearance
34+
path: /hackers/hackerone-clearance.html
3335
- title: Hacker Email Alias
3436
path: /hackers/hacker-email-alias.html
3537
- title: Sessions

0 commit comments

Comments
 (0)