What's inside
- Clarify responsibilities, deputies and reporting access before an incident.
- Recognise significant incidents and record the assessment.
- Prepare early warning, notification and final reporting with the correct deadline triggers.
- Identify preparation gaps; document actual incidents in the Incident Report.
Check preparedness or document an actual incident?
This checklist reviews organisational preparedness. It does not replace a complete response plan or the handling of an actual incident.
The Incident Report is the complementary internal case file for the timeline, affected parties, impact, root cause analysis and corrective actions. Regulatory reporting uses the applicable official reporting channel.
Who is subject to these NIS2 reporting deadlines?
The deadlines below concern significant incidents affecting essential and important entities under German BSIG. Assess significance and the point of awareness, and document your reasoning; not every alert automatically triggers a reporting duty. Assess other obligations, such as personal-data breach notification, separately.
Basics & Registration
3 Checkpoints
Check if you are in scope
Assess sector, size and statutory exceptions using the legal criteria and BSI guidance. Access to the registration portal does not determine whether you are in scope.
Complete BSI registration
Check § 33 BSIG: generally register no later than three months after first or again qualifying as an affected entity, not merely after internal discovery. Notify changes within the applicable deadlines.
Appoint an incident response manager
A person or team that is notified immediately for every incident and coordinates the response.
Detection & Classification
3 Checkpoints
Set up monitoring and alerting
Define risk-appropriate monitoring, alert assessment, escalation and availability outside office hours. Test the process in practice.
Define significance criteria
Assess severe operational disruption or financial loss to the entity, and considerable material or non-material damage to others, including potential effects. Consider applicable detailed criteria (§ 2 No. 11 BSIG).
Document the classification process
Define a prompt assessment and escalation process. Record awareness, significance and decisions. Reporting deadlines do not wait for completion of root cause analysis.
Reporting Process
3 Checkpoints
Ensure 24-hour early warning capability
Report significant incidents without undue delay and within 24 hours of awareness using the applicable BSI channel (§ 32(1), first sentence, No. 1 BSIG).
Prepare 72-hour incident notification
Without undue delay and within 72 hours of awareness: update the early warning, assess severity and impact and include available IoCs. Prepare intermediate reports on request (§ 32(1) Nos. 2 and 3 BSIG).
Prepare the final report within one month
No later than one month after the notification under No. 2. For an ongoing incident submit a progress report, then the final report after handling is completed (§ 32(1) No. 4 and (2) BSIG).
Supply Chain & Improvement
2 Checkpoints
Inventory critical suppliers
Record relevant suppliers and dependencies, assess risks and agree appropriate security and notification obligations. Keep reachable incident contacts.
Establish a post-mortem process
Define how incidents are reviewed, causes and improvements documented and actions followed up. Use the Incident Report as the actual case file.
Get the complete checklist as a PDF
All 11 checkpoints on A4 to print and check off. Free, all you need is your email address.