Start with decisions, not a wall of metrics
Article 20 calls for management-body approval and oversight of cybersecurity measures. A useful dashboard therefore begins with decisions directors must make: whether a risk is tolerable, whether remediation requires resources, and whether a control programme is progressing. Group information by the organisation's important services and their operational dependencies rather than by technology vendor or security tool. The executive summary should state what changed since the previous review and where management intervention is required.
Choose indicators with operational meaning
Indicators can cover high-risk vulnerabilities, privileged access, recovery testing, incidents, supplier assurance and delayed security actions. Use denominators and context to prevent a misleading impression: 90 percent of controls completed says little if a remaining gap threatens a critical service. Explain thresholds, data sources, confidence levels and material exclusions. Distinguish an absence of incidents from evidence that monitoring and detection are functioning effectively.
Connect findings to Article 21 measures
A dashboard should reflect the breadth of Article 21, not just patching or phishing statistics. Include incident handling, business continuity, security in acquisition and development, supply-chain risk, workforce access and effectiveness testing as appropriate to the entity. Show which controls have been approved, implemented, tested or found deficient. This allows management to oversee the measures it previously authorised and challenge weak assurances.
Make ownership and escalation explicit
For each significant gap, identify the operational owner, anticipated resolution date, interim mitigation and decision required. Risks that could affect service continuity or regulatory notification should have clear escalation routes outside the ordinary board calendar. A structured status report helps leadership distinguish acceptable delays from unaddressed exposure. Board minutes should reflect the questions raised and actions agreed, not simply that a dashboard was presented.
Review the dashboard as the organisation changes
Metrics and thresholds should evolve after incidents, major acquisitions, service expansion or shifts in threat exposure. A dashboard that was relevant to a smaller organisation may omit critical dependencies after growth. Have security and risk owners periodically validate the underlying data and discuss whether the presentation is driving useful decisions. Keep versions of dashboard packs and meeting decisions as evidence of continuing oversight.
Questions on the text
Does NIS2 require a particular dashboard template?
No. Articles 20 and 21 establish governance and risk-management duties, not a single mandatory board dashboard.
Which metrics matter most?
Those that show material service risk, control effectiveness, resilience gaps and decisions management needs to make.
Should dashboards replace board discussion?
No. Dashboards support challenge and decisions; they cannot replace informed oversight.