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.
HomeArticlesWhat NIS2 Requires From Management Bodies
Management Responsibility / 2026-10-10

What NIS2 Requires From Management Bodies

Management bodies of essential and important entities must approve cybersecurity risk-management measures intended to meet Article 21 and oversee their implementation under Article 20(1). Article 20(2) requires management-body training. National law governs how those requirements operate in practice and the applicable liability rules.

Approval of cybersecurity measures

Article 20(1) requires approval of the measures the entity takes to comply with Article 21. The subject is broader than purchasing security tools. Article 21 includes policies for risk analysis and information-system security, incident handling, business continuity, supply-chain security, vulnerability management, training, cryptography and access controls. Management should receive a concise explanation of material risks, proposed measures, limitations and resource needs before giving approval. A recorded decision can demonstrate which version of the programme was considered.

Oversight of implementation

The same provision obliges management bodies to oversee implementation. Meaningful oversight requires information on whether controls are deployed, tested and improved. A dashboard might include material risks, actions overdue, major incident trends, recovery readiness and critical supplier findings, but no single metric establishes compliance. Leaders should ask for evidence, investigate exceptions and ensure responsible owners have the authority and resources to remediate serious weaknesses. Governance reports should distinguish accepted risk from measures still being implemented.

Training that supports decisions

Article 20(2) requires management-body members to follow training so they can identify risks and assess the effect of cybersecurity practices on the entity's services. An introductory awareness presentation may be useful, but training should relate to the decisions the management body must make. Topics can include significant-incident notification, ransomware consequences, dependency on suppliers and interpreting control-assurance reports. Retain attendance and content records, and refresh training when threats or leadership responsibilities change.

Understanding potential liability

Article 20 recognises that management bodies can be held liable for infringements of their approval and oversight obligations. It does not create a simple EU-wide rule that every director receives a personal fine whenever an incident occurs. Member State law and the organisation's legal form are critical, and the Directive preserves national rules for public bodies and officials. A board should obtain jurisdiction-specific advice instead of relying on unqualified statements about criminal or financial exposure.

An actionable implementation routine

Assign a governance owner to collect the Article 21 control programme, prepare regular decision papers and maintain an action tracker. Record approvals, conditions, dissenting questions and agreed follow-up. Link board reporting to operational risk owners and technical assurance so directors can verify progress rather than repeatedly receiving broad assurances. Treat cybersecurity governance as part of ordinary service and continuity management, with additional meetings when a significant event changes the risk position.

Questions on the text

Is board approval a one-time requirement?

Article 20 also requires ongoing oversight, so changes and implementation progress must be reviewed.

Must every board member receive cybersecurity training?

Article 20(2) requires management-body members to follow training, implemented through national law.

What should directors ask the security team?

They should seek understandable evidence about significant risks, proposed measures, implementation gaps and operational impact.

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.