SDG data protection blog

Laws & regulationIT security

NIS2 Reporting Obligations: Deadlines, Content and Reporting Channel

29 September 2026 by Sebastian Baier · Reading time approx. 8 minutes

Under Section 32 BSIG (the BSI Act), particularly important and important entities must report significant security incidents to the BSI (Federal Office for Information Security): an early warning within 24 hours of becoming aware, an incident notification within 72 hours and a final report no later than one month after that. Reports are submitted via the BSI portal to the joint reporting office of the BSI and the BBK (Federal Office of Civil Protection and Disaster Assistance). The BSI emphasises the principle of "speed before completeness": it is better to report early with incomplete information and add to it later.

This article explains when an incident is significant, what belongs in which report and how to set up a reporting process that also works at weekends. You will find an overview of all NIS2 obligations on the page NIS2 consulting.

When is a security incident significant?

The BSIG distinguishes three levels (Section 2 BSIG):

Term Definition (paraphrased) Reportable?
Near miss (No. 1) an event that could have compromised availability, integrity or confidentiality, but was prevented or did not materialise no, voluntary reporting possible
Security incident (No. 40) an event that compromises the availability, integrity or confidentiality of data or services no, but must be handled internally
Significant security incident (No. 11) a security incident that has caused or is capable of causing severe operational disruption or financial loss, or has affected or is capable of affecting other persons by causing considerable material or non-material damage yes

The word "capable" is important: an incident whose consequences have not yet occurred but are threatening can also be significant.

More specific criteria are provided by Implementing Regulation (EU) 2024/2690. For digital providers such as cloud services, data centres, DNS providers, managed (security) service providers, online marketplaces and trust service providers, its thresholds apply directly. For all other sectors, the BSI assumes that an incident is significant if at least one of the criteria in Art. 3 (1) of this regulation is met. An incident that disrupts or impairs the provision of critical services is always significant.

The deadlines under Section 32 BSIG

Stage Deadline
Early warning without undue delay, no later than 24 hours after becoming aware
Incident notification without undue delay, no later than 72 hours after becoming aware
Intermediate report at the request of the BSI
Final report no later than one month after the incident notification; if the incident is ongoing, a progress report instead, and the final report once handling is complete

The deadlines are maximum deadlines and should not be used up in full. In the BSI's view, "becoming aware" means that an employee learns of the incident during working hours.

What belongs in which report

Early warning (24 hours)

  • Classification (significant security incident, security incident or near miss) and reason
  • Preliminary description of the disruption, impact, expected duration and suspected cause
  • Times of occurrence and discovery
  • Sectors affected and, where applicable, critical facilities
  • Suspicion of unlawful or malicious acts and possible cross-border impact
  • Measures taken and whether the incident is under control
  • Contact details of the person reporting

Incident notification (72 hours)

  • Update of the information from the early warning
  • More detailed information on the cause
  • Information on criminal prosecution and cooperation with authorities
  • Measures taken and planned for containment
  • Severity and impact
  • Indicators of compromise (IOCs), where applicable

Final report (no later than one month)

  • Detailed description including severity and impact
  • Type of threat or underlying cause
  • Mitigation measures taken and ongoing
  • Cross-border impact

Reporting channel: BSI portal and reporting office

  • After registration: Reports go via the BSI portal to the joint reporting office of the BSI and the BBK.
  • Not yet registered: Entities that suffer a significant incident before registering report via an online form in the BSI's reporting and information portal. They should then register without delay, see NIS2 registration with the BSI.
  • Operators of critical facilities and federal authorities temporarily continue to use their existing reporting channels.

Practical rules from the BSI

  • Speed before completeness: report early, add information later.
  • No withdrawal: A submitted report cannot be withdrawn, but it can be corrected or supplemented at any time with a follow-up report.
  • Who may report: Any employee can report. Several people can be authorised, including service providers. Responsibility for the report and its content, however, remains with the entity.
  • Acknowledgement of receipt: The BSI usually confirms receipt immediately, at the latest within 24 hours. If you do not receive a confirmation, you should follow up.
  • Informing customers: The BSI can order entities to inform the recipients of their services about significant security incidents without undue delay.
  • Availability for warnings: Entities should be able to receive and escalate warnings from the BSI outside business hours too.

NIS2, KRITIS, CRA and GDPR: when several reporting obligations apply

Obligation Trigger Recipient First deadline
NIS2 (Section 32 BSIG) significant security incident in operations joint reporting office BSI/BBK 24 hours
KRITIS-Dachgesetz (German critical infrastructure umbrella act, Section 18) incident at a critical facility (physical resilience) BBK via the joint reporting office 24 hours
Cyber Resilience Act (Art. 14) actively exploited vulnerability or severe incident in the product ENISA and CSIRT via the single reporting platform 24 hours
GDPR (Art. 33) personal data breach data protection supervisory authority 72 hours

A ransomware attack, for example, can be both a significant security incident under the BSIG and a personal data breach under the GDPR. A joint incident process should therefore check at the outset which obligations apply. More on this in the articles CRA reporting obligations and KRITIS-Dachgesetz.

How to set up the reporting process

  1. Define roles Who assesses, who decides on reporting, who reports? Each with a deputy.
  2. Set up access Several authorised people in the BSI portal, and a commissioned service provider if applicable.
  3. Define significance criteria based on Section 2 No. 11 BSIG and Art. 3 of Implementing Regulation (EU) 2024/2690, with examples from your company.
  4. Ensure availability Escalation paths outside business hours, also for warnings from the BSI.
  5. Prepare templates for the early warning, incident notification and final report, as well as for informing customers and reporting data breaches.
  6. Link other reporting obligations GDPR, KRITIS-Dachgesetz where applicable, CRA and contractual obligations.
  7. Practise Run through the process using a realistic scenario, including with management.
  8. Document and review Follow up on every report and every incident.

The reporting process is part of incident handling under Section 30 (2) No. 2 BSIG. In an ISMS based on ISO 27001 it belongs to incident management. The NIS2 checklist gives an overview of all measures.

How SDG supports you

  • Setting up the reporting process with roles, significance criteria, templates and escalation paths
  • Linking it with data breach reporting, on request together with our work as your external data protection officer
  • Practising the process using a realistic scenario
  • External information security officer as your contact in the event of incidents: external information security officer
  • Training for employees and management: training

Frequently asked questions about NIS2 reporting obligations

What is a significant security incident under NIS2?

Under Section 2 No. 11 BSIG, a security incident that has caused or is capable of causing severe operational disruption or financial loss for the entity, or has affected or is capable of affecting other persons by causing considerable material or non-material damage. Implementing Regulation (EU) 2024/2690 contains more specific criteria.

Which deadlines apply to NIS2 reporting?

Early warning without undue delay, no later than 24 hours after becoming aware; incident notification no later than 72 hours; final report no later than one month after the incident notification. If the incident is ongoing, a progress report comes first.

Where do I report a NIS2 security incident?

Via the BSI portal to the joint reporting office of the BSI and the BBK. Anyone not yet registered reports via an online form in the BSI's reporting and information portal and registers without delay.

When does the 24-hour deadline start?

From the moment you become aware of the incident. In the BSI's view, this is the case when an employee learns of it during working hours. The deadline is a maximum deadline and should not be used up in full.

Do I have to report if not all the information is available yet?

Yes. The BSI expressly recommends "speed before completeness". Missing or incorrect information can be supplemented or corrected at any time with a follow-up report.

May a service provider report on our behalf?

Yes. Several people and also service providers can be authorised to report. Responsibility for the report and its content, however, remains with the entity.

What happens if I miss a report?

Late, incomplete or omitted reports can be punished with fines under Section 65 BSIG: up to EUR 10 million for particularly important entities and up to EUR 7 million for important entities.

Sources: Section 32 BSIG, Section 2 BSIG, BSI: NIS2 reporting obligation, Implementing Regulation (EU) 2024/2690

Note: This article provides general information and does not replace legal advice in individual cases.