Start with the legal entity and governing body
Determine which legal entity provides the in-scope service and whether it is classified as essential or important. Identify the relevant management body under the organisation's legal form and applicable Member State law. In a corporate group, distinguish regulated subsidiaries from their parent and map shared-security services clearly. Governance designed only around a corporate brand can leave approval and reporting duties without an identifiable accountable entity. Record the relevant statutory basis and governing documents so responsibilities are not inferred from job titles alone.
Assign risk ownership and control delivery
Build a responsibility map that separates management approval, executive risk ownership, technical design, implementation and assurance. Operational teams may own identity systems, backups, software security and supplier relationships while a CISO or security lead coordinates overall cybersecurity. Article 21 calls for a wide range of proportionate risk-management measures, not a single departmental checklist. Assign named owners for material gaps and ensure they can obtain necessary resources. Escalate competing priorities or residual risks to the forum authorised to decide them.
Create a manageable reporting and decision cycle
Specify what the management body receives, how frequently it reviews progress and what prompts an extraordinary briefing. Present critical services, significant risk scenarios, incident experience, overdue measures, continuity tests and dependencies on important suppliers in a format that supports decisions. Document approval of identifiable Article 21 measures and subsequent oversight of implementation. The Directive does not require one universal governance committee model or board dashboard, so tailor the process while retaining evidence of informed decisions.
Integrate incident response and external communication
Define how operational responders assess an event, who decides whether it qualifies as significant, and who coordinates Article 23 notifications to the relevant CSIRT or competent authority under applicable rules. Connect cybersecurity leadership, legal advisers, communications and service owners before an incident occurs. The management body needs rapid access to material developments but should not replace the response team in every technical decision. Test escalation, deputies and authority contacts, especially when shared infrastructure affects several legal entities.
Check effectiveness and preserve records
Governance is credible when actions can be traced from risk identification through approval, implementation, testing and remediation. Retain meeting packs, decision records, training evidence, internal assurance results and exception logs. Review arrangements after major incidents, business acquisitions, changes in leadership or new national guidance. Management should ask not only whether measures exist but whether they work in practice. Periodic independent challenge can identify gaps missed by teams responsible for implementation.
Questions on the text
Must NIS2 entities establish a particular committee structure?
No. The Directive sets management approval and oversight duties, while the governance model should reflect the entity and applicable law.
Who owns cybersecurity controls in a governance model?
Named operational owners deliver controls, security leadership coordinates, and the management body retains its statutory approval and oversight responsibilities.
How does incident response fit into governance?
Define operational response, significance assessment, escalation and notification decision-makers before an incident occurs.