Digital Sovereignty
EUCS: The New Law of the Cloud Landscape
For the past decade, the European cloud compliance landscape has been a "Balkanized Mess."
EUCS: The New Law of the Cloud Landscape

For the past decade, the European cloud compliance landscape has been a "Balkanized Mess."

  • If you wanted to host health data in France, you needed SecNumCloud certification.

  • If you wanted to host government data in Germany, you needed C5 (Cloud Computing Compliance Criteria Catalogue).

  • If you wanted to do business in Spain, you needed ENS (Esquema Nacional de Seguridad).

This fragmentation was a nightmare for SaaS vendors. You had to pay for 27 different audits to sell to 27 different countries. It was also a barrier to a "Digital Single Market."

Enter ENISA (The European Union Agency for Cybersecurity). Their mission: To create one ring to rule them all. The European Union Cybersecurity Certification Scheme (EUCS).

Why You Must Care: EUCS is not just another badge. It will likely become mandatory for public procurement across the EU. If your SaaS platform runs on a cloud that isn't EUCS certified, you will be disqualified from billions of euros in government contracts.

Part 1: The Three Assurance Levels

EUCS is not binary (Pass/Fail). It is tiered. Understanding which tier your application falls into is the most critical strategic decision you will make this year.

Level 1: Basic (CS Basic)

Target: Non-critical data. Public websites, marketing brochures, open data portals. Requirements:

  • Standard encryption (TLS 1.2+).

  • Basic Incident Response plan.

  • Comparable to ISO 27001 but lighter. Impact: Almost any competent cloud provider (including cheap VPS hosts) can pass this.

Level 2: Substantial (CS Substantial)

Target: Standard enterprise workloads. ERP systems, CRM, Payroll, Email. Requirements:

  • Strong MFA.

  • Disaster Recovery (DR) testing.

  • Data Residency (Data must be stored in the EU), but Data Sovereignty (Immunity from US law) is not strictly required. Impact: AWS, Azure, and Google Cloud (standard regions like eu-west-1) fit here easily.

Level 3: High (CS High)

Target: "Essential" services. Health data, National Security, Energy Grids, Law Enforcement. Requirements (The Controversy):

  • Immunity from Extra-territorial Law: The provider must demonstrate that no non-EU government (e.g., USA, China) can compel data access.

  • Headquarters Location: Effectively requires the cloud provider to be headquartered in the EU (or use a strict legal Trustee structure).

  • Staff Nationality: Administrators with root access may need to be EU citizens. Impact: This effectively bans standard US Hyperscalers. Only OVHcloud, T-Systems, Orange, or "Trusted Cloud" setups (like Google Distributed Cloud hosted by a partner) can qualify.

Part 2: The Political Battle (The "Sovereignty Criteria")

The definition of "CS High" has sparked a massive lobbying war in Brussels.

The US Position (AWS/Google/Microsoft/AmCham): They argue that "Security is technical, not political." A US cloud with good encryption is just as secure as a French cloud. They claim the "Sovereignty Requirement" (immunity from non-EU law) is Protectionism designed to prop up inferior European competitors.

The EU Position (France/Internal Market Commissioner): They argue that "Legal Security is part of Security." If a US judge can order the data to be exfiltrated (CLOUD Act), the data is not secure, regardless of the encryption strength. They point to the risk of "Geopolitical Sanctions" (e.g., what if a future US president sanctions a European company?).

The Compromise (Current Status): As of late 2024, the draft has softened slightly. "CS High" might be split into "High" (Technical excellence) and "High+" (Sovereignty). However, individual nations (like France) say they will require the "Sovereignty" criteria for their public sector regardless of what the final EUCS text says.

Part 3: Technical Implementation for SaaS Vendors

If you are a SaaS CTO, you cannot afford to wait for the politicians to finish arguing. You need an architecture that supports Portability.

Terraform

# The "EUCS Ready" Terraform Strategy

# You create an abstraction layer (module) for "Storage"
# Depending on the "compliance_level" variable, it provisions
# different backends.

variable "compliance_level" {
    description = "EUCS Level: Basic, Substantial, High"
    default = "Substantial"
}

module "object_storage" {
    source = "./modules/storage"

    # If Basic/Substantial -> Use AWS S3 (Standard)
    # If High -> Use MinIO on OVH Dedicated Servers

    provider = var.compliance_level == "High" ? "ovh" : "aws"
    bucket_name = "patient-records-v1"
}

The days of hardcoding import boto3 are over. You must use storage abstractions (like the S3 API standard, which MinIO and Ceph support) so you can swap the backend without rewriting code.

Part 4: The Audit Nightmare

Getting EUCS certified is not self-assessment. You must be audited by a CAB (Conformity Assessment Body).

  • Documentation: You need to map every control (Encryption key rotation, Background checks, Physical access logs) to the EUCS control matrix.

  • Continuous Monitoring: It's not a one-time stamp. You need "Continuous Auditing" tools that pipe your CloudTrail/Audit logs to a compliance dashboard.

  • Supply Chain: You are responsible for your vendors. If you rely on SendGrid (US company) for email, you might fail CS High. You might need to switch to a European SMTP provider like Mailjet.

Deep Dive: The French Inspiration (SecNumCloud) EUCS didn't appear out of thin air. It is heavily modeled on France's SecNumCloud (SNC). SNC is notoriously difficult. It requires the cloud operator to be immune to non-EU laws (read: No US ownership). The "Sovereign Shield": Microsoft and Google are currently building "SNC-Compliant" regions in France by licensing their IP to local French companies (ex. S3NS by Google/Thales and Bleu by Microsoft/Orange). These local companies operate the hardware, creating a legal air-gap.

Strategy: The "Hybrid Assurance" Architecture Problem: "CS High" clouds are expensive and feature-poor. Solution: Don't put everything in "High".

  1. Frontend (CS Basic): Run your React app on Vercel/Netlify. No sensitive data.

  2. Business Logic (CS Substantial): Run your Java API on AWS eu-central-1 (Germany). Encryption at rest/transit is sufficient.

  3. Deep Storage (CS High): Store the actual patient PDFs in a "CS High" Object Store (e.g., Scaleway Object Storage or OVH Cloud). Result: You get the speed of AWS for compute, but the compliance of a Sovereign Cloud for data storage.

Checklist: The "EUCS Ready" Audit [ ] Identity: Are all admins approaching root logging in via FIDO2 keys? [ ] Encryption: Are you using Customer Managed Keys (CMK) held in an external HSM? [ ] Support: Do you have a contract ensuring support tickets are handled only by EU nationals? [ ] Dependency: Have you audited your package.json for libraries that phone home to US servers?

Part 5: Future Outlook

EUCS will cascade down the supply chain.

  1. Government requires EUCS High for a Hospital SaaS.

  2. The Hospital SaaS requires EUCS High from its hosting provider.

  3. It also requires EUCS High from its analytics tool, its log aggregator, and its CI/CD pipeline.

This will create a bifurcated market: The "Commodity Market" (US Cloud, standard compliance) and the "Sovereign Market" (EU Cloud, high compliance, higher price). Smart vendors will offer two SKUs: "Enterprise" and "Sovereign Edition."

The Rise of "Sovereign-Native" Startups

We are seeing a new wave of startups (like Scaleway, Hetzner, UpCloud) that use their "EU-Native" status as a competitive weapon against AWS. They market "No CLOUD Act Risk" as a primary feature, not just a compliance checkbox.

Part 6: Glossary

  • ENISA: European Union Agency for Cybersecurity. The authors of EUCS.

  • CAB: Conformity Assessment Body. The private auditors licensed to issue the certificate.

  • SecNumCloud: The rigorous French standard that inspired CS High.

  • Data Residency: Geographic location of data.

  • Data Sovereignty: Legal jurisdiction of data.

Conclusion

EUCS is the biggest shift in European cloud procurement in history. It turns "Sovereignty" from a vague marketing term into a hard procurement requirement. If you want to sell to the EU Public Sector in 2026, start preparing your "CS High" strategy today.

See, Understand, Optimize -
All in One Place

Atler Pilot decodes your cloud spend story by bringing monitoring, automation, and intelligent insights together for faster and better cloud operations.