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

Skip to content

Commit 2f3da14

Browse files
committed
typo fixed
1 parent 106154a commit 2f3da14

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/programs/pentests.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ In a penetration test (pentest), authorized hackers simulate a cyberattack on a
1313
Here are the steps outlining the process of pentests:
1414
1. Fill out the scoping questionnaire provided by your Account Manager. (*~30 minutes*)
1515
2. You'll work with one of HackerOne's Solutions Architects to confirm the scope of the engagement, ensure login credentials/assets are ready for testing, and set up your pentest. HackerOne will look at all pentest applicants and form the best pentester team for your pentest based on the skills required for the specified scope. (*~1 week*)
16-
3. During the testing perioed you'll be able to view and begin remediating any found vulnerabilities immediately in the platform or via any issue tracking integrations that are set up. (*2 weeks*)
16+
3. During the testing period you'll be able to view and begin remediating any found vulnerabilities immediately in the platform or via any issue tracking integrations that are set up. (*2 weeks*)
1717
4. After testing has been completed, the lead pentester will draft and provide a summary report of the team's findings. (*~1 week*)
1818
5. Once the vulnerabilities have been remediated, the pentest team will retest the vulnerabilities to make sure they’re fixed. (*60 days from the conclusion of testing*)
1919

0 commit comments

Comments
 (0)