What evidence do auditors commonly ask for on OPS-21 Involvement of Cloud Customers in the Event of Incidents?

Notification timeline for a sampled incident showing each update issued to the customer; Contractual communication commitments listing notification intervals and channels; Status page history or portal notices published for the same incident; Closure notice describing the actions taken and any customer follow up required.

What is the most common gap auditors find on OPS-21?

Customers told at the start and at closure with nothing in between during a long incident

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

`OPS-21` Involvement of Cloud Customers in the Event of Incidents

Keep affected cloud customers informed at regular intervals on the status of incidents concerning them, involve them in resolution where appropriate and necessary, and tell them what action was taken once the incident is resolved, all as the contract provides.

Source: BSI C5 (121-criteria catalogue), OPS-21. 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.

artefacts

held by a system

at each review

moderate

to go live

Document repository

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

Status page history or portal notices published for the same incident · Document repository

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Notification timeline for a sampled incident showing each update issued to the customer · Document repository
Contractual communication commitments listing notification intervals and channels · Policy repository / GRC workspace
Closure notice describing the actions taken and any customer follow up required · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Document repository); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Customers told at the start and at closure with nothing in between during a long incident
Only the technical contact notified while the contractual escalation contact is missed
Closure message omits what was actually done, leaving the customer nothing to act on
Notification intervals promised in the contract absent from the incident procedure

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-20 Managing Vulnerabilities, Malfunctions and Errors - Measurements, Analyses and Assessments of Procedures · OPS-22 Testing and Documentation of known Vulnerabilities