What Article 20 places on leadership
NIS2 treats cybersecurity as a management responsibility rather than a topic exclusively for technical teams. Article 20(1) addresses the management bodies of essential and important entities: they approve the measures taken to meet Article 21 and oversee implementation. Article 20(2) adds training requirements for management-body members. These duties should be reflected in governance arrangements, not merely cited in a policy document. The relevant national implementing law determines the concrete mechanism and how it applies to an organisation's governance structure.
Approval means an informed decision
A management body should be able to identify the principal cyber risks to the entity's services, understand the proposed controls, and challenge significant gaps. Approval should relate to an identifiable package of risk-management measures, with responsible owners, resources and dates. Management may delegate technical design to security specialists, but a blanket statement that cybersecurity has been delegated does not demonstrate the approval required by Article 20. Records should explain what information management considered and what decisions it made.
Oversight continues after approval
Article 20 requires oversight of implementation, not simply a signature on a cybersecurity plan. Management should request evidence of progress, incident lessons, unresolved vulnerabilities, continuity capability and risks from key suppliers. Article 21 covers a broad set of measures, from risk analysis and incident handling to business continuity, supply-chain security and access controls. Leadership needs reporting that connects these subjects to the services the organisation provides, with clear thresholds for escalating overdue or ineffective measures.
Training and possible liability
Article 20(2) requires management-body members to follow training sufficient to identify risks and assess cybersecurity risk-management practices and their operational impact. The Directive also provides that members can be held liable for infringements of Article 20(1) obligations under applicable national arrangements. Liability should not be described as automatic personal punishment for every cyber incident. The application to public institutions, public servants and officials is expressly subject to national law, and national measures require jurisdiction-specific review.
Building a workable governance record
Keep the entity's scope classification, board or management terms of reference, approved control framework, security reports, meeting minutes, training records and tracked decisions together. Identify who provides specialist advice, who accepts material risks and who follows up agreed actions. Review responsibilities after leadership changes or a material incident. A useful governance record demonstrates informed approval, continuing challenge and measurable follow-through rather than a collection of unsigned templates.
Questions on the text
Does Article 20 apply to important entities?
Yes. Its governance requirements concern essential and important entities.
Can the CISO approve all measures on the board's behalf?
Specialists can prepare and manage measures, but Article 20 specifically requires management-body approval and oversight under applicable law.
Does an incident automatically make directors personally liable?
No. Liability depends on the relevant infringement and applicable national legal framework.