NIS2 Reporting Obligations

NIS2 introduces strict reporting deadlines for significant security incidents — initial report within 24 hours, final report within one month.

The reporting obligations under NIS2 Art. 23 are one of the sharpest aspects of the directive: significant security incidents must be reported to the competent authority within 24 hours — with clear follow-up deadlines and threatened fines for violations.

The three reporting deadlines at a glance

NIS2 Art. 23 defines a three-stage reporting system: (1) early warning within 24 hours — first notification of the competent authority about a significant incident. (2) notification within 72 hours — full initial report with incident classification, first assessment of severity and possible cross-border impacts. (3) final report within one month — complete description, root cause analysis, measures taken and prevention measures.

24 hours for the initial report

The 24-hour deadline for the NIS2 early warning is extremely short. Organisations need ready-made incident response processes and reporting templates — before an incident happens.

What is a significant security incident?

An incident is significant if it: (a) has caused or may cause serious operational disruption or financial loss, or (b) has affected or may affect other natural or legal persons by causing considerable material or non-material damage. Examples: ransomware attacks, DDoS attacks on critical services, data breaches with sensitive data, outages of critical systems beyond a threshold.

Prepare incident response

360TPRM detects security incidents at suppliers immediately — delivering the data basis for NIS2-compliant reporting.

FAQ

Who do you report to in Germany?+

The Federal Office for Information Security (BSI). Sectors under BaFin supervision also report to BaFin. There's a central reporting portal.

What happens if you don't report?+

Fines of up to €10 million or 2% of global annual turnover. On top of that, personal liability for management if negligence is demonstrated.

Prepare incident response

See in a 45-minute demo how 360TPRM specifically meets your requirements.

Request free demo →