CA-8 Penetration testing
Requires penetration testing to be conducted on organization-defined systems or components at an organization-defined frequency, so that control effectiveness is tested by simulated adversary activity rather than by insp
4
artefacts
0
held by a system
2
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
- Penetration test report with findings, severity and evidence · Vulnerability scanner / patch tooling
- Remediation and re-test records for findings raised · Document repository
governing documentDocuments that govern the control
- Defined testing frequency and the systems or components in scope · Policy repository / GRC workspace
- Rules of engagement and scope agreement for each test · Vendor register / contract 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
- Scope narrowed to the external perimeter so internal paths are never tested
- Testing performed once at go live and not repeated at the defined frequency
- Findings reported but not tracked to closure or re-tested
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 sheetCA-7 Continuous monitoring · CA-9 Internal system connections