OPS-17 Logging and Monitoring - Availability of the Monitoring Software
Monitor the system components used for logging and monitoring themselves, and report their failures automatically and promptly to the responsible departments so the loss of visibility is assessed and the required action taken.
Source: BSI C5 (121-criteria catalogue), OPS-17. 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.
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
- Heartbeat or watchdog configuration that detects a stalled log collector · SIEM / log platform
- Incident record for a monitoring outage with detection and restoration times · Backup / DR tooling
- Log volume trend showing collection gaps and their explanation · SIEM / log platform
periodic reviewEvidence produced at each review
- Availability report for the monitoring platform itself · SIEM / log platform
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- The monitoring platform watched by nothing, so its own outage passes in silence
- Agents that stop sending without any absence alert being generated
- Collector storage exhaustion dropping events with no notification
- No defined maximum acceptable blind period during a monitoring failure
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 sheetOPS-16 Logging and Monitoring - Configuration · OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept