# BSI C5:2020 OPS-17 — Logging and Monitoring - Availability of the Monitoring Software - Source: https://support.icompaas.com/compliance/bsi-c5-2020/ops-17-logging-and-monitoring-availability-of-the-monitoring-software - Section: [Compliance](https://support.icompaas.com/compliance) › [BSI C5:2020 (Cloud Computing Compliance Criteria)](https://support.icompaas.com/compliance/bsi-c5-2020) › Operations Security (OPS) - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **BSI C5:2020**·Criterion `OPS-17`·high·Component: **Operations Security** ## What this control requires > Monitors logging and monitoring system components, automatically reporting failures to responsible departments for prompt action. Ensures continuous operation of monitoring tools to detect threats and protect cloud customer data effectively. > > — BSI C5:2020, Criterion OPS-17 ### In plain English Monitors logging and monitoring system components, automatically reporting failures to responsible departments for prompt action. In practice, this means you can prove you application cloud customer data-level controls on a defined cadence. ## Why it matters BSI C5 is the default cloud-security baseline German public-sector buyers and many DAX-listed enterprises expect; gaps here directly block procurement in the DACH region and frequently appear as must-have items in EU public-tender documents. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A C5 attesting auditor (under ISAE 3000 / IDW PS 860) tests both the design and — for a Type 2 — the operating effectiveness over the attestation period. For each criterion they look for both the Basic and any in-scope Additional objectives. Within **Operations Security**, the assessor will trace your implementation back to the catalogue reference (Criterion OPS-17) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Secure Development **Pipeline.** Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline. **Branch protection.** Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence. #### Code Review Testing **Pipeline.** Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this. ### Operational checklist - **Application.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Data.** Document the trigger, the owner and the cadence. - **Secure.** Document the trigger, the owner and the cadence. - **Scope:** cloud customer data, development. ## Evidence to collect - **Code Repo Scan.** Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports. - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Source control pipelines (GitHub, GitLab) enforce SDLC guardrails. Focus: Logging and Monitoring - Availability of the Monitoring Software. ## Common pitfalls - CI security checks set to warn-only; the merge button is faster than the security feedback. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-171 Rev. 3 3.13.13** — Mobile Code](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-13-13-mobile-code) - [**ISO/IEC 27001:2022 A.8.28** — Secure coding](https://support.icompaas.com/compliance/iso-27001-2022/a-8-28-secure-coding) - [**SOC 2 (2017 TSC) CC1.3** — Organizational Structure and Reporting Lines](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc1-3-organizational-structure-and-reporting-lines) - [**GDPR Article 41** — Monitoring of approved codes of conduct](https://support.icompaas.com/compliance/gdpr/article-41-monitoring-of-approved-codes-of-conduct) - [**CIS Controls v8 16.3** — Perform Root Cause Analysis on Security Vulnerabilities](https://support.icompaas.com/compliance/cis-controls-v8/16-3-perform-root-cause-analysis-on-security-vulnerabilities) ## Related controls in BSI C5:2020 - [**Criterion OPS-13** — Logging and Monitoring - Identification of Events](https://support.icompaas.com/compliance/bsi-c5-2020/ops-13-logging-and-monitoring-identification-of-events) - [**Criterion OPS-03** — Capacity Management - Controlling of Resources](https://support.icompaas.com/compliance/bsi-c5-2020/ops-03-capacity-management-controlling-of-resources) - [**Criterion PSS-02** — Identification of Vulnerabilities of the Cloud Service](https://support.icompaas.com/compliance/bsi-c5-2020/pss-02-identification-of-vulnerabilities-of-the-cloud-service) - [**Criterion DEV-04** — Safety training and awareness programme regarding continuous software delivery and associated systems, components or tools.](https://support.icompaas.com/compliance/bsi-c5-2020/dev-04-safety-training-and-awareness-programme-regarding-continuous-software-delivery-and) - [**Criterion OPS-10** — Logging and Monitoring - Concept](https://support.icompaas.com/compliance/bsi-c5-2020/ops-10-logging-and-monitoring-concept) - [**Criterion OPS-16** — Logging and Monitoring - Configuration](https://support.icompaas.com/compliance/bsi-c5-2020/ops-16-logging-and-monitoring-configuration) ## References - [Bundesamt für Sicherheit in der Informationstechnik (BSI) — BSI C5:2020](https://www.bsi.bund.de/EN/Topics/CloudComputing/Compliance_Criteria_Catalogue/Compliance_Criteria_Catalogue_node.html) - Catalogue identifier: `Criterion OPS-17` Topics: application securitylogging monitoringsecure developmentcode review testingcontinuous monitoringdevsecops ## Related compliance guidance - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.