BSI C5:2020 SP-01 — Documentation, communication and provision of policies and instructions

What this control requires

Derives policies from the information security policy, documenting them with uniform structure, version control, and top management approval. Communicates objectives, scope, roles, dependencies, security strategy, and legal requirements to employees and third parties to ensure compliance and protect cloud data.

In plain English

Derives policies from the information security policy, documenting them with uniform structure, version control, and top management approval. In practice, this means you can prove you information security policy-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 Policy Management, the assessor will trace your implementation back to the catalogue reference (Criterion SP-01) and look for objective evidence on the latest two assessment cycles.

How to implement

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.

Cloud Posture

CSPM. Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold.

Operational checklist

• Information. Document the trigger, the owner and the cadence.
• Risk. Document the trigger, the owner and the cadence.
• Documentation,. 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: security policy, management.

Evidence to collect

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

Signed policy or standard documents the safeguard. Focus: Documentation, communication and provision of policies and instructions.

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.
• Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why.

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.

• HIPAA (45 CFR Part 164) 164.308(a)(5)(i) — Security Awareness and Training
• ISO/IEC 27001:2022 A.5.23 — Information security for use of cloud services
• NIST SP 800-53 Rev. 5 PL-2(3) — Plan And Coordinate With Other Organizational Entities
• NIST SP 800-171 Rev. 3 3.12.3 — Continuous Monitoring
• SOC 2 (2017 TSC) CC2.3 — External Communication on Internal Control Matters

Related controls in BSI C5:2020

• Criterion SP-03 — Exceptions from Existing Policies and Instructions
• Criterion SP-02 — Review and Approval of 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 SIM-05 — Evaluation and learning process

References

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

Topics: governance riskpolicy managementcloud posture