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.
HomeArticlesNIS2 Cybersecurity Metrics and KPIs
Security Testing Audit / 2026-10-09

NIS2 Cybersecurity Metrics and KPIs

NIS2 does not prescribe one universal dashboard of cybersecurity KPIs. Organisations can use a small, risk-based set of metrics to assess whether Article 21 security measures work, make gaps visible to management, and document corrective action.

Select measures that match material cyber risks

Begin with the services in scope, then trace each important risk to a safeguard and an intended outcome. A vulnerability management metric should relate to exposure of critical systems rather than the total number of tickets closed. Define the population being measured, responsible owner, review period and data source.

Article 21(2)(f) requires policies and procedures to assess the effectiveness of risk-management measures. Metrics can support this assessment but do not replace testing or establish compliance by themselves.

Differentiate coverage, speed and effectiveness

Coverage measures reveal whether assets, accounts or suppliers are included in an assurance activity. Timeliness measures track completion against an internal objective. Effectiveness measures investigate whether the control actually reduced exposure or enabled a response.

For example, a high percentage of scanned hosts is useful only when the inventory is complete and meaningful findings are triaged. Pair scan coverage with critical exposure age, verified remediation and the number of unavailable systems.

Define indicators precisely

Possible indicators include the proportion of privileged accounts reviewed, the number of successful restoration tests against documented recovery objectives, time to contain significant incidents, and material security findings overdue for resolution. They are illustrative internal indicators, not figures mandated uniformly by NIS2.

Document the numerator, denominator, exceptions, calculation schedule and interpretation. If a metric definition changes, annotate the historical series so apparent improvements do not arise solely from reclassification.

Make uncertainty and exceptions visible

Strong dashboards show gaps in evidence rather than silently excluding them. An unmonitored cloud tenant or legacy system creates uncertainty that should be reported alongside measured performance. Segment results by critical service where aggregate averages would conceal serious weaknesses.

Do not automatically mark a measure effective because its indicator turns green. Compare reported values with incident lessons, independent review findings and direct control tests.

Connect reporting to corrective decisions

Set thresholds according to risk appetite, operational capability and any applicable legal or contractual requirements. Assign an owner and escalation process when measures cross a threshold, and record decisions about remediation or risk acceptance.

Management reports should explain what deteriorated, why it matters to service resilience, what action is proposed and how success will be verified. Check national requirements and any sector-specific measures before presenting a KPI target as legally required.

Points of clarification

Does NIS2 set one mandatory metric or review schedule for every organisation?

No single universally applicable schedule or KPI set follows from Article 21 alone. Assess applicable national and sector-specific requirements and choose measures appropriate to the entity's risks.

Is completing a control checklist proof of effectiveness?

No. Operational test results, incident outcomes and verified corrective work can provide stronger evidence than completion records alone.

What should be kept for audit and oversight?

Retain the scope, assessment method, results, limitations, decisions, named owners and verification of corrective actions.

Further entries on this subject

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.