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 Evidence Register: Fields, Ownership and Review
Readiness Templates Software Automation / 2026-10-11

NIS2 Evidence Register: Fields, Ownership and Review

A NIS2 evidence register links an applicable obligation and cybersecurity risk to an implemented control, a responsible owner and verifiable records. It should distinguish design evidence from operating effectiveness and avoid treating document volume as proof of compliance.

Define the unit of evidence

Create one register row for each meaningful obligation-to-control relationship, with the affected service and systems identified. Reference the NIS2 Directive and the applicable national legislation rather than assuming the Directive alone explains every supervisory expectation.

Article 21(2)(f) identifies policies and procedures to assess the effectiveness of cybersecurity risk-management measures. Evidence should make it possible to review what was implemented and how its operation was assessed.

Choose fields that support traceability

Useful columns include record identifier, entity, legal source, control area, asset or service, control owner, evidence custodian, evidence type, period covered, storage reference, verification date, reviewer, finding and next review date.

Separate the review status from the compliance conclusion. For example, a backup configuration record may show that a schedule exists while a restoration test demonstrates whether recovery works.

Collect proportionate evidence from operations

Use access reviews, incident exercises, risk decisions, supplier assessments, recovery tests, change records and technical configuration reports where relevant. Ask whether each item genuinely supports the claimed safeguard.

Do not expose credentials, vulnerability details or personal information unnecessarily in a shared audit folder. Restrict access, keep original sources identifiable and apply applicable retention and confidentiality requirements.

Manage gaps and changes in the register

Record missing, expired or inconclusive evidence as an open item with an owner, due date and proposed way to verify the control. Document compensating measures and the reason for accepting residual risk when appropriate.

Review evidence after significant incidents, system migrations, new suppliers and changes to legal obligations. A static spreadsheet becomes misleading when the underlying control changes.

Make the register usable for oversight

Provide management with material findings, overdue remediation, untested high-risk controls and uncertainty rather than only a completion percentage. Permit reviewers to follow each summary back to the supporting source.

An evidence register is a coordination tool, not a regulatory certificate. The competence of the reviewer and the actual quality of safeguards remain essential.

Questions on the text

Does a completed software assessment prove NIS2 compliance?

No. Actual obligations and operating controls must be evaluated against applicable laws and evidence.

Can the platform replace management oversight?

No. Management remains responsible for oversight under the applicable legal framework.

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.