NIS2 guide
NIS2 incident reporting: 24 hours, 72 hours, one month
When a significant incident hits, NIS2 sets three main deadlines. The first two count from the moment you become aware of the significant incident, or, in the Swedish regulation, from the moment it is identified as significant. The third counts from the day you submit your incident notification. Sweden has binding rules on what counts as significant and on what each report must say.
On this page
This is a plain-language summary, not legal advice. Where this page and the law differ, the law decides.
1. In short
- Early warning: within 24 hours of becoming aware (the law) or of identifying the incident as significant (the authority's regulation). Section 4 shows both.
- Incident notification: within 72 hours of the same moment.
- Final report: within one month of the incident notification.
- In Sweden the authority's binding regulation MCFFS 2026:8 sets what counts as significant and what each report must say. It has no non-binding advice part: everything in it is binding.
- Only significant incidents have to be reported (Article 23(1)).
- Reporting does not by itself increase your liability (Article 23(1)).
2. The timeline
The reports are set out in Article 23(4) of the NIS2 directive. The directive counts the 24 and 72 hours from the moment you become aware of the significant incident. The month counts from the day you submit the incident notification. The table shows the directive. What Swedish rules add is in section 9 and section 10.
| Deadline | What the report must say |
|---|---|
| 24 hours Early warning Point (a) | Where applicable, whether the incident is suspected of being caused by unlawful or malicious acts, and whether it could have a cross-border impact |
| 72 hours Incident notification Point (b) | Where applicable, an update of the early warning. An initial assessment of the incident, including its severity and impact. Indicators of compromise, where available |
| On request Intermediate report Point (c) | Relevant status updates, when the CSIRT or the authority asks for them |
| One month Final report Point (d) | A detailed description of the incident, including its severity and impact. The type of threat or root cause that is likely to have triggered it. Mitigation measures applied and ongoing. The cross-border impact, where applicable |
| Still ongoing Progress report Point (e) | If the incident is still ongoing when the final report is due: a progress report at that time, then a final report within one month of handling the incident |
Both of the first two deadlines also say "without undue delay". The hours are the outer limit, not the target.
For significant incidents that have an impact on the provision of their trust services, providers of trust services have 24 hours, not 72, for the incident notification (Article 23(4)). In Sweden the 24 hours are tied to the provider: a provider of trust services must submit the incident notification within 24 hours (2 kap. 6 § of the law; MCFFS 2026:8, 2 kap. 4 §, last paragraph).
3. What counts as significant
Article 23(3) names two cases. An incident is significant if:
- "it has caused or is capable of causing severe operational disruption of the services or financial loss for the entity concerned"
- "it has affected or is capable of affecting other natural or legal persons by causing considerable material or non-material damage"
Either case is enough. The Swedish law joins the two with "or" (2 kap. 5 §). Note the words "is capable of". An incident can be significant before any damage has been done.
For the providers covered by Implementing Regulation (EU) 2024/2690, that regulation specifies the cases further. The Commission may do the same for other kinds of entity (Article 23(11)).
In Sweden: binding criteria
The authority has set binding criteria in MCFFS 2026:8 (in force 1 July 2026). Chapter 3 applies in general. Chapter 4 adds shorter limits for some sectors. Both leave out the five sectors named below the second table. The main limits:
| Case | Binding criterion (MCFFS 2026:8) |
|---|---|
| Severe disruption, general rule 3 kap. 1 § | Sector-critical systems (sektorskritiska system) were unavailable or degraded so that sector activity could be run only in limited form for more than 12 hours, or staff had to use alternative working methods for more than 48 hours. Or information that needs extended protection (information i behov av utökat skydd), belongs to you and is handled in a sector-critical system became available to unauthorised persons, was altered or was destroyed. The sector limits in the next table also count (3 kap. 1 §, point 3). |
| Financial damage 3 kap. 3 and 5 §§ | The total cost is more than 5 percent of your total annual turnover in the previous financial year. For public administration: 5 percent of your appropriation or total revenue. Count restoration of lost or altered information, replacing or restoring systems, outside advice (incident handling, legal, forensics, clean-up), extra staff costs, unmet contract obligations and lost revenue from unplanned production loss. If the amount cannot be fixed when you report, estimate it. |
| Significant damage to others 3 kap. 6 § | Information that needs extended protection, which you process for another legal person or for at least 500 natural persons, became available to unauthorised persons, was altered or was destroyed. Or the incident caused pollution damage under 10 kap. 1 § miljöbalken. Or you have learned that it led to crisis-staff mode or reorganisation at a provider of an important societal function, to serious injury or illness, or to death. |
| Could cause it 3 kap. 2, 4 and 7 §§ | A significant cyber threat or a significant vulnerability (betydande sårbarhet) has arisen in your systems that is likely to cause, or that makes possible, the consequences above. No damage needs to have happened yet. |
| Repeated incidents 3 kap. 8 § | Incidents that are not significant alone count as significant when they happened at least twice within six months, are assessed to have the same root cause and together caused financial damage as above. |
- Sector-critical system (sektorskritiskt system): a system you need to run your sector activity or to provide your outside services.
- Information that needs extended protection: information that outside rules require to be protected at a set level, or that you judge needs the same level of protection (MCFFS 2026:8, 1 kap. 3 §).
Chapter 4 sets shorter, sector-specific limits for severe disruption (4 kap. 1–9 §§). Examples:
| Sector | Limits (MCFFS 2026:8, 4 kap.) |
|---|---|
| Public administration (1 §) | Limited operation for more than 4 hours, or alternative working methods for more than 12 hours |
| Electricity, district heating and cooling (2 §) | External services not provided to at least 2,000 end users or 50 percent of end users for more than 2 hours; alternative working methods for more than 6 hours; grid or production control systems not usable as intended for more than 1 hour |
| Gas and hydrogen (3 §), oil (4 §) | Gas and hydrogen: control and monitoring under the system responsibility service (systemansvarstjänst) not possible as intended for more than 1 hour. Oil: control and monitoring of pipelines and plants not possible as intended for more than 2 hours. Both: alternative working methods for more than 6 hours |
| Sea, air and road transport (5 §) | Limited operation for more than 1 hour; or external services down for more than 1 hour and likely to affect at least 1,000 users or an area of at least 10,000 km2; or alternative working methods for more than 6 hours |
| Rail and public transport (6 §) | Limited operation likely to affect more than 5 percent of planned departures in a traffic day for a mode of transport; or alternative working methods for more than 6 hours |
| Care providers (7 §) | Limited operation of part of the activity for more than 1 hour; alternative working methods for more than 6 hours; a reporting duty under 3 kap. 5 § first paragraph patientsäkerhetslagen (2010:659); or ambulance care not provided |
| Drinking water (8 §), waste water (9 §) | Sector-critical systems unavailable or degraded for more than 4 hours, or alternative working methods for more than 8 hours |
One sentence limits who these Swedish criteria cover. The criteria in chapters 3–4, and the duty to inform recipients in chapter 5, "omfattar inte" (do not cover) sector activity in digital infrastructure, digital providers, ICT service management (business to business), postal and courier services, and space (MCFFS 2026:8, 1 kap. 1 §, second paragraph). That sentence names chapters 3–4 and 5 only. This page does not say more than that about those sectors: if you work in one of them, ask FRA how the report deadlines apply to you, and read Article 23(3) of the directive and, where it applies, Implementing Regulation (EU) 2024/2690.
4. When the clock starts
The directive says both the 24-hour and the 72-hour deadline run from "becoming aware of the significant incident" (Article 23(4), points (a) and (b)). The clock starts when you know about the significant incident, not when the incident began. The directive does not define that moment more closely.
The Swedish texts word it in two ways:
| Text | Clock starts |
|---|---|
| The law 2 kap. 5 & 6 §§ | When the operator "har fått kännedom om" the incident: has become aware of it |
| MCFFS 2026:8 2 kap. 3 & 4 §§ | When the incident has been "identifierats som betydande" under chapters 3–4: identified as significant |
This page does not say which one an authority will apply. Our advice: to be safe, count from whichever of the two moments comes first. Write down both: when you first knew about the incident, and when you identified it as significant.
For the providers covered by Implementing Regulation (EU) 2024/2690, its recital 31 says more. An entity has become aware when, after an initial assessment, it "has a reasonable degree of certainty that a significant incident has occurred".
The final report is different. Its month runs from the day you submitted the incident notification (point (d)).
5. Who you report to
You report to your country's CSIRT or, where applicable, its competent authority (Article 23(1)).
In Sweden, incident reports go to the CSIRT unit. Since 1 July 2026 that is Försvarets radioanstalt (FRA). Before that date it was Myndigheten för civilt försvar (MCF). The change was made by SFS 2026:623. Submit each report the way, and through the contact channels, that FRA has published (MCFFS 2026:8, 2 kap. 1 §). State authorities that have already reported the same incident under förordning (2022:524) om statliga myndigheters beredskap only supplement those reports, within the deadlines in the law (2 kap. 2 §).
6. What you get back
The CSIRT or the authority must answer without undue delay, and where possible within 24 hours of your early warning. The answer includes initial feedback on the incident and, if you ask for it, guidance or operational advice on mitigation measures. If the incident is suspected to be criminal, you also get guidance on reporting it to law enforcement (Article 23(5)).
7. Telling the people who use your service
- Where appropriate, you must notify the recipients of your services, without undue delay, of a significant incident that is likely to adversely affect those services (Article 23(1)).
- Where applicable, when a significant cyber threat could affect them, you must tell them, without undue delay, about any measures or remedies they can take. Where appropriate, you also tell them about the threat itself (Article 23(2)).
In Sweden the authority's binding regulation sets what to say (MCFFS 2026:8, chapter 5):
- Significant incident that affected external services (5 kap. 1 §): tell recipients as soon as it can be done what the incident is, where applicable what they need to do to limit the consequences, and where applicable what the consequences may be if they do not. You do not have to give this information if you judge that it could make the incident harder to handle or make its consequences worse.
- Significant cyber threat that is not an incident (5 kap. 2 §): tell recipients as soon as it can be done what the threat is, where applicable what they need to do to reduce the risk that it becomes an incident, and where applicable what happens if they do not. You do not have to say what the threat is if you judge that this would raise the risk that an incident happens.
These two paragraphs do not cover the sectors named at the end of section 3.
8. If personal data is involved
A personal data breach has its own rule in the GDPR. The controller must notify the data protection authority without undue delay and, where feasible, not later than 72 hours after becoming aware of the breach, unless the breach is unlikely to result in a risk to people's rights and freedoms (GDPR Article 33(1)).
That is a separate report to a separate authority. One incident can require both. In Sweden, the supervisory authority under Cybersäkerhetslagen cooperates with Integritetsskyddsmyndigheten (IMY) on incidents that are also personal data breaches (ordinance 2025:1507, 18 §).
9. In Sweden
Cybersäkerhetslagen (2025:1506) carries the same deadlines in chapter 2. In the law the clock runs from becoming aware.
| Section | What it requires |
|---|---|
| 2 kap. 5 § | Notify the authority of a significant incident (betydande incident) as soon as possible and at the latest 24 hours after becoming aware of it |
| 2 kap. 6 § | Submit an incident notification (incidentanmälan) as soon as possible and at the latest 72 hours after becoming aware. 24 hours for providers of trust services |
| 2 kap. 7 § | Submit an interim report (delrapport) when the authority asks |
| 2 kap. 8 § | Submit a final report (slutrapport) at the latest one month after the incident notification. If the incident is still ongoing, submit a status report then, and the final report within one month of the incident being handled |
Not reporting counts as a serious breach when the authority decides how to act (4 kap. 3 §). More on the Swedish law: Cybersäkerhetslagen: what Sweden's NIS2 law requires.
The law lets the authority issue more detailed rules (2 kap. 14 §). That has been done. MCFFS 2026:8, "Myndigheten för civilt försvars föreskrifter om incidentrapportering och informationsskyldighet för väsentliga och viktiga verksamhetsutövare", has been in force since 1 July 2026. It replaced MCFFS 2026:6, whose 3 kap. 1 § it corrects. It was issued by MCF. Since 1 July 2026 FRA holds the rule-making role (ordinance 2025:1507, 38–39 §§, as changed by SFS 2026:623), and the regulation applies unchanged. It is binding in full. Unlike MCFFS 2026:11, it has no part of non-binding general advice.
10. What each report must say in Sweden
Binding content under MCFFS 2026:8, 2 kap. 3–6 §§. Use it as a checklist for your drafts. In Swedish, the first report is the upplysning.
For the five sectors named at the end of section 3, ask FRA how these deadlines apply to you. The definition of a significant incident does not cover them.
| Report | Deadline and content |
|---|---|
| Early warning upplysning 2 kap. 3 § | As soon as it can be done, and at the latest 24 hours after the incident was identified as significant. It states: (1) your name, contact details and organisation number; (2) whether the incident is ongoing; (3) the course of events, and when and how the incident was discovered; (4) whether it is suspected to be caused by intentionally harmful or unlawful acts; (5) if it began at a supplier, information about the supplier; (6) the effect on your sector activity; (7) the consequences it causes or risks causing; (8) whether it has or risks having cross-border consequences. Points 2–8 rest on a preliminary assessment. |
| Incident notification incidentanmälan 2 kap. 4 § | As soon as it can be done, and at the latest 72 hours after you identified the incident as significant (24 hours for providers of trust services). It updates the early warning and adds: (1) when the incident happened; (2) when it ended, or an estimate of how long it is expected to last; (3) an assessment of the cause; (4) the effect on systems; (5) where applicable, indicators of compromise (angreppsindikatorer); (6) where applicable, the effect on information that needs extended protection. |
| Final report slutrapport 2 kap. 5 § | At the latest one month after the incident notification, or one month after the incident was handled. It updates the earlier reports and adds: (1) a final assessment of the consequences, where applicable with the estimated number of recipients of your services affected, the geographic area, financial damage, cross-border consequences and the effect on important societal functions; (2) as far as possible a detailed description of the root cause; (3) the technical and organisational measures taken to handle the incident and, where applicable, taken or to be taken to handle and minimise the consequences and to prevent similar incidents. |
| Progress report lägesrapport 2 kap. 6 § | If the incident is still ongoing after one month, you submit this instead of the final report. It states: why the incident is still ongoing; an estimate of how long it is expected to last; whether it still affects, or risks affecting, your sector activity; where applicable, indicators of compromise. |
Prepare the numbers early: the final report asks for the number of affected recipients and for the financial damage.
11. Be ready before it happens
These are practical steps, not legal text.
- Decide who judges whether an incident is significant, and who stands in for that person.
- Keep the contact details for reporting somewhere you can reach without your own network.
- Prepare the three reports as drafts, with the fields from the timeline above.
- Write down when you first knew about the incident and when you identified it as significant. To be safe, count from whichever of the two moments comes first (section 4).
- Log every decision and who made it.
12. How SimpleSecurity helps
SimpleSecurity keeps the record and watches the clocks. You stay in charge of what is sent and when.
- Incident Register: tracks the NIS2 24-hour and 72-hour clocks, counted from the moment you became aware, and the GDPR breach-notification clock.
- Automatic incidents: an incident is created automatically from downtime, and vulnerability, certificate and vendor signals are queued as incident candidates for you to judge.
- Aegis Intelligence: drafts incident reviews, breach notices and NIS2 reports from your own records, for you to check and save.
See every service or see the plans.
Related guides
13. Sources
- Directive (EU) 2022/2555 (NIS2), Article 23
- Commission Implementing Regulation (EU) 2024/2690
- Regulation (EU) 2016/679 (GDPR), Article 33
- Cybersäkerhetslag (2025:1506), 2 kap. 5–8 §§ and 4 kap. 3 §
- Cybersäkerhetsförordning (2025:1507), 6 §, 18 § and 31 §
- Förordning (2026:623) om ändring i cybersäkerhetsförordningen, in force 1 July 2026
- MCFFS 2026:8, incident reporting and the duty to inform recipients, in force 1 July 2026