11.4.3 External penetration testing annually
External penetration testing is performed at least once every 12 months and after any significant infrastructure or application upgrade or change.
5
artefacts
1
held by a system
2
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
- Findings tracker and remediation tickets · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Annual external pen test report by qualified third party · Vendor register / contract repository
- Re-test evidence · Document repository
governing documentDocuments that govern the control
- Engagement letter establishing independence · Document repository
- Statement of work · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Ticketing / ITSM on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Internal team performed external test
- Findings open
- No re-test
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.2 Internal penetration testing annually · 11.4.4 Pen test findings remediated