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.
HomeArticlesNIS2 Enforcement Evidence and Compliance Documentation
Supervision Enforcement / 2026-10-11

NIS2 Enforcement Evidence and Compliance Documentation

When a NIS2 competent authority examines compliance, the relevant question is whether the entity implemented appropriate cybersecurity measures and fulfilled applicable reporting duties, not simply whether policies exist. Evidence should connect legal obligations, critical services, decisions and verified actions.

Build evidence around actual legal duties

Identify the entity's NIS2 classification, competent authority, national law and relevant obligations under Articles 20, 21 and 23. Map each requirement to responsible teams and records.

A generic compliance binder may miss the specific service or control under review. Keep the legal scope assessment alongside the evidence so a reviewer can understand why a duty applies.

Distinguish policy approval from operation

Retain approved security policies, management decisions, configuration evidence, incident exercises and restoration results. A written policy states intent, while test results and operational logs can demonstrate implementation.

Record the period and systems covered by a control test. Avoid suggesting a sample of one environment proves compliance across every service or subsidiary.

Keep incident decisions traceable

For suspected significant incidents, record the timeline, service impact, facts known, classification decisions and notifications made or reasons for not notifying. Preserve updates when an initial assessment changes.

The NIS2 reporting regime has distinct notification stages and conditions. An internal incident ticket by itself is not necessarily proof that Article 23 requirements were met.

Document remediation and outstanding exceptions

Track vulnerabilities, supervisory findings and corrective actions with owners, deadlines, residual risks and verification. Distinguish a proposed fix, a deployed change and a confirmed resolved finding.

When suppliers are involved, retain the evidence of requests, responses and the entity's own risk decision, rather than assuming contract terms demonstrate implementation.

Respond to evidence requests carefully

Authenticate supervisory requests, establish the legal scope and preserve records. Coordinate legal and security teams to provide accurate responsive information while protecting sensitive technical detail through lawful procedures.

Never invent missing test results or backdate approval. State limitations explicitly and identify corrective measures where appropriate.

Review record quality and retention

Use consistent version control, access restrictions, indexing and review triggers. Retain material in accordance with applicable national law and other relevant obligations rather than imposing an invented universal NIS2 retention period.

The supervisory model differs between essential entities under Article 32 and important entities under Article 33. Check the authority's lawful powers and procedural requirements.

Questions on the text

Does an incident automatically prove an NIS2 infringement?

No. An infringement requires assessment of the applicable legal duties and relevant facts.

Is a documented policy sufficient evidence?

Not on its own. Implemented controls, appropriate tests and risk decisions provide important additional evidence.

More from the Desk

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.