# BSI C5:2020 SIM-01 — Policy for security incident management - Source: https://support.icompaas.com/compliance/bsi-c5-2020/sim-01-policy-for-security-incident-management - Section: [Compliance](https://support.icompaas.com/compliance) › [BSI C5:2020 (Cloud Computing Compliance Criteria)](https://support.icompaas.com/compliance/bsi-c5-2020) › Security Incident Management (SIM) - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **BSI C5:2020**·Criterion `SIM-01`·high·Component: **Security Incident Management** ## What this control requires > Documents incident management policies per SP-01, defining classification, escalation, and CERT coordination. Ensures timely customer notification and effective response to incidents, protecting cloud customer data from security breaches. > > — BSI C5:2020, Criterion SIM-01 ### In plain English Documents incident management policies per SP-01, defining classification, escalation, and CERT coordination. 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 **Security Incident Management**, the assessor will trace your implementation back to the catalogue reference (Criterion SIM-01) and look for objective evidence on the latest two assessment cycles. ## How to implement #### 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. #### Cloud Posture **CSPM.** Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold. #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### 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. - **Policy.** Document the trigger, the owner and the cadence. - **Scope:** cloud customer data, security incident management. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Policy for security incident management. ## Common pitfalls - Runbooks that name a role but no person, or list a paging channel that no longer exists. - Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why. - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## 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. - [**ISO/IEC 27001:2022 A.5.24** — Information security incident management planning and preparation](https://support.icompaas.com/compliance/iso-27001-2022/a-5-24-information-security-incident-management-planning-and-preparation) - [**HIPAA (45 CFR Part 164) 164.308(a)(6)(i)** — Security Incident Procedures](https://support.icompaas.com/compliance/hipaa/164-308-a-6-i-security-incident-procedures) - [**NIST SP 800-171 Rev. 3 3.12.3** — Continuous Monitoring](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-12-3-continuous-monitoring) - [**CIS Controls v8 17.4** — Establish and Maintain an Incident Response Process](https://support.icompaas.com/compliance/cis-controls-v8/17-4-establish-and-maintain-an-incident-response-process) - [**ISO/IEC 42001:2023 A.3.3** — Reporting of concerns](https://support.icompaas.com/compliance/iso-42001-2023/a-3-3-reporting-of-concerns) ## Related controls in BSI C5:2020 - [**Criterion SIM-05** — Evaluation and learning process](https://support.icompaas.com/compliance/bsi-c5-2020/sim-05-evaluation-and-learning-process) - [**Criterion SIM-02** — Processing of security incidents](https://support.icompaas.com/compliance/bsi-c5-2020/sim-02-processing-of-security-incidents) - [**Criterion SIM-04** — Duty of the users to report security incidents to a central body](https://support.icompaas.com/compliance/bsi-c5-2020/sim-04-duty-of-the-users-to-report-security-incidents-to-a-central-body) - [**Criterion SP-03** — Exceptions from Existing Policies and Instructions](https://support.icompaas.com/compliance/bsi-c5-2020/sp-03-exceptions-from-existing-policies-and-instructions) - [**Criterion HR-02** — Employment terms and conditions](https://support.icompaas.com/compliance/bsi-c5-2020/hr-02-employment-terms-and-conditions) - [**Criterion PI-01** — Documentation and safety of input and output interfaces](https://support.icompaas.com/compliance/bsi-c5-2020/pi-01-documentation-and-safety-of-input-and-output-interfaces) ## 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 SIM-01` Topics: governance riskincident responsecloud posturepolicy management ## 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.