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.
HomeArticlesDocumenting Management Approval of NIS2 Controls
Management Responsibility / 2026-10-10

Documenting Management Approval of NIS2 Controls

To evidence the approval required by NIS2 Article 20, a management body should retain a clear record of the cybersecurity risk-management measures considered, the decision taken, outstanding gaps and implementation responsibilities. Approval records should be connected to ongoing oversight, not treated as a substitute for implementing Article 21 controls.

Identify exactly what was approved

A broad minute stating that the board supports cybersecurity may not establish which measures the management body considered. Use a controlled document reference identifying the relevant entity, approved policies, risk assessment, proposed controls and version date. Explain how the measures relate to Article 21 and the organisation's important services. Record the approval decision and any qualifications, so later reviewers can reconstruct the content and scope of the decision.

Present the underlying risk and implementation context

Approval papers should identify material risks, intended mitigation, remaining gaps, responsible owners, schedules and funding. Management needs enough information to challenge unsupported assumptions about supplier assurance, recovery capability or security effectiveness. A concise main paper can link to detailed technical annexes without forcing directors to review every operational setting. Record which supporting documents were available at the meeting.

Capture conditions, exceptions and accountability

If approval depends on additional funding, a planned remediation or a risk exception, record those conditions with accountable owners and target dates. Minutes should note significant questions raised and any decisions deferred for missing evidence. Do not describe a disputed or conditional measure as unqualified approval. Ensure action registers link to the decision record so management can later verify whether commitments were met.

Connect the record to ongoing oversight

Article 20 requires supervision of implementation after approval. Management reports should reference the approved measure set and describe implementation progress, effectiveness tests, incidents and deviations. When a material change is proposed, record the rationale for additional review or approval in accordance with the entity's governance process. The Directive does not prescribe that every minor technical configuration change needs a new board vote.

Retain records for regulator and internal review

Store decision papers, signed or approved minutes, document versions, attendance and action histories in a controlled repository. Preserve an audit trail showing when measures were reviewed and what follow-up occurred. National law and organisational policies may set retention or formal approval requirements, so check those before defining a single retention period. Evidence should demonstrate informed governance and effective security work, not only paperwork.

Questions on the text

Is a board signature alone enough for NIS2 compliance?

No. Management must also oversee implementation, and the measures must address the entity's Article 21 obligations.

Should approval minutes identify a specific document version?

Yes. That helps show which measures management actually reviewed and approved.

Must management reapprove every small configuration change?

The Directive does not state such a universal rule. Establish suitable material-change triggers under applicable governance rules.

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.