Skip to main content
Back to overview

France and Spain Referred to the CJEU Over NIS2: What Suppliers Should Do Now

By NIS2Certify
nis2francespaincjeusupply-chainmsp
France and Spain Referred to the CJEU Over NIS2: What Suppliers Should Do Now

On 9 June 2026, the European Commission referred France and Spain to the Court of Justice of the European Union for failing to transpose NIS2 into national law. More than 18 months after the deadline, the EU's two largest economies still don't have the directive on their statute books — and now the only body that can fine a member state for ignoring EU law is involved.

If you advise organisations operating in France or Spain, this is not a story about Brussels procedure. It changes how you should be scoping NIS2 readiness work in those markets right now. Here's what the referral actually means and what to tell your clients this week.

The referral is the last stop, not a warning shot

The Commission doesn't go to the CJEU first. The path to a referral is long and deliberate, and France and Spain have now travelled all of it.

The transposition deadline was 17 October 2024. Only four member states met it. The Commission opened infringement proceedings against 23 countries on 28 November 2024 with formal letters of notice. It escalated on 7 May 2025, issuing reasoned opinions to 19 governments — the formal "you have two months to comply" stage. France and Spain were on that list, didn't comply, and have now been referred to the court.

Referral is the final stage. The CJEU is the only body that can order a member state to pay for breaching EU law, through lump-sum fines and daily penalty charges that accrue until the law is fixed. That financial pressure is now bearing down on Paris and Madrid, which means national transposition is far more likely to land in 2026 than to slip again.

NIS2 transposition by country

  • AustriaIn force
    • In force since October 1, 2026
    • Act: NISG 2026 (BGBl. I Nr. 94/2025)
    • Registration due December 31, 2026

    Authority: Federal Office for Cybersecurity · Source

  • NetherlandsIn force
    • In force since August 15, 2026
    • Act: Cyberbeveiligingswet (Stb. 2026, 187)
    • Registration required, no transition period

    Authority: NCSC (MijnNCSC) · Source

  • LuxembourgIn force
    • In force since May 10, 2026
    • Act: Law of 5 May 2026
    • Registration due July 10, 2026

    Authority: ILR (CSSF for finance) · Source

  • PolandIn force
    • In force since April 3, 2026
    • Act: UKSC (Dz.U. 2026 poz. 252)
    • Registration due October 3, 2026
    • Measures due April 3, 2027

    Authority: Minister Cyfryzacji (Wykaz KSC) · Source

  • PortugalIn force
    • In force since April 3, 2026
    • Act: Decree-Law 125/2025 (RJC)

    Authority: CNCS · Source

  • BulgariaIn force
    • In force since February 13, 2026
    • Act: Cybersecurity Act amendment (State Gazette No 17/2026)

    Authority: Ministry of e-Government · Source

  • MaltaIn force
    • In force since January 23, 2026
    • Act: S.L. 460.41

    Authority: Critical Infrastructure Protection Department · Source

  • SwedenIn force
    • In force since January 15, 2026
    • Act: SFS 2025:1506

    Authority: NCSC-SE · Source

  • EstoniaIn force
    • In force since January 1, 2026
    • Act: Cybersecurity Act (KüTS) amendment
    • Registration within 3 months

    Authority: RIA · Source

  • GermanyIn force
    • In force since December 6, 2025
    • Act: NIS2UmsuCG
    • Registration due March 6, 2026
    • 17,729 registered by June 30, 2026

    Authority: BSI · Source

  • CzechiaIn force
    • In force since November 1, 2025
    • Act: Act No 264/2025 Coll.
    • Registration within 60 days

    Authority: NÚKIB · Source

  • DenmarkIn force
    • In force since July 1, 2025
    • Act: NIS 2 Act No 434 of 6 May 2025
    • Registration due October 1, 2025

    Authority: Danish Agency for Societal Security · Source

  • SloveniaIn force
    • In force since June 19, 2025
    • Act: ZInfV-1 (OG 40/25)
    • Registration within 30 days

    Authority: URSIV · Source

  • CyprusIn force
    • In force since April 25, 2025
    • Act: Law 60(I)/2025

    Authority: Digital Security Authority · Source

  • FinlandIn force
    • In force since April 8, 2025
    • Act: Cybersecurity Act 124/2025
    • Registration due May 8, 2025
    • Measures due July 8, 2025

    Authority: Traficom (NCSC-FI) · Source

  • HungaryIn force
    • In force since January 1, 2025
    • Act: Act LXIX of 2024

    Authority: SZTFH · Source

  • SlovakiaIn force
    • In force since January 1, 2025
    • Act: Act No 366/2024 Coll.
    • Registration within 60 days

    Authority: NBÚ · Source

  • RomaniaIn force
    • In force since December 31, 2024
    • Act: GEO 155/2024 (Law 124/2025)
    • Registration within 30 days

    Authority: DNSC · Source

  • GreeceIn force
    • In force since November 27, 2024
    • Act: Law 5160/2024 (Gazette A' 195)

    Authority: National Cybersecurity Authority · Source

  • BelgiumIn force
    • In force since October 18, 2024
    • Registration due March 18, 2025

    Authority: CCB · Source

  • LithuaniaIn force
    • In force since October 18, 2024
    • Act: Law No XIV-2902

    Authority: NCSC (MoND) · Source

  • ItalyIn force
    • In force since October 16, 2024
    • Act: D.Lgs. 138/2024
    • Baseline measures due by October 2026 (entities listed in 2025)

    Authority: ACN · Source

  • LatviaIn force
    • In force since September 1, 2024
    • Act: National Cybersecurity Law

    Authority: National Cybersecurity Centre · Source

  • CroatiaIn force
    • In force since February 15, 2024
    • Act: Cybersecurity Act (OG 14/2024)

    Authority: NCSC (SOA) · Source

  • FranceNot yet transposed
    • Senate adopted the law on March 12, 2025
    • Regulator published its framework on March 17, 2026
    • Referred to the Court of Justice on July 8, 2026
    • Pre-registration open

    Authority: ANSSI · Source

  • SpainNot yet transposed
    • Draft bill approved on January 14, 2025
    • Referred to the Court of Justice on July 8, 2026
    • The NIS1 regime still applies

    Authority: CCN / INCIBE · Source

  • IrelandNot yet transposed
    • Referred to the Court of Justice on July 8, 2026
    • Bill not yet enacted

    Authority: NCSC Ireland · Source

Status as of September 28, 2026. Other member states: see the country-by-country timeline.

France and Spain took different roads to the same place

The two delays don't have the same cause, and that matters for how you predict the timeline.

Spain approved a draft cybersecurity bill in the Council of Ministers in January 2025, but the final text still hasn't been published. The law is expected to take effect at some point during 2026. The framework exists on paper — what's missing is promulgation.

France folded NIS2 into a broader law on the resilience of critical infrastructure, a wider legislative package that has not been fully promulgated. The directive is tied to a larger, slower-moving vehicle, which is why France's timing is harder to call.

For a consultant, the practical read is this: both countries will almost certainly have law in force within the next 12 months, and the CJEU referral makes further slippage politically expensive. Treat the absence of a national law as a timing question, not a reason to wait.

"No national law yet" is the most dangerous thing a client can believe

The single biggest risk in France and Spain right now is the client who reads the headlines and concludes they have a reprieve. They don't.

NIS2 obligations don't only flow from the country a company is headquartered in. If your client sells to, or operates infrastructure for, entities in member states that have transposed — Germany, Italy, Belgium, the Netherlands, and most of the bloc — those obligations already apply through the supply chain. A French managed service provider serving German essential entities is being asked for Article 21 evidence today, regardless of what France has or hasn't passed.

The directive's supply-chain provisions are the mechanism. Essential and important entities must manage the security of their suppliers, which means they push contractual security requirements down to vendors irrespective of where those vendors sit. The obligation cascades from the compliant jurisdiction into the non-compliant one.

NIS2 Penalty Escalation — Beyond the Fine

!

Trigger event

Non-Compliance Detected or Incident Occurs

A supervisory authority identifies a compliance gap or an organisation fails to meet NIS2 requirements

Authorities can impose
▼
Non-Monetary Penalties
1

Compliance orders with binding deadlines

2

Mandatory security audits at your expense

3

Public disclosure of violations

4

Binding instructions on specific security measures

Escalates to
▼
Operational & Personal Consequences
1

Suspension of certifications or operating licences

2

Temporary ban on management functions for individuals

3

Public naming of responsible natural persons

Trigger
Non-monetary
Operational / personal

So the honest message to a French or Spanish client is: the national law is coming, your customers in other member states are already bound, and the contractual requirements are reaching you now. The gap between "our country hasn't transposed" and "we have no obligations" is exactly where unprepared organisations get caught.

Determining scope when the national text isn't final

The wrinkle in France and Spain is that the final national definitions — sector annexes, size thresholds, the line between essential and important entities — aren't locked. Scope determination normally leans on the transposing law's specifics. Here you don't have them yet.

Work from the directive itself. NIS2's sector lists and the medium-enterprise threshold (50 or more employees, or fewer than 50 with both annual turnover and balance sheet total above €10 million, with carve-outs for certain critical providers regardless of size) are set at EU level and won't move much in transposition. A client that is clearly in scope under the directive will be in scope under the French or Spanish law. Build the readiness assessment on the directive's baseline now, and treat the eventual national text as a refinement rather than a starting point.

Does NIS2 Apply to Your Organisation?

1

Does your organisation operate in an essential or important sector (energy, transport, health, digital infrastructure, etc.)?

Yes ↓No →
2

Does your organisation have 50 or more employees, or both an annual turnover and a balance sheet total exceeding €10 million?

Yes ↓No →
3

Is your organisation a critical infrastructure provider or a qualified trust service provider?

Yes ↓No →
✗

NIS2 does not directly apply to your organisation.

✓

NIS2 applies to your organisation as an Essential or Important Entity.

!

NIS2 may apply to your organisation — seek legal advice to confirm your status.

Applies
Possibly applies
Does not apply

This is also where you protect your own credibility. Tell clients which conclusions are firm (driven by the directive and unlikely to change) and which are provisional (dependent on national specifics still to be published). A gap analysis built on the directive will be 90% durable; flag the 10% that may shift.

What to do with French and Spanish clients this week

The referral is a prompt, not a fire drill. Concrete moves:

Map customer exposure first. For each client, list the member states their customers and operations touch. Any compliant jurisdiction in that list means live obligations today, national law or not. This is usually the fastest way to show a sceptical client why "we'll wait for the law" is the wrong posture.

Run the gap analysis against the directive baseline. Don't wait for the national text. The Article 21 measures — risk management, incident handling, business continuity, supply-chain security, vulnerability handling, basic cyber hygiene, MFA — are EU-level and stable. Assess against those.

Get supplier contract language in order. The supply-chain cascade arrives through contracts. Clients on the receiving end of new security clauses from their German or Italian customers need to be able to answer them. Clients who are themselves essential or important entities need to start pushing requirements down to their own vendors.

Document the readiness posture now so that when the French or Spanish law is published — likely with a short runway to enforcement — your client moves from "starting" to "demonstrating" rather than scrambling. Organisations that treated the delay as breathing room will find the enforcement window uncomfortably tight.

The CJEU referral tells you the delay is ending. The member states that dragged their feet are the ones whose enforcement is most likely to be sharp once the law lands, precisely because the Commission has already lost patience. Position your clients to be ready before the text is final, not after.

If you want a fast, structured read on whether a client is in scope and where the biggest gaps sit, run them through the NIS2 readiness quick scan — it works off the directive baseline, which is exactly what you need while France and Spain finish their national laws.

For the wider picture on how the directive's supply-chain obligations move between jurisdictions, see our guide to NIS2 supply chain security and supplier contracts under Article 21.

Still have a question?

Answers are generated from our articles and are not legal advice. Do not enter personal or confidential data.