BSI C5:2020 SIM-02 — Processing of security incidents

What this control requires

Engages experts to classify, prioritize, and analyze potential security incidents, performing root-cause analysis. Ensures swift and accurate handling to mitigate impacts on cloud customer data and maintain service security and integrity.

In plain English

Engages experts to classify, prioritize, and analyze potential security incidents, performing root-cause analysis. 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-02) and look for objective evidence on the latest two assessment cycles.

How to implement

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.
• Access. Document the trigger, the owner and the cadence.
• Scope: cloud customer data, security incident management, security incidents.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Processing of security incidents.

Common pitfalls

• 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.26 — Response to information security incidents
• HIPAA (45 CFR Part 164) 164.308(a)(6)(i) — Security Incident Procedures
• NIST SP 800-171 Rev. 3 3.12.3 — Continuous Monitoring
• NIST SP 800-53 Rev. 5 PS-1 — Policy And Procedures

Related controls in BSI C5:2020

• Criterion SIM-05 — Evaluation and learning process
• Criterion SIM-01 — Policy for security incident management
• Criterion SP-03 — Exceptions from Existing Policies and Instructions
• Criterion HR-02 — Employment terms and conditions
• Criterion PI-01 — Documentation and safety of input and output interfaces
• Criterion COM-01 — Identification of applicable legal, regulatory, self-imposed or contractual requirements

References

• Bundesamt für Sicherheit in der Informationstechnik (BSI) — BSI C5:2020
• Catalogue identifier: Criterion SIM-02

Topics: governance riskcloud posturepolicy managementprivileged access