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.
HomeArticlesHow to Use ENISA's NIS2 Evidence Examples
Implementing Regulation 2024 2690 / 2026-10-11

How to Use ENISA's NIS2 Evidence Examples

ENISA's technical implementation guidance includes examples of evidence that can help providers demonstrate how they address Regulation (EU) 2024/2690. These examples are practical aids, not an exhaustive mandatory list or automatic proof of compliance. Evidence must reflect the control as operated by the regulated entity.

Connect evidence to a specific requirement

Start with the numbered requirement in the regulation's Annex and describe the control implemented to satisfy it. Then examine ENISA's corresponding evidence examples. Policies, inventories, logs or meeting records only matter when they support the particular requirement under review. A large folder of security documents without this traceability can obscure important gaps.

Separate policy evidence from operational evidence

An approved risk policy shows governance intent; it does not establish that vulnerabilities were remediated or backups successfully restored. A provider may need both design evidence and records of actual operation. Examples include authorised access reviews, incident exercise outcomes, supplier assessments and change approvals. Assess the freshness, completeness and authenticity of the record before linking it to a control.

Adapt examples to the entity's services

A DNS provider and a cloud platform may use different systems and procedures to implement the same high-level control. Choose evidence that fits the service, risk and technologies involved, rather than fabricating artefacts to resemble a guidance example. Document the connection between each artefact, its owner, the covered service and the reporting period. Preserve confidential customer and security data appropriately.

Handle gaps and exceptions transparently

Where a measure is incomplete, record what remains, its risk, the interim safeguard and who is accountable for remediation. If a qualified Annex requirement is not applied, document the rationale required by the regulation instead of presenting missing evidence as compliance. An example in guidance is not itself an exemption route. Review exceptions after infrastructure or threat changes.

Prepare a compact assurance trail

Maintain an evidence register containing the Annex citation, control description, example reference, actual evidence, date, responsible owner and test outcome. Verify links and versions before an internal audit or regulator request. Keep management informed of material weaknesses and unresolved corrective actions. The goal is verifiable performance, not maximum document volume.

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.