EvidenceSheet
BSI C5 (121-criteria catalogue) · C5: Operations

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, initiating improvements and verifying that those improvements worked.

Source: BSI C5 (121-criteria catalogue), OPS-20. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open BSI C5 (121-criteria catalogue) in the compliance library.

The edition of the catalogue is not stamped here; check the edition your attestation is issued against.

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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • 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

  • Quarterly metrics pack covering mean time to remediate and deadline compliance · Policy repository / GRC workspace
  • Improvement action register with named owners and due dates · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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