11.4.1 Penetration testing methodology defined
A penetration testing methodology is defined, documented, and implemented covering industry-accepted approaches, CDE perimeter coverage, application-layer and network-layer tests, and exploitation of vulnerabilities.
5
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Pen test methodology document referencing NIST 800-115 or OWASP · Document repository
- Scope statement covering CDE perimeter and critical systems · Policy repository / GRC workspace
- Test plan including app and network layer · Policy repository / GRC workspace
- Tester qualifications and certifications · Document repository
- Engagement letter · 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
- No methodology
- Scope misses critical systems
- Tester qualifications absent
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.3.2.1 External scans after significant change · 11.4.2 Internal penetration testing annually