EvidenceSheet

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

Measure, analyse and assess the procedures used to handle vulnerabilities and incidents to confirm they remain suitable, appropriate and effective, with accountable departments evaluating results at least quarterly, init

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

  • Quarterly metrics pack covering mean time to remediate and deadline compliance · Vulnerability scanner / patch tooling
  • Minutes of the management review at which those metrics were discussed · Vulnerability scanner / patch tooling
  • Evidence that a previously agreed improvement was verified as effective · Vulnerability scanner / patch tooling

governing documentDocuments that govern the control

  • Improvement action register with named owners and due dates · 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-19 Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests · OPS-21 Involvement of Cloud Customers in the Event of Incidents