Strategic sovereignty (SOV-1)
The provider's strategy, governance and decision-making must support sovereign cloud use and be transparent to customers.
C3A is the BSI's non-binding criteria catalogue for digital sovereignty in cloud services. It is structured around six sovereignty categories: strategic, legal and jurisdictional, data, operational, supply chain and technology.
C3A was published by the BSI on 27 April 2026. It provides transparency criteria for digitally sovereign cloud use, is based on the EU Cloud Sovereignty Framework (EU CSF), and presupposes compliance with C5. The dashboard currently maps WAF-SOV-010 (Data Residency & Geolocation) and WAF-SOV-020 (Encryption Key Management) to the C3A data and jurisdictional dimensions; use that as a starting point and verify the exact criteria in the official catalogue.
A practical reading of the obligations that usually end up in architecture, operations and evidence reviews.
The provider's strategy, governance and decision-making must support sovereign cloud use and be transparent to customers.
Jurisdiction, ownership, legal exposure and the provider's ability to resist extraterritorial access requests must be assessable.
Data classification, residency, processing locations, encryption and key management determine who can access the data and under which law.
Operational independence, supplier dependencies, SBOM/hardware transparency, source-code escrow and exit capability are part of the sovereignty picture.
Each obligation maps to one or more pillars. The pillar pages show the controls, principles and evidence expectations behind the score.
The primary mapping: WAF-SOV-010 and WAF-SOV-020 are relevant to the data, jurisdictional and technology sovereignty categories.
Read the Sovereign pillar →Encryption, key custody and access boundaries are the technical core of the data and technology categories.
Read the Security pillar →Evidence, supplier oversight and change control make the sovereignty claims auditable.
Read the Operational Excellence pillar →A jurisdiction change or provider exit is only credible if the workload can be recovered and moved.
Read the Reliability pillar →These are the control themes teams usually need to evidence. The controls catalogue is the authoritative source for the exact control-level mapping.
Confirm the C3A scope and the six sovereignty categories in the official BSI publication.
Review the dashboard's current WAF-SOV-010/020 mapping as a starting point, then verify the exact C3A criteria.
Score the Sovereign pillar and collect residency, jurisdiction and key-management evidence.
Export the evidence for provider, procurement or audit conversations.
Wombat controls carry tags for the frameworks below. Use them to connect the technical baseline to the evidence your auditor or procurement team already expects.
Score the sovereign baseline, then connect the official C3A categories to the controls and evidence you can actually produce.
Wombat is a technical framework, not a law firm. These pages map relevant Wombat pillars and control themes to regulatory obligations; they do not provide legal advice. Validate the mapping against the official text and your auditor.
The same control baseline usually has to satisfy more than one obligation. Jump to the adjacent hub and reuse the evidence.
NIS2 raises the baseline for cybersecurity risk management, incident reporting and supply-chain accountability across essential and important entities in the EU.
Open the NIS2 hub →DORA brings ICT risk management, incident reporting, resilience testing and third-party oversight into one operational-resilience regime for financial entities and their critical providers.
Open the DORA hub →The BSI Cloud Computing Compliance Criteria Catalogue (C5) is the German benchmark for cloud security, transparency and auditability — and a common procurement requirement for cloud providers and their customers.
Open the BSI C5 hub →Residency, jurisdiction, key ownership, supplier concentration and exit paths — turned into controls a team can assess.
Open the sovereignty hub →