What Section 32 BSIG requires: the significant incident
Section 32 BSIG implements Article 23 of Directive (EU) 2022/2555. Essential entities (besonders wichtige Einrichtungen), important entities (wichtige Einrichtungen) and operators of critical facilities (kritische Anlagen) are subject to the reporting obligation, and only for significant incidents. Under Section 2 No. 40 BSIG, an incident is any event that compromises the availability, integrity or confidentiality of data or services. Under Section 2 No. 11 BSIG, it becomes significant if it
- has caused or can cause severe operational disruption of the services or financial loss for the entity, or
- has affected or can affect other natural or legal persons by causing considerable material or non-material damage.
Both alternatives contain "can cause". The reporting obligation therefore arises as soon as damage is threatened, not only once it has occurred. For DNS providers, cloud, data centre and CDN providers, managed service providers, online marketplaces, search engines and social networks, Implementing Regulation (EU) 2024/2690 specifies significance with thresholds, for example on outage duration and affected users. For operators of critical facilities, BSI practice treats any incident that impairs or disrupts the critical service as significant.
All three deadlines are maximum deadlines. Section 32 (1) No. 1 of the law requires "without undue delay, but no later than within 24 hours". In BSI's view, awareness means the point at which an employee learns of the incident during working hours. Calculate your specific dates with the deadline calculator:
Content of each reporting stage
Section 32 (1) BSIG sets out minimum content for each stage. BSI supplements this in its reporting form with information that has proven useful in practice.
| Stage | Deadline | Statutory minimum content (Sec. 32 (1)) | Additional information per BSI form |
|---|---|---|---|
| Early warning (No. 1) | 24 h after becoming aware | Indication of whether unlawful or malicious action is suspected and whether cross-border effects are possible | Classification, preliminary description, affected sectors, measures already taken, contact details |
| Incident notification (No. 2) | 72 h after becoming aware | Confirmation or update of the early warning, initial assessment of severity and impact, indicators of compromise (IoCs) where available | Cause, status of law enforcement and cooperation with authorities, remedial measures |
| Interim report (No. 3) | on request by BSI | relevant status updates | Progress of recovery, new findings |
| Final report (No. 4) | no later than 1 month after the notification | Detailed description incl. severity and impact, likely type of threat or root cause, remedial measures taken and ongoing, cross-border effects where applicable | Lessons learned, assessment of the effectiveness of the measures |
Under Section 32 (3), operators of critical facilities add information on the affected facility, the critical service and its impairment. For the early warning, BSI's principle applies: speed before completeness. Whatever is not known after 24 hours is submitted later.
Reporting channel: BSI portal and joint reporting office
Section 32 (1) BSIG names as recipient a joint reporting office of BSI, the German Federal Office for Information Security, and BBK, the Federal Office of Civil Protection. Technically, the report is submitted via the BSI portal, where registered entities also maintain their master data under Section 33. Access requires an ELSTER organisation certificate via "Mein Unternehmenskonto". Apply for it before the first incident; issuance takes days, not hours.
- Entities that suffer an incident before completing registration report via the online form of BSI's reporting and information portal (MIP).
- Operators of critical facilities and federal authorities use their existing reporting channels for a transitional period (as at 26 October 2026).
- BSI usually confirms receipt immediately, at the latest within 24 hours, and forwards reports to the competent federal supervisory authorities under Section 32 (5).
- Any employee may report; a commissioned service provider can also submit the report. Responsibility remains with the entity.
Under Section 32 (6) in conjunction with Section 36, BSI may offer support in handling the incident. That is not automatic, but for complex incidents it is a genuine resource.
Interim reports and progress report
Unlike under the CRA, there is no fixed interim deadline under NIS-2. Interim reports under Section 32 (1) No. 3 are only due on request by BSI, but then promptly. If the incident is still not resolved one month after the notification, a progress report replaces the final report under Section 32 (2). The final report then follows within one month of the incident being fully handled. Document internally when handling is deemed complete, otherwise this last deadline starts running unnoticed.
Informing customers under Section 35 BSIG
The report to BSI is not the only communication obligation. Section 35 (1) BSIG allows BSI to instruct entities to inform the recipients of their services without undue delay if the incident could affect service delivery. Publication on the entity's own website is sufficient. Violations of such an instruction fall into the maximum range of Section 65 BSIG.
For entities in finance, digital infrastructure, ICT service management and digital services, Section 35 (2) goes further: they must inform potentially affected customers and BSI on their own initiative about a significant cyber threat and state what countermeasures customers can take, provided the customers' interest prevails. For MSPs and cloud providers, customer communication therefore belongs in the reporting process.
Interplay with CRA and GDPR notifications
One incident can trigger three reporting obligations at the same time. The deadlines are similar; recipients and content are not.
| Framework | Trigger | Deadlines | Recipient |
|---|---|---|---|
| NIS-2 (Sec. 32 BSIG) | significant incident in the entity's own organisation | 24 h / 72 h / 1 month | joint BSI/BBK reporting office via the BSI portal |
| CRA (Art. 14 Regulation (EU) 2024/2847) | actively exploited vulnerability or severe incident having an impact on the security of a product with digital elements | 24 h / 72 h / 14 days (vulnerability) or 1 month (incident) | ENISA single reporting platform, coordinated by the competent CSIRT |
| GDPR (Art. 33, 34) | personal data breach | 72 h to the supervisory authority; data subjects without undue delay in case of high risk | state data protection authority |
Manufacturers that fall under NIS-2 as important entities have had to master both channels since 11 September 2026: an attack on the development environment is a NIS-2 incident; if a vulnerability in the product is exploited in the process, the CRA reporting obligation is added. A joint triage scheme that checks all three obligations for every incident prevents any of them being forgotten. The distinction between the frameworks is explained in the comparison CRA vs. NIS-2.
Internal reporting process in 5 steps
24 hours is a short time when the incident starts on a Friday evening. A robust process looks like this:
Every employee knows the internal reporting point (service desk, security hotline). Suspected cases are escalated immediately to the incident response team, including outside working hours. The time of becoming aware is logged.
Within a few hours, a designated role decides on the basis of a criteria catalogue under Section 2 No. 11 BSIG whether the incident is significant. When in doubt, report. The decision is documented with reasons.
A prepared template with the mandatory information is submitted in the BSI portal. Two people have access and a certificate so that holidays or illness do not jeopardise the deadline.
The incident response team isolates, analyses and restores. Forensic findings, IoCs and measures go into an incident log from which the 72-hour notification is produced. GDPR and CRA obligations are checked in parallel.
No later than one month later, the final report follows with root cause and remedial measures. A lessons-learned session feeds into the effectiveness assessment under Section 30 (2) No. 6 BSIG.
Common mistakes
- No portal access before the incident. ELSTER certificate and BSI portal registration are missing; the 24-hour deadline expires while applying for them.
- Waiting for certainty. Teams want to know the cause first. The early warning only requires a suspicion and possible impact.
- Awareness set incorrectly. The deadline starts when an employee becomes aware, not when the management body is briefed.
- Single point of responsibility. Only one person can report, and that person is unreachable.
- GDPR notification as a substitute. The notification to the data protection authority does not replace the BSI report, and vice versa.
- No progress report. The incident lasts longer than a month and the obligation under Section 32 (2) is overlooked.
- Customer information forgotten. Section 35 BSIG is not mapped in the process, even though BSI can order it.
Next steps
First check with the applicability check whether Section 32 BSIG applies to you, then secure portal access. After that comes the process: criteria catalogue, templates, roles, exercise. Our NIS-2 consulting builds reporting processes that hold 24 hours even at the weekend and integrates them with CRA and GDPR notifications. The overall framework is described on the NIS-2 overview page.

