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.
HomeArticlesWhat Is NIS2 Implementing Regulation 2024/2690?
Implementing Regulation 2024 2690 / 2026-10-11

What Is NIS2 Implementing Regulation 2024/2690?

Regulation (EU) 2024/2690 is a Commission implementing regulation that specifies technical and methodological cybersecurity risk-management measures and significant-incident criteria for named categories of NIS2 providers. It sits alongside Directive (EU) 2022/2555 and gives affected entities more detailed requirements to implement.

Its relationship to the NIS2 Directive

Article 21 of NIS2 lays out broad cybersecurity risk-management obligations. The Commission implementing regulation adds detail for the provider categories within its Article 1 rather than replacing the Directive. Article 23 of NIS2 still governs incident notifications, while the regulation clarifies significance for the named providers. An organisation needs both instruments to understand its duties: the Directive establishes the legal framework and the regulation provides sector-specific implementing detail.

The entities covered

The text explicitly names DNS providers, TLD registries, cloud, data centre and content delivery services, managed and managed security services, certain online platforms and trust service providers. Similar-sounding businesses are not automatically included. For example, buying cloud services does not make the customer a cloud computing service provider. Verify the legal definition and which entity actually delivers the service before mapping controls.

Risk controls in its Annex

The Annex develops practical expectations concerning security policies, risk management, incident handling, continuity, supply-chain protections, secure acquisition and development, effectiveness assessment, basic cyber hygiene and access management. An evidence pack should identify control ownership and show that the relevant measure is operating. A security policy alone cannot demonstrate recovery testing, supplier assessment or vulnerability handling.

Proportionate implementation and exceptions

Article 2(2) connects the required security level to exposure, the organisation's size and the likelihood and severity of incidents. Some Annex requirements use qualified wording such as where appropriate or to the extent feasible. If the entity chooses not to apply a qualified requirement, the regulation calls for comprehensible documentation of the reason. The exception rationale should connect to genuine operational conditions and be reviewed when those conditions change.

Incident significance is defined separately

Common criteria under Article 3 include specified financial, trade-secret, health and access-related impacts. Provider-specific criteria appear in Articles 5 to 14, and Article 4 addresses recurring events that meet its combined test. A security operations team should translate the applicable thresholds into a triage procedure before incidents occur, including evidence collection for service availability, user impact and financial exposure.

Points of clarification

Does what is nis2 implementing regulation 2024/2690? 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.