An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesCommission Implementing Regulation 2024/2690 and NIS2 Technical Requirements
Implementing Regulation 2024 2690 / 2026-10-11

Commission Implementing Regulation 2024/2690 and NIS2 Technical Requirements

Commission Implementing Regulation (EU) 2024/2690 sets detailed cybersecurity risk-management requirements and significant-incident criteria for specified digital infrastructure, ICT service and trust service providers covered by NIS2. Its Annex supplies technical and methodological measures; Articles 3 to 14 define incident significance conditions. It does not automatically impose its entire Annex on every entity in every NIS2 sector.

Why a separate implementing regulation exists

NIS2 Article 21(5) empowers the Commission to specify cybersecurity measures for defined digital and ICT providers, while Article 23(11) concerns significant-incident criteria. Regulation 2024/2690 was adopted on 17 October 2024 and published on 18 October. It supplies detail beyond the Directive's broader duties. Businesses should read the operative articles and Annex together because the Annex addresses implementation while Articles 3 to 14 address whether incidents meet prescribed significance criteria.

Which providers the regulation addresses

Article 1 names DNS providers, top-level domain registries, cloud computing, data centre and content delivery network providers, managed service and managed security service providers, providers of online marketplaces, online search engines and social networking service platforms, and trust service providers. Being an energy company, bank or hospital does not by itself place an entity under this implementing regulation. A group that operates a qualifying digital service should assess that provider separately from other regulated businesses.

How the Annex should be applied

The Annex specifies policies, risk assessment, incident handling, business continuity, supply-chain security, access controls and other technical and methodological expectations. Article 2(2) requires security appropriate to exposure, size and the likelihood and severity of incidents. Where a requirement permits application only where appropriate, applicable or feasible, an entity that does not apply it must document comprehensible reasoning. These qualifiers are not permission to ignore the Annex as a whole.

When incidents count as significant

Article 3 identifies common triggers, including direct financial loss exceeding the lower of EUR 500,000 or five percent of preceding-year turnover, potential exfiltration of trade secrets and certain severe safety or operational consequences. Articles 5 to 14 add provider-specific criteria, so a cloud outage and a DNS resolution disruption cannot be assessed through one generic duration rule. Article 4 also addresses repeated incidents with a shared apparent root cause.

How to prepare an implementation record

First confirm the legal entity and whether its actual services fall within Article 1. Map each applicable Annex requirement to an operational owner and existing control, record gaps, and maintain evidence of testing. Separately build incident triage criteria based on the appropriate provider category. Keep Directive obligations, implementing-regulation details and national notification channels together in the compliance register without presenting them as interchangeable sources.

Points of clarification

Does commission implementing regulation 2024/2690 and nis2 technical requirements apply to every business?

No. Confirm the exact legal entity, provider or sector category, scope rules and applicable national framework.

Can a general cybersecurity policy demonstrate full compliance?

No. The organisation also needs evidence of appropriate measures, operation, oversight and incident handling.

Where should a business verify the legal requirements?

Use the cited EUR-Lex legislation alongside current national implementing law and competent-authority guidance.

Further entries on this subject

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.