Skip to main content
NIS-2 — Network and Information Security Directive

Hit the 24-hour early warning window — from the incident your team is already triaging.

TENSOR embeds NIS-2 significant-incident classification and the 24h/72h/1mo reporting cascade into your service desk. No bolt-on, no spreadsheet timer.

What the regulation requires → what TENSOR produces

The clock starts on the incident your team already triaged.

NIS-2
Art. 23 — Significant-incident classification

Incidents are assessed against NIS-2 significance criteria as they are triaged. Classification fields are built into the incident form — no separate workflow.

NIS-2
Art. 23(4) — 24h / 72h / 1mo reporting cascade

Early warning within 24 hours, incident notification within 72 hours, final report within one month. Cascade timers start when the incident meets the significance threshold.

NIS-2
Art. 23 — War room and coordinated response

Major-incident war room with timeline, stakeholder updates, and auto-drafted post-incident review. Everything the CSIRT or competent authority needs is captured in one place — and external updates are segregated from incident response, so the responder isn't the one issuing public statements.

NIS-2
Art. 23(1) — Status page for affected services

Tenant status pages keep internal and (optionally) external stakeholders informed during significant incidents, with a full audit trail of updates.

Common questions

NIS-2 FAQ

Informational only — not legal advice. Consult qualified counsel for regulatory obligations specific to your organization.

See the NIS-2 cascade on a live incident.

30 minutes. We'll walk through significant-incident classification and reporting timelines.