← Frameworks / Cloud Controls

BSI Cloud Computing Compliance Criteria Catalogue (C5:2026)

C5, the Cloud Computing Compliance Criteria Catalogue, is the cloud security standard of Germany's Federal Office for Information Security (BSI). A cloud provider has an auditor attest how it meets C5, and its customers read the report. C5:2026 has 168 criteria in 17 domains. Each criterion has basic criteria and may have optional additional ones. BSI built C5:2026 to be compatible with the security requirements of EUCS, the planned EU cloud certification scheme, at level Substantial. BSI recommends C5:2026 for audit periods ending on or after 1 June 2027, and C5:2020 until then. Federal bodies set C5's basic criteria for the cloud services they use, and German law asks healthcare providers and health insurers for a C5 attestation before they put health and social data in a cloud service. OSA keeps BSI's criterion ids and maps each criterion, with its additional criteria, to SP 800-53 from three independent ratings, with titles in its own words.

How this mapping was made

OSA's own analysis, from BSI's text by three independent ratings. NIST's catalogue of registered crosswalks has none for C5 (checked 12 November 2026), and BSI publishes no mapping to SP 800-53. BSI licenses C5:2026 under CC BY-ND 4.0, which allows it to be shared only unchanged, and OSA's data is CC BY-SA 4.0, so OSA rated the criteria itself and wrote the titles, rationale and gaps in its own words. Six AI raters worked in two groups of three. One group rated the 76 criteria of the domains OIS to OPS, and the other the 92 of IAM to PSS. Each rater worked on its own, from BSI's English text of each criterion and BSI's supplementary information, and from the control statements. None saw another's rating. Each rater read a criterion together with its additional criteria and rated them as one. OSA lists a control for a criterion where at least two of the three raters in its group named it, or where OSA's house rule for policy clauses adds it. The coverage figure is the median of the three estimates of how much of the criterion and its additional criteria an organisation would meet by putting the listed controls in place. OSA wrote the titles, rationale and gaps after the controls were settled, from the raters' reasons and the gaps at least two of them named, and a reviewer checked each one against the control statements.

Texts

  • Cloud Computing Compliance Criteria Catalogue C5:2026, machine-readable, English, version 1.0.2 (Federal Office for Information Security (BSI), first published 7 April 2026, files dated 4 November 2026, licensed CC BY-ND 4.0)
  • Cloud Computing Compliance Criteria Catalogue C5:2026, English, version 1.0.2 (PDF) (Federal Office for Information Security (BSI), 2026, licensed CC BY-ND 4.0)
  • Kriterienkatalog Cloud Computing C5:2026, maschinenlesbare Version, Deutsch, Version 1.1.1 (Bundesamt für Sicherheit in der Informationstechnik (BSI), with the corrections of 11 August 2026, files dated 4 November 2026, licensed CC BY-ND 4.0)
Clause Title SP 800-53 Controls
OIS-01 An ISO 27001 management system that covers the cloud service
OIS-02 A top-level security policy set by senior management
OIS-03 Shared responsibility model with customers
OIS-04 Separating conflicting duties on the basis of risk
OIS-05 Gathering threat intelligence and feeding it into risk management
OIS-06 Keeping in touch with Germany's national cyber bodies
OIS-07 A documented, repeatable method for managing risk
OIS-08 Yearly and event-driven risk assessment of the service
OIS-09 Planning and tracking the treatment of risks
OIS-10 Assessing security risk in projects that affect the service
SP-01 One consistent, approved set of security policies
SP-02 Yearly expert review of security policies, approved before use
SP-03 A risk-approved register of policy exceptions
HR-01 Screening staff who can reach production systems and data
HR-02 Security duties written into staff contracts
HR-03 Role-based security awareness and training for all staff
HR-04 A documented disciplinary process for policy breaches
HR-05 Security duties that continue after leaving or changing jobs
HR-06 Confidentiality agreements for staff and service organisations
HR-07 Rules for protecting information when staff work remotely
HR-08 Putting the remote working rules into practice
AM-01 Documented rules for identifying and tracking service assets
AM-02 Keeping a complete, current inventory of assets
AM-03 Details recorded for each hardware item
AM-04 A full record of the software the service uses
AM-05 Rules for using assets securely through their life cycle
AM-06 Approving new hardware before it enters production
AM-07 Retiring hardware with secure deletion or destruction
AM-08 Staff commitments on handling and returning assets
AM-09 Classifying assets by the protection needs of their data
AM-10 Storing idle hardware safely until it is needed
AM-11 Moving production hardware off site under control
AM-12 Securing portable storage and the devices staff use
PS-01 Site security requirements for data centres and premises
PS-02 Running the service from at least two separate sites
PS-03 A solid building shell that resists and detects intrusion
PS-04 Controlling and logging entry to sites and secure areas
PS-05 Protecting the sites from environmental hazards
PS-06 Keeping power and other supply facilities running
PS-07 Monitoring utilities and room conditions with alarms
PS-08 Security rules for office workplaces
OPS-01 Planning staff and system capacity ahead of demand
OPS-02 Watching capacity so customers get what was agreed
OPS-03 Customer control over allocated resources
OPS-04 Rules for protecting systems and devices from malware
OPS-05 Running and updating malware protection in production
OPS-06 Backup and restore rules matched to recovery objectives
OPS-07 Watching backup runs and fixing failures
OPS-08 Testing restores against recovery objectives each year
OPS-09 Keeping protected backups at a distant second site
OPS-10 A policy for event logging and system monitoring
OPS-11 Using derived and account data only to run the service
OPS-12 Technical limits on who sees logs and how long they stay
OPS-13 Central security event analysis linked to incident response
OPS-14 Storing logs centrally in tamper-proof form
OPS-15 Logs that trace each access and support forensic work
OPS-16 Multi-factor access to logging systems and controlled changes
OPS-17 Alerts when logging or monitoring tools fail
OPS-18 Rules for finding and fixing vulnerabilities on time
OPS-19 How incidents and crashes are handled and recorded
OPS-20 Recording and resolving incidents as the procedures set out
OPS-21 Spotting and fixing crashes of components or the service
OPS-22 Regular, risk-based penetration testing of the service
OPS-23 Measuring how well vulnerability and incident handling works
OPS-24 Keeping affected customers informed during incidents
OPS-25 Scanning for known vulnerabilities at least monthly
OPS-26 Hardening production components to industry benchmarks
OPS-27 Rules for timely, tested patching
OPS-28 Deploying patches through change control
OPS-29 Keeping third-party and open-source libraries up to date
OPS-30 Rules for keeping each customer's data apart
OPS-31 Strict separation of customer data on shared resources
OPS-32 Policy for protecting data in use with trusted hardware
OPS-33 Letting customers verify trusted execution remotely
OPS-34 Securing containers and images across their life cycle
OPS-35 Putting the container rules into practice
IAM-01 Identity and access policy with a role-based framework
IAM-02 Granting and changing identities, with break-glass rules
IAM-03 Risk-based locking of identities and watch for stolen credentials
IAM-04 Adjusting or removing access when duties or tasks change
IAM-05 Yearly access review and clean-up of orphaned resources
IAM-06 Managing and monitoring privileged access
IAM-07 Tenant separation and notice of provider access to customer data
IAM-08 Authentication of staff and components, with MFA and lockout
IAM-09 Safe handling of passwords and other credentials
CRY-01 Cryptography policy and post-quantum strategy
CRY-02 Assessing and recording changes to cryptographic systems
CRY-03 Yearly and incident-driven audits of cryptographic practice
CRY-04 Encrypting and authenticating data in transit
CRY-05 Encrypting stored customer data and keeping keys with the customer
CRY-06 Creating keys from secure random bit generators
CRY-07 Scheduled key rotation and notice when the provider skips it
CRY-08 Issuing and obtaining certificates securely
CRY-09 Issuing keys to verified holders with set validity dates
CRY-10 Protected key stores separate from the application layer
CRY-11 Archiving keys safely for later recovery
CRY-12 Overseeing changes in key state, such as suspension
CRY-13 Limiting compromised keys and telling affected customers
CRY-14 Retiring keys and logging their destruction
CRY-15 Safe use of pre-shared keys and wildcard certificates
CRY-16 Key backup or redundancy to keep key services running
CRY-17 Tracking keys through their lives, with full records
CRY-18 Using an outside key management service securely
CRY-19 Protecting keys that customers bring and manage
COS-01 Layered defences that detect and stop network attacks
COS-02 Network zoning and permitted connections inside the provider
COS-03 Trusted and untrusted zones, with yearly network reviews
COS-04 Security gateways at each network boundary
COS-05 Separate administration networks protected by MFA
COS-06 Keeping each customer's traffic apart on shared networks
COS-07 Current network maps and where customer data is kept
COS-08 Policy and safeguards for moving data securely
PI-01 Secure, documented interfaces for customer systems and data export
PI-02 Contract terms for returning customer data at exit
PI-03 Deleting customer data at contract end, with proof
DEV-01 Secure development rules across the whole service life cycle
DEV-02 Contract terms and risk checks for outsourced development
DEV-03 Change management policy for the service's components
DEV-04 Role-based training on secure delivery and malicious code
DEV-05 Documented design of security functions, based on analysis
DEV-06 Assessing the risk of each change before release
DEV-07 Risk-based, documented tests before changes go live
DEV-08 Tracing every production change to who made it
DEV-09 Tracking every software and configuration change, with rollback
DEV-10 Approving changes before they reach production
DEV-11 Risk-based protection of non-production environments
DEV-12 Keeping production apart from test and development
DEV-13 Keeping a software bill of materials up to date
DEV-14 Rules for outside and open-source software and hardware
DEV-15 Handling emergency changes and other exceptions safely
SSO-01 Rules for overseeing suppliers that help run the service
SSO-02 Assessing supplier risk before and during use
SSO-03 Limiting supplier access to customer data
SSO-04 A reviewed register of suppliers and their details
SSO-05 Ongoing checks that suppliers meet their security duties
SSO-06 Exit plans for suppliers the provider depends on heavily
SSO-07 Telling customers which suppliers handle their data
SSO-08 Approving each transfer between components and their vendors
SIM-01 How the provider prepares for and handles security incidents
SIM-02 Approved plans for each stage of incident response
SIM-03 Analysing incidents to their root cause and keeping evidence
SIM-04 Sharing incident outcomes with affected customers
SIM-05 Making staff and partners report events to one central point
SIM-06 Learning from incidents through a knowledge base
BCM-01 Running continuity management under a senior owner
BCM-02 Assessing the impact of disruption on critical services
BCM-03 Documented plans to keep the service running
BCM-04 Yearly continuity tests that include customers
COM-01 Listing the requirements that apply and how they are met
COM-02 A multi-year audit programme that protects the live service
COM-03 Yearly impartial internal audits with risk-based follow-up
COM-04 Reporting security performance to top management
INQ-01 Legal review of government requests for data
INQ-02 Telling customers about government requests for their data
INQ-03 Giving agencies only the data a request covers
INQ-04 Documenting for customers how data is disclosed to authorities
PSS-01 Guidance that helps customers configure and use the service securely
PSS-02 Finding vulnerabilities during development by testing and review
PSS-03 Publishing known vulnerabilities and fixes to customers
PSS-04 Logs and error reports that customers can use and control
PSS-05 Multi-factor sign-in that customers can enforce
PSS-06 Secure sessions that end after inactivity
PSS-07 Password rules and tools the provider offers customers
PSS-08 Self-service roles and access rights for customer users
PSS-09 Checking every action against the user's permissions
PSS-10 Keeping customer data confidential in virtual networks
PSS-11 Hardened, traceable machine and container images
PSS-12 Keeping customer data in the regions the contract names