Relate reviews to management-body responsibility
Article 20 of Directive (EU) 2022/2555 addresses management bodies' approval and oversight of cybersecurity risk-management measures, subject to national implementation. Article 21 requires appropriate and proportionate measures. A useful performance review therefore goes beyond a presentation of technical activity.
Management needs to understand exposure affecting the organisation's essential services, decisions requiring support and material exceptions. The reporting format should be adapted to the entity's risk and governance structure.
Build a decision-focused review pack
Include changes to the risk profile, major incidents, control assessments, supply-chain concerns, test outcomes and the status of significant remediation. Brief explanations of scope and measurement limitations help prevent false assurance.
A dashboard showing that all training sessions were delivered does not reveal whether high-risk roles retained unsafe privileges. Explain what the evidence supports and identify where further assessment is required.
Ask questions that test the evidence
Management can challenge whether critical assets are covered, whether reported improvements are independently checked, whether supplier controls have been assessed and whether recovery targets have been demonstrated in exercises.
When an indicator is positive but a recent incident showed a related failure, reconcile the contradiction before accepting the status. Require owners to explain recurring findings and any controls that cannot be verified safely.
Record approvals, exceptions and ownership
Minutes should identify significant matters reviewed, decisions made, resources approved, accepted risks and responsible owners. Preserve the basis for decisions, including which evidence was available and any uncertainty described at the meeting.
Not every operational exception requires board-level action. Establish escalation thresholds that bring material service risks and overdue corrective work to the appropriate management level.
Follow decisions through to verified outcomes
Review prior actions at the next meeting and ask for evidence of completion. A patching improvement initiative should be measured through the exposure it removed, not solely whether a project was declared complete.
Trigger additional reviews when major incidents, acquisitions, new critical suppliers or significant regulatory changes alter the risk picture. Frequency and records should reflect national law and the entity's governance needs; the Directive does not prescribe one identical meeting calendar for all organisations.
Points of clarification
Does NIS2 set one mandatory metric or review schedule for every organisation?
No single universally applicable schedule or KPI set follows from Article 21 alone. Assess applicable national and sector-specific requirements and choose measures appropriate to the entity's risks.
Is completing a control checklist proof of effectiveness?
No. Operational test results, incident outcomes and verified corrective work can provide stronger evidence than completion records alone.
What should be kept for audit and oversight?
Retain the scope, assessment method, results, limitations, decisions, named owners and verification of corrective actions.