EvidenceSheet

OPS-19 Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests

Commission penetration tests at least annually by qualified internal personnel or external providers, following a documented test methodology across the components identified as relevant in a risk analysis, rating findin

4
artefacts
0
held by a system
2
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 report with scope statement, methodology and dated findings · Vulnerability scanner / patch tooling
  • Qualification or certification records for the testers used · Vulnerability scanner / patch tooling

governing documentDocuments that govern the control

  • Risk analysis that determined which components were placed in scope · Policy repository / GRC workspace
  • Remediation tracker showing closure dates against the agreed time windows · 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

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 sheet

OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept · OPS-20 Managing Vulnerabilities, Malfunctions and Errors - Measurements, Analyses and Assessments of Procedures