SEC11-BP03 Perform regular penetration testing
Conduct authorised penetration tests against applications and infrastructure on at least an annual cadence and after significant change, within AWS testing policy.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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
- Pen test reports · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Remediation tracker · Policy repository / GRC workspace
- Scope and methodology document · Policy repository / GRC workspace
- AWS notification or policy compliance · 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
- pen tests skipped or scope narrowed
- findings never remediated
- no retest
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 sheetSEC11-BP02 Automate testing throughout the development and release lifecycle · SEC11-BP04 Conduct code reviews