An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesHow a NIS2 Compliance Dashboard Could Work: Data, Metrics and Workflows
Readiness Templates Software Automation / 2026-10-11

How a NIS2 Compliance Dashboard Could Work: Data, Metrics and Workflows

A useful NIS2 compliance dashboard would connect covered services and entities to legal obligations, operational controls, evidence, significant incidents and management decisions. It should show uncertainty, overdue corrective actions and control effectiveness instead of suggesting that a percentage score proves compliance.

Design around the entity and its regulated services

Start with each legal entity, the services it provides, jurisdiction, preliminary classification and documented source of the legal assessment. Associate critical systems, assets and suppliers with those services.

This structure prevents a group-wide score from concealing a material gap in a particular operation. It also allows users to review differing national requirements without falsely assuming a single EU administrative process.

Separate obligation, implementation and verification status

Map applicable Article 21 measure areas to identified controls, accountable owners and risk decisions. Store distinct states for not assessed, planned, implemented, verified and ineffective, with dates and evidence references.

A green tile should mean something a reviewer can reproduce. If evidence is missing, stale or outside the assessed service, the dashboard should display that limitation rather than infer successful implementation.

Create incident and remediation views

For incident workflows, capture detection, assessment and awareness timestamps, reporting recipients, staged notification decisions and submission evidence where applicable under Article 23 and national law.

Make overdue critical actions and unresolved incident-significance decisions visible to authorised owners. Test escalation alerts, including their behaviour when the platform or primary communications channel is unavailable.

Give management a decision-ready overview

Management reporting should highlight material risk to services, significant gaps, recovery-test outcomes, supplier dependencies, resource decisions and accountable follow-up. Article 20 provides an important governance context for such oversight.

Offer drill-down from each summary to supporting records while protecting sensitive information. A weighted readiness index can support internal trends, but should never be presented as an official regulator-issued compliance score.

Protect the dashboard and plan continuous improvement

Restrict access to confidential configurations, risks and evidence. Provide audit history, data quality checks, export capabilities, recovery arrangements and defined ownership for each imported data source.

Reassess mappings and metrics after major incidents, acquisitions, system changes or amendments to applicable law. Pilot the workflow with users from legal, security, operations and management before treating the dashboard as the authoritative record.

Questions on the text

Does NIS2 require specialised compliance software?

No. The Directive requires appropriate cybersecurity risk-management measures and associated obligations, not purchase of a specific software product.

Can a readiness score prove compliance?

No. The applicable law, operational control effectiveness and supporting evidence require assessment.

What should be reviewed before software selection?

Assess service scope, national-law mapping, security, workflow quality, evidence portability and ownership of ongoing updates.

More from the Desk

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.