What must be put forward for approval
Security specialists should prepare a package that names the relevant entity, the systems and services in scope, principal risk scenarios, proposed controls and important dependencies. The package should show how measures address Article 21, including risk policies, incident handling, continuity, supply-chain security and access controls. Management cannot sensibly approve a programme without knowing what is included. A short board paper may be adequate if it links to detailed policies and a controlled version of the underlying measures.
Separate approval from implementation
Approval confirms a management-level decision about the measures, while implementation concerns carrying those measures into operation. An approved plan that remains unexecuted may leave substantial exposure. Managers should therefore ask which controls are already effective, which are scheduled and where exceptions remain. The CISO or relevant operational teams can own delivery, but management-body oversight under Article 20 continues after the approval meeting. Make accountability for both decisions and execution explicit.
Evidence supporting an informed decision
Decision-makers benefit from a risk assessment, a control-gap analysis, a proposed remediation timetable, financial implications and an explanation of remaining risk. A security score without a defined methodology is not enough. Management should have an opportunity to challenge assumptions about suppliers, incident detection and recovery capabilities. Meeting minutes ought to capture approval of a specific document version, conditions attached, deferred items, decisions on resources and assigned follow-up.
Handling exceptions and changes
Organisations regularly encounter controls that cannot be introduced immediately or must be adapted to their environment. Record each material exception, its risk consequences, interim safeguards, responsible owner and target date. Management should review changes to the risk landscape or operating model that materially alter the approved programme. Requiring a full new vote after every minor technical adjustment is not prescribed by the Directive; the governance process should instead define which changes are material enough for renewed management consideration.
Keeping national implementation in view
NIS2 is a directive implemented through Member State law. The organisation should confirm which body must approve measures under the applicable domestic framework and whether relevant sector-specific EU provisions alter obligations. Retain meeting records, programme versions and reports demonstrating the transition from approval to implementation. Compliance is better supported by evidence of working controls and oversight than by a formal signature alone.
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.