These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Penetration Test Management
- Process
- Finding lifecycle
Finding lifecycle
Use the authorized engagement as the boundary for finding work.
Step by step
-
Confirm scope Security Lead
Security Lead checks the client, authorized targets, dates and authorization document.
- Check client, authorized targets, dates and authorization document.
- Updates Engagement scopes
-
Record finding Tester
Tester links the asset issue to its engagement and records severity and evidence.
- Link the asset issue to its engagement and keep severity and evidence.
- Updates Security findings, Engagement scopes
-
Coordinate remediation Security Lead
Security Lead moves an open finding into remediation after the response begins.
- Move an open finding into remediation after the response begins.
- Updates Security findings
-
Retest Tester
Tester reviews the affected asset and recorded evidence before the final outcome.
- Review the affected asset and recorded evidence before the final outcome.
- Updates Security findings
-
Record outcome Security Lead
Security Lead reviews the recorded outcome, keeping Closed distinct from accepted risk.
- Keep closure and accepted risk distinct in the status.
- Updates Security findings
Who does what
Roles and permissions- Security Lead
- , Tester, Admin.
- The named reviewer makes the human decision where this process has a gate.
- Use [roles](/penetration-test-management/roles) to rehearse what each person can see and change.
Set up Penetration Test Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.