What evidence do auditors commonly ask for on OPS-07 Data Backup and Recovery - Monitoring?

Backup job status report for a sampled period showing successes, failures and reruns; Ticket trail following a failed job through to successful completion; Alerting rule configuration for backup failure notifications; List of protected objects reconciled against the scheduled job definitions.

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

Failures visible in the backup console but never raised as tickets or owned

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

`OPS-07` Data Backup and Recovery - Monitoring

Watch backup execution through technical and organisational measures and have qualified staff investigate and rectify malfunctions promptly, so the agreed scope, frequency and retention of data backup are still achieved.

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

easy

to go live

Backup / DR tooling

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

Backup job status report for a sampled period showing successes, failures and reruns · Backup / DR tooling
Ticket trail following a failed job through to successful completion · Backup / DR tooling
Alerting rule configuration for backup failure notifications · Backup / DR tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

List of protected objects reconciled against the scheduled job definitions · Policy repository / GRC workspace

First move

Automate the pull from your Backup / DR tooling. Backup job success history and restore-test logs from the backup platform.

Common gaps auditors find

Failures visible in the backup console but never raised as tickets or owned
Jobs reported successful while individual volumes or files were skipped
Alerting configured only for hard failures so silent partial backups pass unnoticed
No responsible owner outside business hours so weekend failures wait until Monday

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-06 Data Backup and Recovery - Concept · OPS-08 Data Backup and Recovery - Regular Testing