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.
HomeArticlesBoard Responsibility for NIS2 Compliance
Management Responsibility / 2026-10-10

Board Responsibility for NIS2 Compliance

Boards of essential and important entities have a role in approving cybersecurity risk-management measures and overseeing their implementation under NIS2 Article 20. The precise management body and the application of liability provisions depend on the entity's governance structure and national law.

The board's role is a governance responsibility

Article 20 requires management bodies to approve the measures adopted to comply with Article 21 and supervise their implementation. In a company where the board constitutes the relevant management body, that means cybersecurity must enter ordinary governance rather than remain an isolated technical programme. Directors need enough information to evaluate whether material risks are recognised and treated. A board should also establish how issues travel from security leaders to decision-makers and what happens when proposed measures are not adequately funded.

Determine who holds the statutory duty

Not every organisational structure has an identical board. Dual-board companies, public entities and corporate groups may distribute formal decision rights differently. The entity should examine its governing documents and relevant national implementation before identifying the Article 20 management body. Committees can prepare recommendations, but delegating preparation or operation to a specialist does not itself replace an approval duty imposed on the designated management body. A written responsibility map should distinguish decision authority from advice and execution.

What directors should approve

An approval package should connect the business's essential services to its risk assessment and planned security measures. Article 21 covers risk analysis, incident handling, continuity, supply-chain security, vulnerability management, access control and other topics. Management should see the priorities, identified gaps, implementation dates, budget dependencies and residual risks. A clear decision record is better evidence of informed approval than a slide showing a general commitment to security without the measures being considered.

How board oversight can work in practice

Regular reporting should highlight exceptional risks, important incidents, overdue remediation, testing findings and resilience of critical services. Directors should be able to challenge optimistic status ratings and obtain independent assurance when justified. Set a sensible review cadence proportionate to risks, with faster escalation for material events. A governance dashboard is a decision aid, not an automatic legal safe harbour. Document the questions raised, commitments made and subsequent verification of progress.

Training and potential liability

Article 20(2) requires management-body members to receive cybersecurity training that enables them to understand and assess risks and security practices. Article 20(1) also contemplates liability for breaches of governance obligations, subject to relevant national arrangements. An incident alone does not establish personal liability. Board records should therefore focus on substantive oversight, training and follow-through, while any specific liability question is analysed under the applicable Member State law.

Questions on the text

Does NIS2 require management bodies to approve and oversee security measures?

Yes. Article 20 links their approval and oversight to measures under Article 21.

Can management delegate technical operations?

Technical delivery can be delegated, but applicable management-body approval and oversight duties remain.

Does NIS2 prescribe one universal board reporting template?

No. The Directive does not specify a single board dashboard or meeting cadence.

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.