|
| 1 | +--- |
| 2 | +title: "Security Checks" |
| 3 | +path: "/hackers/security-checks.html" |
| 4 | +id: "hackers/security-checks" |
| 5 | +--- |
| 6 | + |
| 7 | +Checklists are a way for organizations to meet compliance requirements by enlisting hackers to check for specific vulnerabilities on the OWASP top 10 list. Organizations that opt-in to using checklists will receive a compliance report that they can submit to certify their status among independent and industry compliance frameworks. |
| 8 | + |
| 9 | +> **Note:** This feature is in beta and only accessible to select hackers. |
| 10 | +
|
| 11 | +### How it works |
| 12 | +To participate in a security check: |
| 13 | + |
| 14 | +1. Go to a program’s **Security Checks** tab on their security page. The security checks tab is only available if the program has opted into compliance. |
| 15 | + |
| 16 | + |
| 17 | + |
| 18 | +2. Click **View Details** for the task that you’re interested in on the checklist. |
| 19 | +3. Review the description, instruction, and scope for the task. |
| 20 | +4. Select **Claim this check** if you’re interested in completing the task. |
| 21 | + * You can claim 1 check per program at a time. After you've submitted your results, you can claim another check for that same 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. |
| 22 | + |
| 23 | + |
| 24 | + |
| 25 | +5. Select **Submit results** on the Security Checks page of the program when you’re ready to submit your findings. |
| 26 | + |
| 27 | + |
| 28 | + |
| 29 | +6. Input your findings in the required fields on the submission form. |
| 30 | + |
| 31 | + |
| 32 | + |
| 33 | +7. *(Optional)* Submit a report and link it to your results if you find vulnerabilities during your check. |
| 34 | + |
| 35 | + |
| 36 | + |
| 37 | +8. Click **Submit**. |
| 38 | + |
| 39 | +Once you’ve submitted your results, HackerOne will review your findings. If your findings aren’t approved, your check will be marked as *Rejected*. If your check is rejected, you can reclaim the security check under **Hacker Dashboard > Security Checks**. |
| 40 | + |
| 41 | + |
| 42 | + |
| 43 | +If your check is approved, you’ll automatically be paid the reward amount. |
| 44 | + |
| 45 | + |
| 46 | + |
| 47 | +### Managing Security Checks |
| 48 | + |
| 49 | +You can manage your claimed security checks on the Security Checks tab under your Hacker Dashboard. |
| 50 | + |
| 51 | + |
| 52 | + |
| 53 | +You can also keep track of your Security Check rewards on your Hacker Dashboard. |
| 54 | + |
| 55 | + |
| 56 | + |
| 57 | +### Releasing a Security Check |
| 58 | +If you decide that you no longer want to complete a security check, you can release the check by clicking **Release check** at the bottom of the security check submission page. Keep in mind that once you release the check, other hackers will be able to claim the check and any work you’ve done won’t be saved. |
| 59 | + |
| 60 | + |
| 61 | + |
| 62 | + |
0 commit comments