11.4.4 Pen test findings remediated
Exploitable vulnerabilities and security weaknesses found during penetration testing are corrected, with penetration testing repeated to verify corrections.
5
artefacts
0
held by a system
3
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Re-test reports confirming closure · Document repository
- Sign-off from test owner · Document repository
- Lessons learned records · Document repository
governing documentDocuments that govern the control
- Finding-by-finding remediation tracker · Document repository
- Risk acceptance forms for any unfixed findings · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Findings closed without verification
- No re-test
- Risk acceptances without justification
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet11.4.3 External penetration testing annually · 11.4.5 Segmentation testing