TOOLBOX · DOWNLOAD
One sheetfor everyreporting stage.
Essential and important entities report a significant cybersecurity incident to the competent CSIRT in stages: early warning within 24 hours of becoming aware, notification within 72 hours, and a final report no later than one month after the notification (§ 34 NISG 2026). Reports are submitted via the NIS2-Services application in the Unternehmensserviceportal (Austrian business service portal). This worksheet collects internally what you need for this: master data, points in time, the significance review under § 35 NISG 2026 and § 5 NISV 2026, the information for each reporting stage with references, informing your customers, the parallel review under Art. 33 GDPR, and a log.
Free PDF · Template
NIS2 Incident Report: Template for Early Warning, Notification, and Final Report
- Topic
- NIS2 & Compliance
- Format
- PDF, A4
- Length
- 11 pages
- Size
- 138 KB
- Updated
- Oct 25, 2026
- Sources
- 10
- Usage
- Adaptation for your own use permitted; redistribute unchanged
WHO IT IS FOR
Who This
Is for.
A worksheet to fill in: information for each reporting stage under § 34 NISG 2026, significance under the NISV 2026, customer information, GDPR review, and log.
- Essential and important entities under the NISG 2026
- Information security officers, IT management, and incident response managers
- IT service providers who support customers during an incident or report on their behalf with power of representation
8 SECTIONS
What Is
Inside.
- 01
How to Work with the Template
Collect internally, report via NIS2-Services: what the worksheet does and what it does not replace.
- 02
Part A: Master Data and Reporting Channel
Fill in advance: who reports, to which CSIRT, with which access, and with which deputy.
- 03
Part B: Points in Time, Deadlines, and Log
From the moment of becoming aware, the 24 and 72 hours run, including on weekends. This part covers points in time, deadlines, and the log.
- 04
Part C: Significance Checklist
§ 35 NISG 2026 and the criteria of § 5 NISV 2026; for digital providers, the EU thresholds of IR 2024/2690.
- 05
Part D: Early Warning within 24 Hours
Reduced to the essentials: so that the CSIRT is informed and you get support if needed.
- 06
Part E: Notification within 72 Hours
Update the early warning, initial assessment with severity and impact, and indicators of compromise where available.
- 07
Part F: Intermediate, Progress, and Final Report
What follows the notification: on request, if the incident is ongoing, and no later than one month after the notification.
- 08
Part G: Recipients of the Services and Data Protection
Inform customers under § 34 para. 3 NISG 2026 and check the notification under Art. 33 GDPR in parallel.
EXCERPT
Part C: Significance Checklist
You must report every significant cybersecurity incident, meaning an event that compromises the availability, authenticity, integrity, or confidentiality of data or services (§ 3 no. 30 NISG 2026) and is significant. The NISV 2026 (BGBl. II No. 290/2026, promulgated on October 1, 2026) lists in § 5 cases that are significant in any case. According to the explanatory notes, “is capable of causing” in § 5 para. 1 no. 1 to 3 means that the effect is to be expected in the near future in the ordinary course of events. Check what has occurred or is imminent in this way.
- § 35 para. 1 NISG 2026: severe operational disruption of the services or severe financial losses for the entity (no. 1), or considerable material or non-material damage to other persons (no. 2).
- § 5 para. 1 no. 1 NISV 2026: direct financial loss exceeding €500,000 or 5% of annual turnover in the previous financial year, whichever is lower.
- No. 2: leakage of trade secrets within the meaning of § 26b UWG (Austrian Unfair Competition Act) or of information subject to secrecy under § 6 IFG (Austrian Freedom of Information Act).
- No. 3 and 4: death or serious damage to the health of a natural person.
- No. 5: successful, suspected malicious, and unauthorized access to network and information systems that is likely to cause severe operational disruption.
- No. 6 with § 7: at least two incidents in six months that are not significant on their own, with the same apparent root cause and impact, which together exceed the threshold from no. 1.
- No. 7 and 8: outage or limited availability of the services for more than 24 hours, for more than 100,000 users or 10% of users (whichever is lower), or in the territory of at least one federal state.
- No. 9: the incident has activated crisis management or disaster recovery plans of business continuity management.
- Exclusion under § 6 NISV 2026: only a scheduled interruption of operations or the planned consequences of scheduled maintenance work. This is not a significant incident.
The general criteria continue to apply alongside § 5 NISV 2026. Under § 35 para. 2 NISG 2026, these include the dependence of other sectors on your service, effects on the environment, public safety, or health, your market share, the affected area including cross-border impact, the affected systems, the severity of the threat, exploited vulnerabilities, and experience with similar incidents.
For entities under IR (EU) 2024/2690 (DNS, TLD name registries, cloud, data centers, content delivery networks, managed services and managed security services, online marketplaces, search engines, social networks, trust services), its Art. 3 and 4 and, depending on the type, Art. 5 to 14 apply; according to the explanatory notes, § 5 NISV 2026 governs the other entities. Managed services and managed security services additionally under Art. 10: completely unavailable for more than 30 minutes, limited for more than one hour for more than 5% or 1 million users in the Union (whichever is lower), or data compromised by a suspected malicious act or for this group of users.
| Result | Entry |
|---|---|
| Significant: yes / no / still open; criteria met | __________ __________ __________ __________ |
| Reasoning in two or three sentences | __________ __________ __________ __________ __________ __________ __________ __________ |
| Decided by, date, time; review again on | __________ __________ __________ __________ |
SOURCES
Supported
by Sources.
- NISG 2026, BGBl. I No. 94/2025, current version in the RIS (opens in a new tab)Version as of October 25, 2026, unchanged since the original version; §§ 3 no. 30, 8, 24, 29, 34, 35; accessed October 25, 2026
- NISV 2026, BGBl. II No. 290/2026, authentic promulgation in the RIS (opens in a new tab)§§ 5 to 7; current version unchanged on October 25, 2026; accessed October 25, 2026
- Federal Office for Cyber Security: Explanatory notes on the NISV 2026 (opens in a new tab)On § 5: scope, reporting by representatives, withdrawal, “is capable of causing”; accessed October 25, 2026
- Federal Office for Cyber Security: Reporting obligation and deadlines (opens in a new tab)NIS2-Services, alternative reporting channel, report types, withdrawal; page dated October 5, 2026, accessed October 25, 2026
- Federal Office for Cyber Security: Law and documents, reporting forms for the alternative reporting channel (opens in a new tab)Forms for early warning, notification, final report, and withdrawal, version 1.0, as of October 1, 2026; accessed October 25, 2026
- Federal Office for Cyber Security: Frequently asked questions, reports (opens in a new tab)Weekends, suppliers, several member states; page dated September 25, 2026, accessed October 25, 2026
- Implementing Regulation (EU) 2024/2690, significant incidents (opens in a new tab)Art. 1, 3, 4, and 10; OJ L of October 18, 2024
- Regulation (EU) 2016/679 (GDPR), Art. 33 and 34 (opens in a new tab)Notification to the supervisory authority and communication to data subjects
- Datenschutzgesetz (DSG, Austrian Data Protection Act), § 18 Data Protection Authority (opens in a new tab)§ 18 para. 1, version as of October 25, 2026
- Commission proposal for a Digital Omnibus Regulation, COM(2025) 837 (opens in a new tab)Explanatory memorandum and Art. 33 GDPR and Art. 23a NIS2 Directive in the proposed version; procedure 2025/0360(COD)
This template must be adapted to your entity and does not replace legal advice. It collects information internally; reports are submitted via the reporting channel of the competent CSIRT. The legal texts of the NISG 2026, the NISV 2026, and the GDPR in their current versions and the information requested in the reporting portal are authoritative.
TOOLBOX
Explore
Further.
- Kostenlos
NIS2 applicability check (German)
Am I affected? In 3 minutes
Check Now NIS2 Reporting Obligations
Deadlines, content, and recipients of reports under the NISG 2026 with references, plus a preparation checklist.
Learn MoreNIS2 Cockpit
Readiness and evidence structure for NIS2, in a controlled assessment. Not legal advice.
Learn MoreNIS2 in the Glossary
What the NIS2 Directive governs and whom it affects, briefly explained.
Learn More
NIS2 & COMPLIANCE
More on
This Topic.
- PDF
NIS2 Reporting Obligations
Early warning within 24 hours, notification within 72 hours, final report after one month: deadlines, content, and recipients with references to the NISG 2026, plus a checklist.
View - PDF
GDPR Data Breach Checklist
Data breach detected, now what? Establish the breach, assess the risk, notify the Austrian Data Protection Authority (Datenschutzbehörde) on time, inform data subjects and document everything, under Art. 33 and 34 GDPR.
View - PDF
Supplier Security Questionnaire
Fill-in questionnaire for IT service providers and suppliers: organization, access, vulnerabilities, incident reporting, audit rights and termination, based on NISG 2026 and IR (EU) 2024/2690.
View
YOUR NEXT STEP
From Paper
to Practice.
We review with you what is already implemented in your environment and put the rest into practice: as a project with EXPERTS or as ongoing operations with GRID.