Latest feature: Compare your cloud architecture against known frameworks such as NIS and SOC2.Compare your cloud against NIS and SOC2.

Book a demo
AKRIBOS AI
ProductComplianceEngineersSecurityFAQ
Sign InTry AKRIBOSTry AKRIBOS
Home/Compliance/BSI C5

BSI C5

Germany's cloud computing compliance criteria catalogue.

Updated 13 October 2026

Published by the Federal Office for Information Security, C5 defines the minimum requirements for cloud providers and is widely used by German public-sector and regulated customers as the basis for attestation.

C5:2020 defines 121 criteria across 17 areas, split into basic criteria and additional ones for higher protection needs. Compliance is demonstrated through an attestation by an auditor under ISAE 3000, Type 1 for design or Type 2 for operation over a period, much like SOC 2. German federal agencies must consider C5 when procuring cloud services, and many regulated customers follow suit.

Who needs it

Cloud and SaaS providers selling to German public-sector bodies, banks, insurers and healthcare, and the companies that run their own workloads for those customers. BaFin's guidance on outsourcing to cloud providers references it, and it is often requested alongside ISO 27001.

Where C5 meets your cloud configuration

Several C5 areas are about configuration: identity and access management, cryptography and key management, communication security including network segmentation, and operations including logging, monitoring, vulnerability and patch management. The criteria expect documented controls and evidence that they operate, which is what a continuous review provides.

C5 and the frameworks you already have

C5 maps closely to ISO 27001 Annex A and to SOC 2, and the BSI publishes the correspondence. If you already evidence those, C5 mostly adds German-specific transparency criteria about jurisdiction, data location and subcontractors.

What C5 asks of your cloud

The control areas that map onto infrastructure configuration in AWS, Google Cloud and Azure.

IDM · Identity and access management

Provisioning and deprovisioning, least privilege, privileged access, strong authentication and regular access reviews.

CRY · Cryptography and key management

Encryption of data in transit and at rest, and the management of cryptographic keys.

COS · Communication security

Network segmentation, controlled cross-network traffic, and monitoring of connections.

OPS · Operations

Logging and monitoring of security events, protection of logs, vulnerability and patch management, and backup.

AM · Asset management

An inventory of assets and their classification, including cloud resources and accounts.

SSO · Subcontractors and suppliers

Control over service providers and the access they hold.

How AKRIBOS checks C5

Mapped to your resources

Every C5 control is evaluated against the actual accounts, roles, networks and storage in your estate, with the setting behind each result.

Findings come with the fix

A failing control is shown with the exact change as CLI commands or Terraform. You review and approve; nothing is applied on its own.

Evidence over time

Scheduled reviews and a full audit trail give you a dated record of each control for the whole audit period, not just the day of the audit.

Common issues under C5

Misconfigurations that fail C5 controls, with the control reference for each.

Storage bucket open to the internet

Critical

Object storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.IDM (access to data restricted), AM (asset classification).

Read more

Root or owner account without MFA

Critical

The most privileged identity in the account protected by a password alone.IDM (strong authentication for privileged users).

Read more

Database reachable from the internet

Critical

A managed database with a public address and a firewall that lets the world in.COS (segmentation), IDM (access to data).

Read more

Snapshots or machine images shared publicly

Critical

Disk snapshots, database snapshots or machine images that anyone with a cloud account can copy.AM (asset handling), IDM (access).

Read more

Over-permissive IAM policies

High

Identities, often service accounts, that can do anything in the account because a wildcard or a basic role was easier than a scoped policy.IDM (least privilege, privileged access management).

Read more

SSH or RDP open to 0.0.0.0/0

High

Management ports reachable from any address on the internet.COS (network segmentation and controlled traffic).

Read more

Audit logging incomplete

High

Gaps in the record of who did what: missing regions, missing data-access events, or logs that can be altered.OPS (logging and monitoring of security events).

Read more

Long-lived or unused credentials

High

Access keys, service account keys and client secrets that never rotate and are no longer needed.IDM (credential lifecycle, deprovisioning).

Read more

Instance metadata without session tokens

High

Compute instances that answer metadata requests, including their temporary credentials, to any process that can reach the local metadata address.OPS (vulnerability and patch management).

Read more

Trust policies open to any account

High

Roles or bindings that let identities outside your organisation assume access, often for a vendor integration that was set up too generously.SSO (subcontractors and suppliers), IDM (access).

Read more

Data at rest without the encryption you intended

Medium

Volumes, snapshots or databases created without encryption, or without the customer-managed keys your policy requires.CRY (encryption of data at rest, key management).

Read more

Transport encryption not enforced

Medium

Endpoints that still accept plaintext or outdated TLS, even though an encrypted path exists.CRY (encryption in transit), COS (communication security).

Read more

Network flow logs off

Medium

No record of which addresses talked to which, so traffic to and from a compromised host cannot be reconstructed.COS (monitoring of connections), OPS (logging).

Read more

Default network with permissive rules

Medium

Workloads running in the cloud-created default network, which ships with rules nobody would write deliberately.COS (segmentation).

Read more

C5 questions

Is C5 only for cloud providers?

C5 was written for providers, but the criteria apply equally to any organisation running workloads in the cloud for regulated customers, and customers increasingly ask their suppliers for the same evidence.

Type 1 or Type 2?

Type 1 attests the design of controls at a point in time; Type 2 attests their operation over a period, typically six to twelve months. Public-sector and financial customers usually want Type 2.

How does C5 relate to ISO 27001 and SOC 2?

Heavily overlapping. The BSI publishes mappings, and the same cloud evidence for access, encryption, networks and logging supports all three; C5 adds criteria on transparency about jurisdiction and subcontractors.

Other frameworks

CIS Benchmarks

The baseline configuration standard for AWS, Google Cloud and Azure.

Read more

SOC 2

Evidence that your cloud controls work, not just that they exist.

Read more

ISO/IEC 27001

The international standard for an information security management system, applied to your cloud.

Read more

DORA

The EU Digital Operational Resilience Act, applied to the cloud behind your financial services.

Read more

NIS2

EU-wide cyber risk-management obligations for essential and important entities.

Read more

PCI DSS v4

Requirements for every environment that stores, processes or transmits cardholder data.

Read more

NIST CSF 2.0

The US framework of outcomes: Govern, Identify, Protect, Detect, Respond, Recover.

Read more

DNB Good Practice Information Security

What De Nederlandsche Bank expects of the financial institutions it supervises.

Read more
All frameworks

Attackers don't wait for your next audit. Neither does AKRIBOS.

Connect AWS, Google Cloud or Azure and get your first review today.

Run your first reviewRun your first review
Cinematic desert landscape at dusk with a lone silhouette standing before a warm amber glow, surrounded by dark rolling hills and a deep blue sky.
AKRIBOS

The AI agent that reviews and hardens your cloud, right from your terminal or our dashboard.

Navigation

How It WorksAttack PathsContinuous ReviewsComplianceCommon Cloud IssuesFor EngineersSecurityFAQ

Information

ContactPrivacy PolicyTerms of ServiceData Processing AgreementResponsible Disclosure

Socials

LinkedIn

© 2026 AKRIBOS AI B.V. All rights reserved.

AKRIBOS is a trade name of AKRIBOS AI B.V., registered with the Netherlands Chamber of Commerce (KvK) under number 83548335, Amsterdam, The Netherlands.