11.4.2 Internal penetration testing annually
Internal penetration testing is performed at least once every 12 months and after any significant infrastructure or application upgrade or change.
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
- Annual internal pen test report · Document repository
- Post-change pen test reports · Document repository
- Re-test evidence · Document repository
governing documentDocuments that govern the control
- Tester engagement letters · Document repository
- Findings remediation tracker · Document repository
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
- Tests not annual
- Post-change tests skipped
- Findings open
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.1 Penetration testing methodology defined · 11.4.3 External penetration testing annually