Why approval is only the starting point
Article 20 joins approval of cybersecurity risk-management measures with supervision of their implementation. A security plan that a management body endorsed last year may now be outdated or only partly applied. Oversight helps determine whether the entity can actually prevent, detect, respond to and recover from cyber incidents affecting its services. It also creates a route for escalating blocked projects, weak controls and decisions that exceed the authority of security teams.
Choose evidence that reflects actual risk
Management reports should explain the security and operational consequences of important findings. Useful examples include the age of critical vulnerabilities, restoration-test results, incidents and near misses, unresolved third-party weaknesses and progress on access control improvements. Metrics need context: a low incident count can reflect limited detection rather than strong protection. Require owners to explain changes, limitations and corrective action instead of presenting unqualified green status indicators.
Set responsibilities and escalation routes
Agree who prepares assurance, who validates data, who owns remediation and what constitutes material escalation. A board may rely on the CISO, risk committee and internal audit for different perspectives, but should understand their respective roles and independence. Delays affecting essential services or the entity's ability to meet reporting duties deserve timely escalation. Document how management decisions are communicated back to technical and operational teams.
Review the wider Article 21 programme
The oversight agenda should cover more than vulnerability scanning or cyber awareness. Article 21 includes incident handling, business continuity, disaster recovery, supply-chain security, security in system acquisition and development, effectiveness assessment, training, cryptography, human resources security and access management. The review can rotate through these subjects while retaining a stable view of high-priority risks. Verify that tests produce learning and tracked improvements.
Produce an auditable governance trail
Keep reporting packs, meeting minutes, questions raised, risk decisions, action owners and subsequent evidence of closure. Record exceptions and the reasons for accepting residual risks. Refresh the oversight approach following a major incident, material organisational change or new national guidance. Article 20 does not prescribe one universal board-meeting frequency or dashboard design; each organisation must construct a credible process proportionate to its circumstances and applicable implementing 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.