What the Directive does and does not say about the CISO
Articles 20 and 21 of Directive (EU) 2022/2555 describe governance and risk-management obligations but do not prescribe one universal senior job title for the person managing cybersecurity. A covered organisation may appoint a CISO, security manager or another appropriately empowered individual. What matters is whether responsibilities are clear, expertise is adequate and controls are implemented and supervised. Organisational size, services and national implementing requirements influence the practical arrangements. Avoid claiming that every essential or important entity must create an identical executive role.
Preparing risk-management measures for approval
A security leader can translate Article 21 into an organised programme covering risk analysis, incident handling, business continuity, supplier assurance, vulnerability management, secure development, training, cryptography and access control. This includes identifying the systems and services in scope, proposing suitable measures, documenting material gaps and explaining resource needs. The CISO should submit decisions in business language that enables management to understand consequences, challenge assumptions and approve an identifiable set of measures. Preparation and recommendation are not the same as the statutory management-body approval required by Article 20.
Coordinating implementation and accountability
After approval, a CISO often coordinates delivery across infrastructure, development, legal, procurement, operations and human resources. Responsibilities should be assigned to the teams capable of acting, with milestones, exception procedures and evidence of effectiveness. Supplier security and continuity measures may require joint ownership rather than a security team acting alone. The CISO should surface risks that cannot be remediated within delegated authority. A clear responsibility matrix distinguishes the person who recommends action, the executive who funds it and the operator who implements it.
Reporting to the management body
Reports should identify threats to important services, significant incidents, overdue remediation, recovery-test results and dependencies on critical suppliers. Risk ratings need enough context to support informed decisions. A dashboard can summarise trends, but should not conceal uncertainties or major unresolved findings. Article 20 requires management bodies to oversee implementation, so their questions and decisions should inform subsequent security work. The CISO should have a credible escalation route when a significant weakness or incident cannot wait until the next scheduled governance meeting.
Maintaining independence and organisational resilience
Where possible, arrange reporting lines that allow security concerns to reach leadership without being filtered solely by the operational team being assessed. Document conflicts, delegated authorities, deputies, succession arrangements and access to specialist assurance. Support management-body training with practical scenarios and lessons from incidents. Revisit the CISO role after organisational changes and ensure national law is considered. A named leader improves coordination only when the role has the mandate, information and resources needed to discharge it.
Questions on the text
Does NIS2 require every company to employ a CISO?
The Directive does not universally mandate that specific job title; applicable national and sector-specific rules should also be checked.
Can the CISO replace the management body's approval responsibility?
No. Article 20 places approval and oversight obligations on the management body.
What should a CISO report to the board?
Material service risks, control gaps, incident trends, resilience, supplier exposure and decisions requiring management attention.