BSI C5:2020 OIS-01 — Information Security Management System (ISMS)

What this control requires

Operates an ISO/IEC 27001-compliant ISMS covering CSP organizational units, locations, and cloud service procedures. Documents setup, implementation, and continuous improvement, including ISMS scope, declaration of applicability, and recent management review results to ensure robust security governance for cloud customer data protection.

In plain English

Operates an ISO/IEC 27001-compliant ISMS covering CSP organizational units, locations, and cloud service procedures. In practice, this means you can prove you information security management system (isms)-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 Information Security Governance, the assessor will trace your implementation back to the catalogue reference (Criterion OIS-01) 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

• Information. Document the trigger, the owner and the cadence.
• Risk. 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.
• Protection. Document the trigger, the owner and the cadence.
• Scope: security management system (isms), isms scope, protection, cloud customer data.

Evidence to collect

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

Signed policy or standard documents the safeguard. Focus: Information Security Management System (ISMS).

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.

• NIST SP 800-171 Rev. 3 3.12.3 — Continuous Monitoring
• NIST SP 800-53 Rev. 5 PL-6 — Security-Related Activity Planning
• ISO/IEC 27001:2022 A.5.23 — Information security for use of cloud services
• GDPR Article 3 — Territorial Scope
• SOC 2 (2017 TSC) CC4.1 — Control Monitoring

Related controls in BSI C5:2020

• Criterion AM-06 — Asset Classification and Labelling
• Criterion SP-03 — Exceptions from Existing Policies and Instructions
• Criterion OIS-05 — Contact with Relevant Government Agencies and Interest Groups
• Criterion OIS-06 — Risk Management Policy
• Criterion COS-08 — Policies for data transmission
• Criterion SP-02 — Review and Approval of Policies and Instructions

References

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

Topics: governance riskcloud posturecontinuous monitoringpolicy management