Back to Articles

NIS2

NIS2 in Spain: Referred to the EU Court, and What to Do While the Law Is Pending

12 min read

On 8 July 2026 the European Commission referred Spain to the Court of Justice for failing to transpose NIS2. Where things stand, what already applies, what the draft law adds and five measures Spanish companies can start now.

nis2
spain

On 8 July 2026 the European Commission referred Ireland, Spain, France and the Netherlands to the Court of Justice of the EU for failing to transpose the NIS2 Directive, and asked the Court to impose a lump sum and daily penalty payments. For Spain it was the third step of an infringement procedure that began in November 2024. Looking at it from November 2026, the situation has not changed in substance: the Spanish law that should transpose NIS2, the Ley de Coordinación y Gobernanza de la Ciberseguridad, is still not in the Boletín Oficial del Estado. This article sets out the timeline, what already applies to Spanish companies today, what the draft law adds, and why waiting for the final text is the wrong strategy. For the directive itself, see our complete NIS2 guide.

Key Takeaways

  • Spain missed the NIS2 transposition deadline of 17 October 2024 and was referred to the CJEU on 8 July 2026, together with Ireland, France and the Netherlands.
  • The draft Ley de Coordinación y Gobernanza de la Ciberseguridad was approved on 14 January 2025 as an anteproyecto; we found no publication in the BOE as of this writing.
  • Rules already apply: RDL 12/2018 and RD 43/2021 (the NIS1 framework), the ENS for the public sector and its suppliers, the GDPR and, for finance, DORA.
  • The Article 21 measures take months to put in place. Companies that start when the law is published will start late.
  • Customers in countries that have transposed NIS2 are already asking their suppliers for evidence, including Spanish suppliers.

Where Things Stand, Date by Date

DateEvent
16 January 2023NIS2 (Directive (EU) 2022/2555) enters into force
17 October 2024Deadline for Member States to transpose it
28 November 2024The Commission sends Spain a letter of formal notice
14 January 2025The Council of Ministers approves the anteproyecto of the Ley de Coordinación y Gobernanza de la Ciberseguridad, under the urgent procedure
21 February 2025The draft is notified to the Commission under the TRIS procedure (2025/0104/ES); the standstill period ends on 26 May 2025
7 May 2025The Commission sends a reasoned opinion
17 March 2026The Council of Ministers sends a separate bill on critical entities (protection and resilience) to the Cortes
8 July 2026The Commission refers Spain to the CJEU and asks for financial penalties
November 2026We found no publication of the NIS2 law in the BOE

Sources: the European Commission's announcement of the referral, La Moncloa's summaries of the Councils of Ministers of 14 January 2025 and 17 March 2026, and the TRIS notification.

What the Referral Means, and What It Does Not

A referral to the Court is a dispute between the Commission and the Spanish State. If the Court agrees, Spain may have to pay a lump sum and a daily penalty until it notifies full transposition. It does not, by itself, impose new obligations on Spanish companies: as a rule, a directive that has not been transposed does not create direct obligations for private parties. That is a reason for legal caution, not for operational complacency. The law will arrive, the obligations of NIS2 are already known in detail, and the time needed to meet them does not shrink because the text is late.

What Already Applies Today

  • Royal Decree-Law 12/2018 and Royal Decree 43/2021. The transposition of the first NIS Directive is still in force for operators of essential services and digital service providers. RD 43/2021 develops it, including how incidents are classified and notified.
  • The Esquema Nacional de Seguridad (ENS), Royal Decree 311/2022. It applies to the public sector and to private companies that provide services or solutions to it. For many suppliers, it is already the most demanding framework they face.
  • The GDPR and the Spanish data protection law, with breach notification to the AEPD within 72 hours.
  • DORA, which has applied directly to financial entities since 17 January 2025 and reaches their ICT providers through contracts.

The threat level does not wait for the legislator either. According to INCIBE, its CERT handled 122,223 incidents in 2025, 26% more than in 2024, including 392 ransomware cases and 401 incidents affecting essential and important operators, a third of them in banking.

What the Draft Law Adds

Based on the government's summary and on the text notified to the Commission, the anteproyecto:

  • Applies to public and private entities that are tax-resident in Spain, and to entities resident in another EU State that operate or provide services in Spain.
  • Distinguishes sectors of high criticality (energy, transport, banking and financial markets, health, water, digital infrastructure and technology services, public administration, nuclear industry) from other critical sectors (postal and courier services, waste management, food, digital service providers, scientific research, private security).
  • Requires an individual risk assessment, security measures, notification of significant incidents (including those at external providers) and information to service recipients about threats that may affect them.
  • Creates the Centro Nacional de Ciberseguridad to direct and coordinate the system and to manage cyber crises, with supervision shared among several control authorities, including the Oficina de Coordinación de Ciberseguridad and the Centro Criptológico Nacional.
  • Creates the role of information security officer in each entity.

The text can still change in Parliament. The core does not, because it comes from the directive: Article 21 measures, Article 23 reporting and management accountability under Article 20.

Would You Be in Scope?

NIS2 combines sector and size. As a rule, it covers medium and large enterprises in the sectors of Annexes I and II: at least 50 employees, or annual turnover and balance sheet above EUR 10 million. Some entities are in scope whatever their size, such as providers of public electronic communications networks, trust service providers, DNS service providers and TLD registries. Large entities in Annex I sectors are generally essential; the others are generally important. The Spanish draft follows the same logic, and our guide to essential and important entities walks through the sectors. Two practical points: size is counted at group level when companies are linked, and being out of scope does not protect you from your customers' requirements.

Why Waiting Is a Mistake

Article 21 of NIS2 lists ten groups of measures: risk analysis and security policies; incident handling; business continuity, backups and crisis management; supply chain security; security in acquisition, development and maintenance, including vulnerability handling; procedures to assess the effectiveness of measures; basic cyber hygiene and training; cryptography; human resources security, access control and asset management; and multi-factor authentication and secure communications. None of these can be bought and installed in a week.

Three further reasons not to wait:

  • Your customers do not wait. Article 21(2)(d) makes supply chain security an obligation for entities in scope. Italian, French or German customers that are already subject to their national law are sending questionnaires to their suppliers, Spanish ones included. Our article on NIS2 supply chain security explains what they ask.
  • Management will be accountable. Article 20 requires management bodies to approve and oversee the measures and to follow training.
  • The ceilings are set by the directive. Maximum fines of at least EUR 10 million or 2% of worldwide turnover for essential entities, and EUR 7 million or 1.4% for important entities. Our article on NIS2 penalties covers the details.

Five Measures to Start Now

  1. Know what you expose. Build an inventory of internet-facing assets, including the ones IT did not deploy, and verify which vulnerabilities are real. Everything else depends on it.
  2. Appoint the person and the governance. Name who will act as information security officer, and give management a short, regular report.
  3. Write the incident procedure. Define who decides that an incident is significant and who notifies, and practise the NIS2 sequence: early warning within 24 hours, notification within 72 hours, final report within one month. The RD 43/2021 taxonomy already gives you the vocabulary.
  4. Assess your critical suppliers. Start with those who have remote access or hold your data.
  5. Test that it works. Article 21(2)(f) asks you to assess the effectiveness of your measures. A penetration test of your external perimeter, phishing simulations and multi-factor authentication on every remote access are concrete, verifiable evidence.

For a structured plan, our NIS2 guide for SMEs and the 14-step checklist go into more detail.

A Note for Groups Operating in Italy and Spain

Italy transposed NIS2 with Legislative Decree 138/2024. ACN sent its inclusion notices from April 2025, and the baseline security measures had to be in place within 18 months, by 31 October 2026. Under NIS2, an entity generally falls under the jurisdiction of the Member State in which it is established, so an Italian parent and its Spanish subsidiary may follow two different national rulebooks, one of which is not yet written. The practical answer is one set of group controls mapped twice: to ACN's measures in Italy and, in Spain, to the ENS and the Spanish law once published. A control that is already documented and tested for Italy usually needs only the Spanish mapping.

How Orizon Can Help

Orizon works from Brescia and from Madrid, with the Spanish market in mind. Fireline, our autonomous external penetration test, produces technical, executive, remediation and compliance editions, also in Spanish. For Spain, the compliance edition uses the ENS measures and the RD 43/2021 incident taxonomy; for Italy, ACN's baseline measures. RECON provides technical evidence for the Article 21 measures across your external, internal and cloud surface. Neither claims compliance on your behalf: they give you evidence you can show. The NIS2 compliance page shows how the pieces fit together.

Checklist

  1. Check whether your sector and size would put you in scope under the draft law.
  2. Find out whether you are already covered by RDL 12/2018, the ENS or DORA.
  3. Inventory your exposed assets and verified vulnerabilities.
  4. Name an information security officer and set up regular reporting to management.
  5. Write and rehearse the 24-hour, 72-hour and one-month reporting sequence.
  6. Assess critical suppliers and prepare answers for your own customers' questionnaires.
  7. Test the effectiveness of your measures and keep the evidence.

If you want to start with evidence rather than paperwork, the NIS2 compliance page explains how RECON and Fireline document the Article 21 measures, and our Madrid team can walk you through it.

nis2
spain
espana
cjeu
ens
compliance
regulation