Skip to content

Sovereign cloud and SecNumCloud: the qualified offers and how to choose

Being hosted in Europe is not enough to protect your data from foreign laws. What SecNumCloud requires, how versions 3.1 and 3.2 differ, the qualified offers in the ANSSI catalogue of 16 October 2026, who has to use one, and what we check before choosing.

By Published on 29 September 2026Updated on 26 October 2026

Do you need a SecNumCloud qualified cloud?The path we follow to decide, one class of data at a time.
  1. Your data

    Classified: public, internal, sensitive

  2. Sensitive?

    One class at a time

    no: a well-configured European or public cloud

    yes: the next question

  3. An obligation?

    State, operator, 2026 decree, contract

    yes: a SecNumCloud qualified offer

    no: the next question

  4. Would a foreign request hurt you?

    yes: a SecNumCloud qualified offer

    no: a well-configured European or public cloud

A SecNumCloud qualified offer

In the ANSSI catalogue, still valid

The service you use inside the qualified scope

A European or public cloud

Well configured

In every case: a reversible architecture, to change class or provider

A sovereign cloud is a cloud whose data falls under European law alone: neither the provider nor its shareholders can be compelled by an authority outside the Union to hand over your data. In France, the benchmark is SecNumCloud, the qualification the French cybersecurity agency (ANSSI) grants to a specific cloud offer, for a limited period, when it meets its security requirements, including protection against non-European laws.

This article keeps the list of qualified offers up to date, from the ANSSI catalogue, and gives the path and the checks we follow to choose an offer.

Sovereign cloud: what actually protects your data

The US CLOUD Act, passed in March 2018, lets US authorities require a provider subject to US law to hand over the data it controls, wherever that data is stored. A data centre in Europe is therefore not enough: what matters is who controls the provider and which law it answers to. In France this is also called a "trusted cloud" (cloud de confiance): the national cloud strategy of May 2021 relies on SecNumCloud to define it.

What SecNumCloud requires from the provider

SecNumCloud qualifies an offer, not a whole company. The requirements in force, version 3.2 of 8 March 2022, include:

  • your data, and the technical data of the service (administrator identities, logs, directory, certificates), stored and processed in the European Union;
  • administration and supervision of the service from the Union; support may work from abroad, on a documented list of operations controlled from the Union;
  • a registered office, central administration and principal place of business in the Union;
  • shareholders from outside the Union holding no more than 24% of the capital and voting rights each, and no more than 39% together, with no veto and no majority on the governing bodies;
  • no subcontractor from outside the Union technically able to reach the data, and suppliers that guarantee the provider operational autonomy: being able to keep the service running with its own skills or with at least two suppliers, unless they are qualified themselves;
  • interfaces and first-level support in French, notice within a month of any change that affects these protections, and secure erasure of your data at the end of the contract, announced twenty-one days ahead.

SecNumCloud 3.1 or 3.2: what is the difference?

Version 3.2, published on 8 March 2022, mainly added protection against non-European laws: a whole chapter, 19.6, on the registered office, the capital thresholds, subcontractors from outside the Union and operational autonomy, plus adjustments to about twenty other chapters. Version 3.1 had brought in the General Data Protection Regulation (GDPR) and removed the "advanced" qualification level. The requirements to keep data in the Union did not change between the two.

Version 3.2 is the one in force. For a purchase, the useful question is therefore not the version but this one: is the specific offer you will use in the ANSSI catalogue, and until when?

SecNumCloud qualified offers as of 16 October 2026

The ANSSI catalogue updated on 16 October 2026 lists 30 qualified services from 13 providers. Here are the infrastructure, platform and container offers, the ones that host your applications:

Provider

Qualified offer

Type

Since

Until

Cegedim

CegNumCloud Secured IaaS

Infrastructure

2024-12-04

2027-12-04

Cloud Temple

PaaS Openshift

Platform

2025-05-30

2028-05-30

Cloud Temple

IaaS Secure Temple (VMware, open source, S3 object storage, HSM-KMS, bare metal, VPC, VMI)

Infrastructure

2026-07-31

2028-05-30

Ecritel

Ecritel Secure Cloud

Infrastructure

2026-09-22

2029-09-22

Numspot

Plateforme des services cloud de Numspot

Infrastructure

2026-07-31

2029-07-31

OVHcloud

Hosted Private Cloud powered by VMware

Infrastructure

2023-12-28

2026-12-29

OVHcloud

Bare Metal Pod

Infrastructure

2025-03-24

2028-03-24

OVHcloud

SNC Cloud Platform

Infrastructure

2026-07-31

2029-07-31

Orange Business Services

Cloud Avenue SecNum

Infrastructure

2025-07-11

2028-07-11

Orange Business Services

Cloud Avenue SecNum Dynamic

Infrastructure

2026-09-22

2029-09-22

Outscale

IaaS Cloud on Demand

Infrastructure

2023-11-30

2026-11-30

Thales Cloud Sécurisé (S3NS)

Cloud de confiance S3NS (PREMI3NS)

Infrastructure, platform and containers

2025-12-17

2028-12-17

Worldline

Worldline Cloud Services - Secured IaaS

Infrastructure

2025-03-24

2028-03-31

The catalogue also qualifies software services: the collaboration suites of Oodrive, Whaller and Wimi (Cloud Solutions), Ecritel’s backup service, and four Index Education applications for schools (Pronote, Pronote Primaire, Hyperplanning, EDT).

Worth watching. Two qualifications expire before the end of the year, Outscale’s IaaS Cloud on Demand (30 November 2026) and OVHcloud’s Hosted Private Cloud (29 December 2026): we will check their renewal at the next update. Bleu and Scaleway are not in the catalogue of 16 October 2026. Bleu aims for a qualification by the end of the year, according to its press office quoted by Next on 9 October 2026; Scaleway, which started its process in January 2025, has not given a date.

How to read this table: the qualification covers the named offer, not the provider’s other services. Check that the building blocks your applications need (managed databases, Kubernetes, object storage, GPUs) are inside the qualified scope.

Does your organisation have to use a qualified cloud?

For the French State, it is mandatory. The "cloud au centre" doctrine (circular of 31 May 2023) requires SecNumCloud, or an at least equivalent European qualification, for the sensitive data of government departments. The law of 21 May 2024 to secure and regulate the digital space (SREN, article 31) extended this requirement to State operators and to some public interest groupings. Its decree of 14 April 2026 names six of these groupings, including the French digital health agency, and defines the data concerned: data protected by a secret set by law (national defence, medical secrecy, trade secrets, investigations, privacy) or needed for the State’s essential missions, when a leak would cause concrete harm to public order, security, health or intellectual property. Temporary exemptions exist when no suitable offer is available.

For a private company, it is a choice, unless a contract or a customer requires it. At European level, the EU cloud certification scheme (EUCS) is still waiting for adoption, and no certificate is issued yet: SecNumCloud remains the benchmark in France.

The path we follow to decide, one class of data at a time:

  1. Classify your data: public, internal, sensitive.
  2. For each sensitive class, look for an obligation: a government department, a State operator or a grouping named by the decree, a contract or a customer that requires SecNumCloud.
  3. If there is one: an offer in the ANSSI catalogue, with the specific service you will use inside its scope.
  4. Otherwise, weigh the risk: would a request from a foreign State for this data put you in difficulty? If so, a qualified cloud; if not, a well-configured European or public cloud is often enough.
  5. In every case, a reversible architecture, so you can change class or provider without rebuilding everything.

What we check before choosing a qualified offer

  1. The exact scope. The qualification covers the offer you will use, and its end date in the catalogue covers the length of your project.
  2. The services you need. Managed databases, containers, object storage, GPUs: whatever sits outside the qualified scope sits outside the protection.
  3. Administration and support. Where the service is run from, and the list of operations support may carry out from abroad, which the provider has to document.
  4. The exit. Open formats, infrastructure described as code, and exit and erasure terms written into the contract.
  5. The real cost. Worked out offer by offer on your own usage, rather than on list prices.

Sovereign AI: where to run your models and agents

The same questions apply to AI: where the models run, where the data your agents read goes, where their logs are kept. In the catalogue of 16 October 2026, no generative AI service is qualified as such: the qualification covers the infrastructure it runs on. Two routes exist:

  • run open models yourself on a qualified infrastructure offer that provides GPUs, after checking that they are inside its scope;
  • choose a managed AI service that is going through qualification: on 11 June 2026, Numspot announced managed AI services (models, document search bases, agents) and work with Mistral AI, on a platform whose managed services aim for qualification by the end of the year; its infrastructure offer has been qualified since 31 July 2026.

Either way, check where requests and logs go, and who can reach them. An agent platform can be hosted on qualified infrastructure, with models chosen accordingly: that is the approach of our page Agentic platform, and our article on agentic AI explains what an agent is.

Migrating without rewriting everything

  • Classify your data and applications by sensitivity.
  • Choose a target per class: a qualified cloud for what requires it, a European or public cloud for the rest.
  • Set up a foundation described as code on the target: accounts, identities, connectivity and security rules.
  • Migrate in waves, with a way back at each switch.

Our offers Your data hosted where you decide, A well-organised cloud from day one and Your applications on the cloud of your choice follow these steps, and the page Cloud foundation describes our work on the subject. To talk it through: the free scoping day.

Frequently asked questions

What is SecNumCloud?

The qualification ANSSI grants to a specific cloud offer, for a limited period, when it meets its requirements for security and protection against non-European laws, currently version 3.2.

Is a European cloud necessarily sovereign?

No. You need to look at who controls the provider, where the service is run from and which law it answers to. A European provider owned or steered from abroad can remain exposed to non-European laws.

Is SecNumCloud mandatory for a private company?

No, unless a contract or a customer requires it. It is a choice to make one class of data at a time: a qualified cloud for what is sensitive, a well-configured European or public cloud for the rest.

Are Bleu and S3NS SecNumCloud qualified?

In the ANSSI catalogue of 16 October 2026, the Cloud de confiance S3NS offer from Thales Cloud Sécurisé has been qualified since 17 December 2025, for infrastructure, platform and containers. Bleu is not in it yet: it aims for a qualification by the end of the year. Check the catalogue when you choose.

Sources

Written with an AI assistant from the sources cited, facts checked and reviewed by Mehdi Chafik on 26 October 2026.