NIS2 KPI Dashboard

Part of the NIS2 Evidence Pack. Audience: an operator’s compliance officer tracking control effectiveness between audits.

The NIS2 KPI dashboard measures effectiveness evidence across the thirteen thematic areas, so an operator can spot a control whose evidence is going stale before an auditor does. It is an operator evidence and review aid; it does not replace the customer’s management review or auditor judgment.

Claim boundary: operator-support.

Source Docs

• NIS2 KPI Telemetry Schema v1
• NIS2 Effectiveness Report Contract v1
• NIS2 KPI default targets
• NIS2 KPI catalog
• Assurance Evidence Export v1

Ownership And Overrides

Stella Ops ships conservative default KPI targets so operators can start with a known profile. Tenants may override targets to match their risk appetite, sector, or auditor direction.

Areas that depend on tenant evidence, workforce process, or physical controls must remain explicit tenant-supplied evidence areas. Stella Ops may store opaque evidence references and review status, but it must not become the system of record for those customer processes.

Export Posture

Monthly effectiveness exports should be deterministic and evidence-pointer first. The export should preserve the dashboard state, hashes, source refs, and blockers that existed at export time.

The ExportCenter Assurance registry exposes this export as nis2.effectiveness-report, with compatibility through stella export nis2-effectiveness and POST /v1/exports/assurance/profiles/nis2.effectiveness-report/runs. Readiness remains source-data aware: the monthly dashboard source report must be supplied when starting the export, and missing Policy/control-register refs remain explicit blockers in the resulting bundle rather than fabricated evidence.

Implementation Status (2026-07-14)

Verified against src/. The live per-area KPI telemetry is shipped: Nis2AreaMetricsService emits 31 metrics across the 13 areas (src/Telemetry/StellaOps.Telemetry.Core/.../Nis2AreaMetricsService.cs), read at GET /api/telemetry/nis2/effectiveness (src/Platform/StellaOps.Platform.WebService/Endpoints/Nis2TelemetryEndpoints.cs). The signed monthly effectiveness export materializes through the CLI (stella export nis2-effectiveness) and the ExportCenter Assurance run endpoint (POST /v1/exports/assurance/profiles/nis2.effectiveness-report/runs). Export readiness remains source-data aware and is owned by ExportCenter; the Platform telemetry response does not report export availability as a blocker.

Change Log