# BSI C5:2020 OPS-20 — Managing Vulnerabilities, Malfunctions and Errors - Measurements, Analyses and Assessments of Procedures - Source: https://support.icompaas.com/compliance/bsi-c5-2020/ops-20-managing-vulnerabilities-malfunctions-and-errors-measurements-analyses-and - 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-20`·high·Component: **Operations Security** ## What this control requires > Quarterly evaluates vulnerability and incident handling procedures for effectiveness, initiating continuous improvements. Ensures robust processes to mitigate risks, maintaining the security and integrity of cloud customer data and services. > > — BSI C5:2020, Criterion OPS-20 ### In plain English Quarterly evaluates vulnerability and incident handling procedures for effectiveness, initiating continuous improvements. In practice, this means you can prove you risk 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-20) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Vulnerability Management **Scanners.** Pair an unauthenticated scanner (Nessus / Qualys / Tenable.io) for external surface with an authenticated agent for OS/library CVEs on every host. **SLA.** Document remediation SLAs by CVSS / EPSS: critical 7 days, high 30 days, medium 90 days; report monthly trend to leadership. **Containers.** Scan images in CI (Trivy / Grype / Snyk Container) AND at runtime; block deploys on critical findings without exception. #### Cloud Posture **CSPM.** Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold. #### Incident Response **Runbook.** Maintain a runbook keyed by incident type with named roles (IC, comms, scribe), an out-of-band comms channel, and a 72-hour timeline for external notification. **Tabletop.** Run a quarterly tabletop exercise (ransomware, insider, supply-chain) and feed gaps back into the runbook. ### Operational checklist - **Risk.** 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. - **Scope:** cloud customer data, management. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Managing Vulnerabilities, Malfunctions and Errors - Measurements, Analyses and Assessments of Procedures. ## Common pitfalls - Scans that hit only the perimeter; missing authenticated scans of OS, runtime libs and base images so most CVEs are invisible. - Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why. - Runbooks that name a role but no person, or list a paging channel that no longer exists. ## 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.11.2** — Vulnerability Monitoring and Scanning](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-11-2-vulnerability-monitoring-and-scanning) - [**SOC 2 (2017 TSC) CC4.1** — Control Monitoring](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc4-1-control-monitoring) ## Related controls in BSI C5:2020 - [**Criterion OPS-19** — Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests](https://support.icompaas.com/compliance/bsi-c5-2020/ops-19-managing-vulnerabilities-malfunctions-and-errors-penetration-tests) - [**Criterion OPS-18** — Managing Vulnerabilities, Malfunctions and Errors - Concept](https://support.icompaas.com/compliance/bsi-c5-2020/ops-18-managing-vulnerabilities-malfunctions-and-errors-concept) - [**Criterion OPS-22** — Testing and Documentation of known Vulnerabilities](https://support.icompaas.com/compliance/bsi-c5-2020/ops-22-testing-and-documentation-of-known-vulnerabilities) - [**Criterion OPS-23** — Managing Vulnerabilities, Malfunctions and Errors - System Hardening](https://support.icompaas.com/compliance/bsi-c5-2020/ops-23-managing-vulnerabilities-malfunctions-and-errors-system-hardening) - [**Criterion OPS-10** — Logging and Monitoring - Concept](https://support.icompaas.com/compliance/bsi-c5-2020/ops-10-logging-and-monitoring-concept) - [**Criterion AM-04** — Decommissioning of Hardware](https://support.icompaas.com/compliance/bsi-c5-2020/am-04-decommissioning-of-hardware) ## 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-20` Topics: governance riskvulnerability managementcloud posturecontinuous monitoringincident response ## 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.