Cloud Security Frameworks

Cloud security frameworks such as BSI C5, ISO 27017, CSA STAR, and SOC

2 are structured catalogues of security controls designed specifically for cloud environments. They translate abstract security goals into concrete, auditable requirements covering areas like identity management, encryption, logging, supplier management, and incident handling. For your organization, a framework serves three purposes: it provides a systematic baseline so that cloud security does not depend on individual judgement, it creates independent evidence of your security posture for customers, auditors, and supervisory authorities, and it establishes a common language between security, procurement, and management. Especially in regulated industries, framework-based attestations are increasingly a precondition for winning contracts and for demonstrating sound third-party and ICT risk management.

The right framework depends on your market, your customers, and your regulatory environment — in practice, most organizations end up with a deliberate combination rather than a single standard.

🔍 Key decision criteria:

We recommend selecting one anchor framework and mapping the others onto it, so controls are implemented once and reported many times.

BSI C

5 (Cloud Computing Compliance Criteria Catalogue) is the German Federal Office for Information Security's criteria catalogue for cloud service security. It defines basic criteria that every cloud provider should meet and additional criteria for elevated protection needs, covering areas from organization and personnel to operations, encryption, and subcontractor management. Compliance is demonstrated through an attestation performed by an auditor based on recognised assurance standards — either as a point-in-time assessment of control design or as an assessment of operating effectiveness over a period. C

5 is not a general legal obligation, but it has become the de facto expectation for cloud services used by German public sector bodies and is increasingly referenced by supervisory authorities and regulated enterprises when assessing cloud providers.

The timeline depends primarily on your starting maturity and the scope of the cloud service to be attested. Organizations with an established ISO 27001 ISMS and disciplined operational processes typically need a focused preparation phase to close gaps, produce the system description, and build up evidence, followed by the audit itself. Organizations starting without a formal control environment should plan for a substantially longer implementation programme. A structural factor is the attestation type: a report on control design can be achieved faster, while a report on operating effectiveness requires controls to have operated reliably over a defined review period before the audit concludes. In our projects, we shorten the path with a precise gap analysis up front, so effort flows only into controls that are actually required.

Both standards extend ISO 27001/27002 for cloud scenarios, but with different focus. ISO

27017 is the general cloud security standard: it provides implementation guidance for existing ISO

27002 controls in cloud contexts and adds cloud-specific controls, addressing both cloud service providers and cloud customers — for example on shared responsibilities, segregation in virtual environments, and administrator operations. ISO 27018, by contrast, focuses specifically on the protection of personally identifiable information (PII) in public clouds, directed at providers acting as PII processors, and aligns cloud operations with data protection principles such as purpose limitation, transparency, and support for customer obligations. In practice: ISO

27017 strengthens your overall cloud security posture, while ISO

27018 provides targeted evidence for privacy-sensitive workloads and GDPR-driven customer requirements. Many providers implement both on top of ISO 27001.

Regulations like DORA and NIS2 define what outcomes you must achieve — resilient ICT operations, managed third-party risk, incident response capability — but they do not hand you an operating model. Cloud security frameworks close that gap.

🔍 How the frameworks support compliance:

We maintain mappings between the major frameworks and the relevant regulations, so you implement each control once and reuse the evidence across all obligations.