Procurement

From principle to procurement

How to make sovereignty a structured, defensible part of buying decisions without breaking procurement law, and without giving up on quality.

A practical approach

Sovereignty is a criterion to add, not a reason to drop the others. European technology should still win on its merits.

Keep evaluating on

  • Security
  • Quality and functionality
  • Cost (total cost of ownership, including exit)
  • Support
  • Interoperability
  • Operational resilience
  • Vendor viability

And add one more question

What are the strategic consequences of this procurement decision for Europe's technological capability?

Where to start

ClassifyUse the sovereignty assessment to find the systems where dependency matters most.
Use natural momentsAct on new purchases and contract renewals. Avoid rip-and-replace without a strong reason.
Build in exit optionsRequire data export, open standards, escrow and change-of-control clauses in every contract.
Evaluate European optionsInvite European suppliers to tender and document the result, including when they do not win.
DiversifyAvoid having one supplier for identity, endpoint, email and cloud at the same time.
Review regularlyOwnership changes. Re-check critical suppliers every year and on every acquisition.

Public buyers: what you can and cannot require

Public procurement law is the most common reason why “buy European” stays a slogan. Understanding the rules makes sovereignty requirements more effective.

The rules

  • Equal treatment. “Contracting authorities shall treat economic operators equally and without discrimination.”1
  • International agreements. For procurement covered by the WTO Government Procurement Agreement (GPA) or trade agreements, suppliers from the other parties must receive treatment “no less favourable” than EU suppliers.1 The United States is a GPA party.2
  • No agreement, no right to equal treatment. The Court of Justice held in 2024 (Kolin, C-652/22) that suppliers from third countries without a procurement agreement with the EU cannot claim equal treatment, and that contracting entities may reflect that difference in the procurement documents.3

In practice, a requirement such as “the supplier must be an EU company” is generally not permitted in procurement covered by these agreements.

What you can usually require

Objective, proportionate and non-discriminatory requirements, linked to the subject of the contract, for example:

  • Operation fully on-premises or offline, and internal update mirroring
  • Customer-held encryption keys
  • Data location and restrictions on support access
  • Data and configuration export, open standards and documented APIs
  • Exit plans, escrow and change-of-control clauses
  • Security certifications and, for sensitive cloud workloads, protection against access by third-country authorities

Example: France's state cloud doctrine requires that, for particularly sensitive data, commercial cloud offers hold SecNumCloud (or an equivalent European) qualification and be protected against unauthorised access by third-country public authorities.45 Defence and security procurement and essential security interests follow separate rules.

What may change

In September 2026 the European Commission proposed a Public Procurement Act. It includes a horizontal European preference framework “in line with the Union's international legal obligations” and would let public buyers address cybersecurity and “undue third-country influence”. Suppliers covered by the EU's international procurement commitments would keep full access.67 It is a proposal, not law. Always involve your legal and procurement specialists. This website is not legal advice.

Printable

Digital Sovereignty Procurement Checklist

25 questions to put to suppliers and to your own team. Use it in requirements, supplier questionnaires and risk assessments.

Ownership and jurisdiction

Data and access

Operability and independence

Openness and exit

Continuity and strategy

Policy & regulation

Regulatory requirement vs. strategic procurement choice

This distinction is essential. EU cybersecurity and data law sets requirements on security, risk management and data protection. None of the laws below requires organisations to buy European technology. Choosing European is a strategic decision that these laws can inform, but not mandate.

Regulatory requirement

What the law obliges you to do: manage supply-chain risk, protect personal data, report incidents, ensure products meet security requirements, and be able to switch cloud providers. It applies equally to European and non-European suppliers.

Strategic procurement choice

What you decide to do beyond the law: giving weight to jurisdiction, ownership, European capability and long-term independence, within the limits of procurement law.

NIS2 Directive — Directive (EU) 2022/25558

Regulatory requirement

Essential and important entities must include supply-chain security in their risk management, “including security-related aspects concerning the relationships between each entity and its direct suppliers”, and take into account each supplier's vulnerabilities and secure development practices. EU-level coordinated risk assessments can include non-technical risk factors such as third-country influence.

Strategic choice it can inform

Use the supply-chain risk assessment NIS2 already requires to document jurisdiction, ownership and dependency, and give weight to suppliers that reduce those risks.

Does it require buying European? No.

Cyber Resilience Act — Regulation (EU) 2024/28479

Regulatory requirement

Cybersecurity requirements for products with digital elements on the EU market, including due diligence on third-party and open-source components. Reporting obligations apply from 11 September 2026, and the regulation applies in full from 11 December 2027. It applies equally to EU and non-EU manufacturers.

Strategic choice it can inform

Use CRA conformity as a security baseline for every supplier. Origin is not a CRA criterion, so sovereignty remains a separate consideration.

Does it require buying European? No.

EU Cybersecurity Act and ENISA — Regulation (EU) 2019/88110

Regulatory requirement

Gives ENISA a permanent mandate and creates EU cybersecurity certification, which is voluntary unless other law says otherwise. The first scheme, EUCC, applies from 27 February 2025.11 The cloud scheme EUCS has not been adopted.12 A revision proposed in January 2026 would add an ICT supply-chain security framework to address risks from high-risk third-country suppliers. It is still a proposal.13

Strategic choice it can inform

Ask for EU certifications where they exist. Follow the revision: if adopted, it may formalise non-technical supplier risk for critical sectors.

Does it require buying European? No.

GDPR — Regulation (EU) 2016/67914

Regulatory requirement

Controllers must only use processors “providing sufficient guarantees”. International transfers need a legal basis, and third-country court orders are only enforceable on the basis of an international agreement (Art. 48). After Schrems II, transfers must be assessed against the law of the recipient country.15 The EU-US Data Privacy Framework is in force, and the General Court dismissed a challenge to it in 2025.1617

Strategic choice it can inform

The GDPR does not require EU suppliers or data localisation. Choosing suppliers outside the reach of foreign disclosure laws is a risk decision, not a legal obligation.

Does it require buying European? No.

Data Act — Regulation (EU) 2023/285418

Regulatory requirement

Applies from 12 September 2025. Cloud providers must remove obstacles to switching and support portability and interoperability. From 12 January 2027 they may no longer charge switching fees. They must also take measures against unlawful third-country governmental access to non-personal data.19

Strategic choice it can inform

Lower switching barriers make it more realistic to diversify, or to move to European providers, at contract renewal.

Does it require buying European? No.

DORA — Regulation (EU) 2022/255420

Regulatory requirement

Applies from 17 January 2025 to financial entities. They must manage ICT third-party and concentration risk, consider the law of third countries where providers are established, and have exit strategies. DORA explicitly “does not impose a data localisation obligation”.

Strategic choice it can inform

Concentration-risk and substitutability analysis under DORA is a natural place to assess dependency on non-European providers.

Does it require buying European? No.

EU sovereignty initiatives (policy, not obligations)

Digital Decade

2030 targets include 10,000 climate-neutral, highly secure edge nodes and 75% of EU enterprises using cloud, big data or AI.21

Tech Sovereignty Package

Proposed in June 2026, including a Cloud and AI Development Act with an EU-wide framework to assess cloud and AI sovereignty. These are proposals.2223

IPCEI-CIS

An Important Project of Common European Interest approved in December 2023 in which seven Member States support an interoperable European cloud and edge ecosystem.24

Gaia-X

An initiative for federated, trustworthy data infrastructure based on common European rules and standards.25

EU 5G Toolbox

Coordinated measures on 5G supplier risk (2020). In 2023 the Commission stated that Huawei and ZTE represent materially higher risks than other 5G suppliers.2627

ENISA

The EU Agency for Cybersecurity supports policy, certification and operational cooperation between Member States.28