Define the audience and legal responsibility
Identify which management body receives the report, the reporting period and the entity or services covered. Article 20(1) concerns approval and oversight of measures taken to comply with Article 21, subject to applicable national law.
Provide enough information to support a decision without turning the board pack into an unfiltered technical log. Mark assumptions and unresolved legal-scope questions where they affect the message.
Summarise material risks and service consequences
Describe the most consequential scenarios, systems and dependencies in language that connects cybersecurity exposure to operational impacts. For each material risk, state its owner, treatment plan, residual exposure and any requested decision.
Distinguish emerging issues from matters already addressed. A coloured risk rating without an explanation of what could happen and who is responsible may create false confidence.
Report control effectiveness instead of policy counts
Group controls according to relevant Article 21 areas, including incident handling, supply-chain security, business continuity, training, access management and effectiveness assessment. Explain which safeguards were implemented, tested and found deficient.
Examples of useful evidence include restoration tests, access-review results, critical vulnerability remediation, supplier assurance gaps and unresolved findings. Present trends alongside their limitations and affected service scope.
Capture incidents, regulatory readiness and escalation
Summarise significant incidents, current response status, lessons learned and relevant notification decisions without unnecessarily exposing sensitive investigation data. Identify overdue actions and barriers requiring management intervention.
Separate confirmed regulatory obligations from proposed EU changes and country-specific requirements. Incident notification responsibilities and thresholds should be checked against the applicable national framework.
Document oversight decisions and follow-up
Reserve space for approvals, risk acceptance within authorised limits, resource allocations, assigned owners, target dates and the evidence expected before closure. Retain meeting decisions in an appropriate governance record.
Article 20(2) also addresses management-body cybersecurity training. Report its completion and relevant learning needs without implying that attendance substitutes for active oversight.
Questions on the text
Does completing the template prove NIS2 compliance?
No. Templates support assessments and decisions, while applicable national rules and operational evidence determine the relevant conclusions.
Who should review and maintain the information?
Assign accountable owners and periodic review, escalating material risks or decisions to the appropriate management body.