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.
HomeArticlesENISA Technical Implementation Guidance Explained
Implementing Regulation 2024 2690 / 2026-10-11

ENISA Technical Implementation Guidance Explained

ENISA's technical implementation guidance helps specified digital and ICT providers interpret the technical and methodological requirements in Commission Implementing Regulation (EU) 2024/2690. It offers practical advice and examples, but the regulation, rather than the guidance, creates the binding requirements.

Understand the guidance's purpose

ENISA published technical implementation guidance to support entities covered by Regulation 2024/2690. Its structure follows the regulation's Annex, explaining controls and offering advice on implementation and evidence. The document is valuable when converting broad policy requirements into actions, but it must be read alongside the actual legal text. A recommendation in guidance should not be presented as an additional binding obligation merely because ENISA suggests it.

Check which entities can use it

The implementing regulation concerns the named provider groups, including DNS, TLD registries, cloud and data centre services, CDNs, managed and managed security services, specified online platforms and trust service providers. ENISA's supporting material is designed for this context. Organisations in other NIS2 sectors can learn from the examples but should not assume that all provisions automatically apply to their own sector.

Read each guidance topic against the Annex

Begin with the precise Annex requirement. Note the corresponding guidance explanation, examples and possible evidence sources. Assess whether the suggested implementation fits the organisation's size, exposure, services and technical architecture. Where qualified requirements allow tailoring, document the reasons for the approach selected. Preserve distinctions between mandatory text, interpretative advice and internal best practice.

Use examples without confusing them with compliance proof

An example of a control or record can help define what to test, but copying a sample document does not demonstrate that a control is operating. An entity should produce service-specific evidence, such as access reviews, vulnerability management records, recovery test results or incident-response exercises. Technical and management owners should confirm that material deficiencies lead to tracked remediation.

Maintain a traceable implementation register

Map each Annex provision to its legal citation, relevant ENISA explanation, operating control, accountable owner and evidence location. Note deviations from examples and the risk rationale. Review the mapping after new ENISA guidance versions, architectural changes or enforcement clarification. This maintains an auditable distinction between regulation and supporting guidance.

Points of clarification

Does ENISA guidance create additional legally binding duties?

No. The regulation is binding; ENISA guidance helps interpret and implement it.

Does ISO 27001 certification automatically establish compliance?

No. Legal scope, provider-specific obligations and actual controls need separate assessment.

How should implementation evidence be organised?

Link every applicable Annex requirement to its control, owner, dated operational evidence and outstanding gaps.

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.