TVM-06 Penetration Testing
Commission penetration testing by independent third parties on a recurring schedule.
4
artefacts
0
held by a system
3
at each review
hard
to go live
Vulnerability scanner / patch tooling
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 reports from independent third parties · Vulnerability scanner / patch tooling
- Evidence of tester independence · Vulnerability scanner / patch tooling
- Findings tracked to remediation with retest evidence · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- The scope tested and how it was chosen · 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
- Testing performed internally and described as independent
- Scope narrowed to avoid the areas most likely to fail
- Findings closed without 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 sheetTVM-05 External Library Vulnerabilities · TVM-07 Vulnerability Identification