Product team testing a smart-speaker-style device with microphones in an anechoic chamber

Cyber Resilience Act

NIS2 Implementing Regulation (EU) 2024/2690, explained

Last updated:

Commission Implementing Regulation (EU) 2024/2690, adopted by the European Commission on 17 October 2024, turns a slice of the NIS2 Directive's Article 21(2) cybersecurity risk-management measures into detailed technical and methodological requirements for a defined list of digital infrastructure and digital service providers. Per the European Commission's own description of the regulation, it applies to DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online marketplaces, online search engines and social networking services platforms, and trust service providers — the digital-infrastructure and digital-provider categories named in NIS2's Annex I. Unlike the Directive itself, which member states had to transpose into national law by 17 October 2024, an EU implementing regulation is directly applicable law for the entities it names, with no national transposition step required.

Key takeaways

  • Published in the Official Journal on 18 October 2024, it entered into force on the twentieth day after publication (7 November 2024) and repealed the NIS1-era Implementing Regulation (EU) 2018/151 (Articles 15 and 16).
  • The official text organises the Annex into 13 numbered sections, each tied back to a point of NIS2 Article 21(2).
  • Articles 3 to 14 decide when one of these providers must notify under NIS2 Article 23.
  • Every Annex section applies to every in-scope entity.

Why does a separate implementing regulation exist?

NIS2 Article 21(2) lists ten broad categories of cybersecurity risk-management measures that every essential and important entity must implement, from risk analysis policies and incident handling to supply chain security and multi-factor authentication. Those categories are high-level on purpose, so one Directive text can apply to energy, health, transport, banking and digital infrastructure alike. Article 21(5) told the Commission to adopt implementing acts with technical and methodological detail for the digital entity types listed above, and Article 23(11) let it define when their incidents are "significant." Regulation 2024/2690 does both. Per the Commission's own page, it sets out "technical and the methodological requirements" for those measures.

Published in the Official Journal on 18 October 2024, it entered into force on the twentieth day after publication (7 November 2024) and repealed the NIS1-era Implementing Regulation (EU) 2018/151 (Articles 15 and 16). Recital 3 states that the Annex is based on ISO/IEC 27001, ISO/IEC 27002, ETSI EN 319 401 and CEN/TS 18026:2024.

What does the Annex actually cover?

The official text organises the Annex into 13 numbered sections, each tied back to a point of NIS2 Article 21(2). Counting the lowest-level numbered points gives about 160 requirements, many with lettered sub-items.

# Annex section NIS2 Art. 21(2) point Subsections
1 Policy on the security of network and information systems (a) Policy; roles, responsibilities and authorities
2 Risk management policy (a) Risk management framework; compliance monitoring; independent review
3 Incident handling (b) Policy; monitoring and logging; event reporting; event assessment and classification; incident response; post-incident reviews
4 Business continuity and crisis management (c) Continuity and disaster recovery plan; backup and redundancy; crisis management
5 Supply chain security (d) Supply chain security policy; directory of suppliers and service providers
6 Security in acquisition, development and maintenance (e) Acquisition of ICT services or products; secure development life cycle; configuration management; change management; security testing; patch management; network security; network segmentation; malicious software; vulnerability handling and disclosure
7 Assessing the effectiveness of measures (f) Single policy-and-procedures section
8 Basic cyber hygiene and security training (g) Awareness and hygiene; security training
9 Cryptography (h) Single policy-and-procedures section
10 Human resources security (i) HR security; background verification; termination or change of employment; disciplinary process
11 Access control (i), (j) Policy; access rights; privileged accounts; administration systems; identification; authentication; multi-factor authentication
12 Asset management (i) Classification; handling; removable media; inventory; return or deletion on termination
13 Environmental and physical security (c), (e), (i) Supporting utilities; physical and environmental threats; perimeter and physical access control

Source: Commission Implementing Regulation (EU) 2024/2690, Annex, OJ L of 18 October 2024, read 11 November 2026.

Section 6 is the longest and the one most relevant to anyone who builds or supplies technology. Some examples of how concrete it gets: point 1.1.2 requires the management body to review the security policy "at least annually"; point 6.6.1 requires that patches be tested before production and "come from trusted sources and are checked for integrity"; and point 6.8.2 asks for a separate administration network, a demilitarised zone, and production kept apart from development and testing.

When does an incident count as significant?

Articles 3 to 14 decide when one of these providers must notify under NIS2 Article 23. An incident is significant if it meets any horizontal criterion in Article 3, or the entity-specific criterion for its type:

Criterion Threshold
Direct financial loss (Art. 3(1)(a)) More than EUR 500,000 or 5% of annual turnover, whichever is lower
Trade secrets, death, health (Art. 3(1)(b)–(d)) Exfiltration of trade secrets; death; considerable damage to a person's health
Malicious access (Art. 3(1)(e)) Successful, suspectedly malicious unauthorised access capable of severe operational disruption
Recurring incidents (Art. 4) Two or more in 6 months, same apparent root cause, together over the financial-loss threshold
DNS service providers (Art. 5) Resolution service completely unavailable for more than 30 minutes, or average response above 10 seconds for more than an hour
Cloud, CDN, managed and managed security services (Arts. 7, 9, 10) Completely unavailable for more than 30 minutes, or limited for more than 5% of EU users (or 1 million, whichever is smaller) for more than an hour
Data centre service providers (Art. 8) Completely unavailable; limited for more than an hour; or physical access compromised
Trust service providers (Art. 14) Completely unavailable for more than 20 minutes, or unavailable for more than an hour per calendar week

Scheduled maintenance does not count (Art. 3(2)). Each entity-type article also lists compromises of data integrity, confidentiality or authenticity, often conditioned on suspected malicious action. See our NIS2 Directive guide for the 24-hour, 72-hour and one-month reporting stages these thresholds trigger.

How does proportionality work in practice?

Every Annex section applies to every in-scope entity. Article 2(2) scales the depth: entities "take due account of the degree of their exposure to risks, their size and the likelihood of occurrence of incidents and their severity." Recital 5 adds that an entity too small to meet a requirement, such as segregating conflicting duties, may use compensating measures like targeted management oversight or more logging.

Some Annex points are qualified with "where appropriate," "where applicable" or "to the extent feasible." For those, Article 2(2) imposes a documentation duty: an entity that decides not to apply such a requirement "shall in a comprehensible manner document its reasoning." A missing control without a written reason is a finding; a documented, risk-based exception is not.

What will in-scope buyers ask their product suppliers for?

The regulation binds cloud, data centre, managed service and other listed providers, not the companies that sell them hardware, firmware or software. But three Annex points tell those buyers what to require, so suppliers receive the questions in tenders and contracts:

Annex point What the buyer must require or obtain What a supplier should have ready
5.1.4 (contract clauses) Cybersecurity requirements; notification "without undue delay" of incidents that put the buyer at risk; right to audit or receive audit reports; an obligation to handle vulnerabilities; subcontracting rules A disclosure policy, an incident-notification contact and time commitment, audit reports or certificates
6.1.2 (acquisition) Security updates "throughout the entire lifetime" or replacement at end of support; "information describing the hardware and software components used"; documented secure configuration; a method to validate compliance A published support period, an SBOM per version, a hardening guide, test reports
6.10.2 (vulnerability handling) Monitoring vulnerability information, including "information provided by suppliers or service providers"; scans on a set schedule; a disclosure procedure Security advisories with affected and fixed versions

Recital 17 also asks buyers to consider the essential requirements of the Cyber Resilience Act when setting product security requirements, which pulls these questions toward the CRA's Annex I. ENISA's Technical Implementation Guidance (June 2025) gives "examples of evidence" per point. For 6.1.2 these include past tenders that address its elements and records from security tests before buying, and it advises buyers to favour vendors with clear end-of-life information that ship critical security fixes separately.

How does it differ from the NIS2 Directive?

NIS2 Directive (2022/2555) This Implementing Regulation (2024/2690)
Legal form Directive, required national transposition Regulation, directly applicable, no transposition
Scope All essential/important entities across NIS2's covered sectors A named subset: DNS, TLD, cloud, data centre, CDN, managed (security) service, online marketplace/search engine/social platform, and trust service providers
Content High-level obligations: scope, classification, incident-reporting deadlines 13-section technical Annex implementing Article 21(2), plus significant-incident thresholds
Guide NIS2 Directive: Scope, Deadlines and Incident Reporting This guide

A provider in scope needs both: the Directive to confirm it is covered and to learn its reporting deadlines, and this regulation for the technical bar its measures must clear. ISO/IEC 27001 helps with structure (see our ISO/IEC 27001 guide), but the regulation names it only as a basis, so certification on its own does not show compliance with each Annex point.

Worked example: what does a hosting provider ask for when buying management appliances?

Synthetic example for illustration; the companies, product and dates are invented.

A data centre service provider in scope of the regulation tenders for 200 out-of-band management appliances that will sit on its administration network (Annex point 6.8.2(f)).

  1. Write the tender from 6.1.2It asks for the support end date, an SBOM for the offered firmware version, the secure-configuration guide, and how the bidder will prove compliance.
  2. Add the 5.1.4 clausesThe draft contract requires incident notification within 24 hours, vulnerability handling with advisories, audit-report access and approval of subcontractors.
  3. Evaluate the bidsBidder A supplies an SBOM, a 7-year support date and a test report; bidder B offers none. Under 5.1.2 the buyer records why A scored higher.
  4. Register the supplier (5.2)The directory entry lists the vendor contact and the product and firmware version supplied.
  5. Monitor (6.10)The provider subscribes to the vendor's advisories and rescans the appliances on a set schedule. When an advisory lists a fixed version, it is tested before production (6.6.1) and rolled out through change management (6.4).

What are the common pitfalls?

  • Relying on secondary summaries. Section titles and point numbers in the OJ text are what an auditor checks.
  • Skipping the reasoning duty. Each "where appropriate" exception needs a written, comprehensible reason.
  • Treating ISO/IEC 27001 certification as proof. It covers the structure, not each Annex point.
  • Forgetting the supplier directory. Point 5.2 requires a maintained registry with contacts and supplied products.
  • Assuming suppliers are out of reach. The obligations flow to them through contracts under 5.1.4 and 6.1.2.

Where should an in-scope entity or supplier start?

  1. Confirm you are one of the named entity typesOther NIS2 sectors follow Article 21(2) without this Annex.
  2. Map existing controls against the 13 sectionsof the official text and record every gap or reasoned exception.
  3. Set incident thresholds in your runbooksusing Articles 3 to 14 for your entity type.
  4. Rewrite procurement templatesaround points 5.1.4 and 6.1.2, using ENISA's evidence examples.
  5. Suppliers: prepare the evidence packof support period, per-version SBOM, advisories and notification contact before the tender arrives.

For suppliers building that evidence pack, SoftWSP's firmware security service extracts an SBOM from a firmware image as CycloneDX 1.6 JSON and matches it against NVD, CISA KEV, FIRST EPSS and CISA's CSAF ICS advisories, with an AI-drafted report that cites each record for an engineer to review. For operators of on-site infrastructure, SoftWSP's passive OT security snapshot produces a device inventory and vulnerability list from a traffic recording, as evidence toward asset-management and vulnerability-handling points.

This guide summarises Commission Implementing Regulation (EU) 2024/2690 from its Official Journal text, the European Commission's description of it and ENISA's June 2025 Technical Implementation Guidance, all read 11 November 2026. It is not legal or compliance advice; the official EUR-Lex text carries the Annex's exact wording.

Put this guide to work

Frequently asked questions

What is Commission Implementing Regulation (EU) 2024/2690?

An EU implementing regulation, adopted by the European Commission on 17 October 2024, that sets out "technical and the methodological requirements" for the cybersecurity risk-management measures that [NIS2](/guides/nis2-directive-explained/) Article 21(2) requires of a specific list of digital infrastructure and digital service providers. Unlike the NIS2 Directive itself, which EU member states had to transpose into national law, an implementing regulation is directly applicable EU law — it does not need a national transposition step for the entities it covers.

Which entities does it apply to?

Per the European Commission's own description of the regulation, it applies to DNS service providers, top-level domain (TLD) name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online marketplaces, providers of online search engines, providers of social networking services platforms, and trust service providers. These correspond to the "digital infrastructure" and "digital providers" categories in NIS2's Annex I, rather than to every essential or important entity NIS2 covers — other sectors (energy, health, transport, etc.) follow Article 21(2) without this regulation's added technical detail, pending any sector-specific implementing acts of their own.

What does the Annex actually require?

The Commission's implementing regulation turns NIS2 Article 21(2)'s ten measure categories (points (a) through (j) — risk analysis and information security policies, incident handling, business continuity, supply chain security, security in acquisition/development/maintenance, policies to assess effectiveness, basic cyber hygiene and training, cryptography, human resources security/access control/asset management, and multi-factor authentication/secured communications) into a more granular Annex. Multiple independent compliance-tooling summaries (OpenKRITIS, OneClickComply, and others) consistently describe that Annex as organized into roughly 13 numbered sections — covering policy, risk management, incident handling, business continuity, supply chain security, secure acquisition/development, effectiveness assessment, cyber hygiene and training, cryptography, human resources security, access control, asset management, and physical/environmental security — containing on the order of 150 individual numbered requirements. The official EUR-Lex text is the authoritative source for the exact section count, numbering and wording before being relied on for a compliance claim.

How does it relate to the NIS2 Directive and to standards like ISO/IEC 27001?

The NIS2 Directive, Directive (EU) 2022/2555, sets the overall legal obligations — scope, essential/important entity classification, incident-reporting deadlines (see our [NIS2 Directive guide](/guides/nis2-directive-explained/)) — and had to be transposed into each member state's national law by 17 October 2024. This implementing regulation instead applies directly, without a transposition step, and only to the specific digital-infrastructure and digital-service entity types listed above; for them, it spells out in more technical detail exactly what Article 21(2)'s measures mean in practice. Secondary summaries reviewed for this guide describe the Annex's requirements as drawing on established information-security standards such as ISO/IEC 27001 and ISO/IEC 27002 for structure and terminology, without requiring formal certification against those standards — confirm this against the official text before treating ISO/IEC 27001 certification as either required or sufficient on its own.

Sources

  1. European Commission: NIS2 — Commission Implementing Regulation on critical entities and networks (official summary and download page)
  2. EUR-Lex: Commission Implementing Regulation (EU) 2024/2690 of 17 October 2024 — official legal text (CELEX 32024R2690)
  3. ENISA: NIS Directive 2 — topic page
  4. ENISA: NIS2 Technical Implementation Guidance (26 June 2025), guidance and examples of evidence for Implementing Regulation (EU) 2024/2690
  5. EUR-Lex: Directive (EU) 2022/2555 (NIS2 Directive), Articles 21 and 23
Was this guide helpful?

In this cluster

NIS2 Implementing Regulation (EU) 2024/2690, explained