Aller au contenu principal
Obligations

Notifier un incident important

Comparé sur 7 juridictions

En Union européenne (socle NIS2)

Notifier les incidents importants selon la chaîne 24 heures, 72 heures, un mois

Un incident est important s’il a causé ou est susceptible de causer une perturbation opérationnelle grave ou des pertes financières pour vous, ou s’il a affecté ou est susceptible d’affecter d’autres personnes en causant un préjudice matériel ou immatériel considérable. L’un ou l’autre de ces cas suffit, et un incident simplement susceptible de causer ce préjudice compte également. Informez votre CSIRT ou votre autorité compétente : une alerte précoce dans les 24 heures après en avoir eu connaissance, indiquant si des actes illicites ou malveillants sont suspectés et s’il pourrait y avoir un impact transfrontière ; une notification d’incident dans les 72 heures après en avoir eu connaissance, avec une première évaluation de la gravité et de l’impact ainsi que les éventuels indicateurs de compromission ; un rapport intermédiaire si on vous le demande ; et un rapport final dans le mois qui suit la notification à 72 heures. Si l’incident est toujours en cours à l’échéance du rapport final, remettez alors un rapport d’avancement, puis un rapport final dans le mois suivant la fin de son traitement.

Quand: Les délais de 24 et de 72 heures courent tous deux à compter de la connaissance de l’incident : ils ne se suivent donc pas — la notification à 72 heures n’est pas « 72 heures après l’alerte précoce ». Le délai d’un mois pour le rapport final court à compter de la remise de la notification à 72 heures. Un prestataire de services de confiance dispose de 24 heures, et non de 72, pour les incidents affectant ses services de confiance.

À quoi ressemble la preuve

  • Une procédure d’incident énonçant les échéances 24 h / 72 h / un mois et le responsable de chacune
  • Un journal des incidents consignant l’heure de la prise de connaissance, et pas seulement celle de la détection
  • Un contact nommément désigné, enregistré auprès du CSIRT national
  • Copies des alertes précoces, notifications et rapports finaux transmis
Base juridique: Directive (EU) 2022/2555, Art. 23(1), Art. 23(3) · Directive (EU) 2022/2555, Art. 23(4)(a)-(e) · Commission Implementing Regulation (EU) 2024/2690, Arts. 3, 5-14

En Ukraine

Report significant cyber incidents within ONE HOUR

Critical infrastructure operators and owners or holders of critical information infrastructure objects notify their sectoral or regional CSIRT without delay, within one hour, of every significant cyber incident. Where there is no sectoral or regional CSIRT, the notification goes to CERT-UA and the Situation Centre of the SBU, also within the hour. An incident counts as significant when its severity is high (orange), critical (red) or extraordinary (black) on the six-level scale that runs 0 to 5 — white, green, yellow, orange, red, black. Do not confuse this with the 24-hour, 72-hour and one-month cascade: that chain binds the subjects of the national response system reporting to the National Cybersecurity Coordination Centre, not the operator. The Law itself says only «невідкладно» and sets no hour figure; the hour comes from the Cabinet resolution.

Quand: One hour from becoming aware, for significant incidents. Owners and holders of systems processing state information resources report every incident within the hour, not only the significant ones.

S’applique lorsque

  • The service is delivered through information and communication systems
  • Systems processing state information resources report every incident

À quoi ressemble la preuve

  • An incident procedure that states the one-hour deadline and names who sends the notification
  • An incident log recording the time of awareness, not only the time of detection
  • Confirmation of which CSIRT you are attached to
  • A severity classification aligned to the six-level scale
Base juridique: Постанова КМУ № 1533 від 26.11.2025, п. 12, п. 17, п. 18, п. 20 · Наказ Адміністрації Держспецзв’язку № 351 від 14.05.2026 «Критерії визначення значного кіберінциденту» (зареєстровано в Мін’юсті 22.06.2026 за № 900/46294, чинний з 30.06.2026), п. 3 · Закон України «Про критичну інфраструктуру» № 1882-IX, ст. 21 ч. 4 п. 2 · Закон України «Про основні засади забезпечення кібербезпеки України» № 2163-VIII, ст. 9-1 ч. 3 абз. 2, ч. 4, ч. 5

En Allemagne

Report to the joint BSI/BBK Meldestelle on a 24-hour, 72-hour and one-month chain

Early warning within 24 hours, notification within 72 hours, an intermediate report if asked, and a final report within one month. Where the incident is still ongoing when the month is up, a progress report falls due then and the final report one month after handling concludes. Two German specifics: reports go to a joint BSI/BBK gemeinsame Meldestelle rather than to the BSI alone, and the statute says einen Monat — one month, not 30 days. In a 31-day month the difference is a real day.

Quand: 24 hours, then 72 hours, then one month from the 72-hour notification. Encode and diary "one month", never "30 days".

À quoi ressemble la preuve

  • An incident procedure naming the gemeinsame Meldestelle of BSI and BBK as the recipient
  • An incident log recording the time of awareness, not just the time of detection
  • Copies of the submitted early warning, notification and final report
Base juridique: BSI-Gesetz vom 2. Dezember 2025 (BGBl. 2025 I Nr. 301, S. 2), zuletzt geändert durch Artikel 8 Absatz 1 des Gesetzes vom 23. Juli 2026 (BGBl. 2026 I Nr. 226), § 32 Absatz 1, Absatz 2

KRITIS operators must transmit three extra items in every report

On top of the ordinary reporting content, an operator of a kritische Anlage additionally transmits the type of installation affected, the critical service concerned, and the impact on that service. This is content, not a separate clock: it rides on the same 24-hour, 72-hour and one-month chain.

Quand: Same deadlines as the ordinary report — the additional content is due with each filing.

S’applique lorsque

  • The KRITIS duty overlay: five duties that size alone never triggers

À quoi ressemble la preuve

  • A reporting template with fields for installation type, critical service and service impact
  • A current mapping of installations to the critical services they support
Base juridique: BSI-Gesetz vom 2. Dezember 2025 (BGBl. 2025 I Nr. 301, S. 2), zuletzt geändert durch Artikel 8 Absatz 1 des Gesetzes vom 23. Juli 2026 (BGBl. 2026 I Nr. 226), § 32 Absatz 3

En Pologne

Report significant incidents to your sectoral CSIRT, through S46, from the moment of detection

The chain is an early warning within 24 hours, a notification within 72 hours (24 hours for trust service providers), an interim report on request, a final report within one month of the 72-hour notification, and — where handling is still running at that point — a progress report followed by a fresh month after handling concludes. Three things are specifically Polish and each of them catches people out. The clocks run *od momentu jego wykrycia*, from DETECTION, not from becoming aware, which is earlier than the directive’s trigger. The recipient is your *CSIRT sektorowy*, not a single national CSIRT. And the filing must go through S46: failing to use S46 is a separate breach that is independently fineable under art. 73(1)(13), so a report delivered by email can leave you in breach even though the substance arrived on time. A public entity that is an *important* entity files only the 72-hour notification and is exempt from the early warning, the interim, the progress and the final reports.

Quand: 24 hours / 72 hours / one month, each running from detection. Trust service providers: 24 hours for the notification limb.

À quoi ressemble la preuve

  • An incident log that records the time of DETECTION, because that is what the Polish clock runs from
  • S46 submission receipts for each stage of the chain
  • A procedure naming your sectoral CSIRT and the person who owns each deadline
Base juridique: Ustawa z dnia 5 lipca 2018 r. o krajowym systemie cyberbezpieczeństwa (Dz. U. z 2026 r. poz. 20), KSC art. 11 ust. 1 pkt 4 oraz ust. 4a-4c (as amended by Dz.U. 2026 poz. 252) · Ustawa z dnia 5 lipca 2018 r. o krajowym systemie cyberbezpieczeństwa (Dz. U. z 2026 r. poz. 20), KSC art. 11 ust. 1a (as amended by Dz.U. 2026 poz. 252) · Ustawa z dnia 5 lipca 2018 r. o krajowym systemie cyberbezpieczeństwa (Dz. U. z 2026 r. poz. 20), KSC art. 11 ust. 2 (as amended by Dz.U. 2026 poz. 252) · Ustawa z dnia 5 lipca 2018 r. o krajowym systemie cyberbezpieczeństwa (Dz. U. z 2026 r. poz. 20), KSC art. 12b (as amended by Dz.U. 2026 poz. 252) · Ustawa z dnia 5 lipca 2018 r. o krajowym systemie cyberbezpieczeństwa (Dz. U. z 2026 r. poz. 20), KSC art. 12c (as amended by Dz.U. 2026 poz. 252) · Ustawa z dnia 5 lipca 2018 r. o krajowym systemie cyberbezpieczeństwa (Dz. U. z 2026 r. poz. 20), KSC art. 73 ust. 1 pkt 13 (as amended by Dz.U. 2026 poz. 252)

Check who currently receives your reports — routing switches per sector, on a date you have to look up

Until the competent authority for your sector publishes the communiqué declaring its sectoral CSIRT operationally capable, reports go to CSIRT MON, CSIRT NASK or CSIRT GOV. Routing switches to the sectoral CSIRT from the day after that publication. Sectoral CSIRTs must exist by 3 October 2027. The transitional routing does not apply where a sectoral cybersecurity team was appointed before 2025. This is a per-sector, date-dependent lookup keyed on a communiqué — we deliberately publish no static sector-to-CSIRT map, because whether any given sectoral CSIRT has declared operational capability has to be queried live in the relevant official journal, and a stale map would send a report to the wrong body inside a 24-hour window.

Quand: Applies from 3 April 2026 until, sector by sector, the operational-capability communiqué is published. Re-check before every filing.

À quoi ressemble la preuve

  • A dated note of the last check of your competent authority’s official journal, with the recipient it resolved to
Base juridique: Ustawa z dnia 23 stycznia 2026 r. o zmianie ustawy o krajowym systemie cyberbezpieczeństwa oraz niektórych innych ustaw (Dz. U. 2026 poz. 252), art. 42 ust. 1 · Ustawa z dnia 23 stycznia 2026 r. o zmianie ustawy o krajowym systemie cyberbezpieczeństwa oraz niektórych innych ustaw (Dz. U. 2026 poz. 252), art. 44 ust. 1-3 · Ustawa z dnia 23 stycznia 2026 r. o zmianie ustawy o krajowym systemie cyberbezpieczeństwa oraz niektórych innych ustaw (Dz. U. 2026 poz. 252), art. 46

En Tchéquie

Report incidents to NÚKIB — and note that NÚKIB, not you, judges significance

Report an incident that (i) manifested within the stanovený rozsah, (ii) originates in cyberspace, and (iii) is one for which intentional causation cannot be excluded within the 24-hour window. There is no significance filter on the higher-regime duty: NÚKIB decides significance, and must tell you within 24 hours of your report whether the incident has a significant impact on the state’s cyberspace. That inverts who judges significance and is materially more onerous than Article 23(1), where you filter first. NÚKIB or the Národní CERT gives its opinion within 24 hours of the initial report. The channel is the Portál Úřadu, falling back to the designated email address or a datová schránka.

Quand: Initial report within 24 hours after detection; notification within 72 hours after detection, reduced to 24 hours for trust service providers; an interim report on request; and the final report within 30 days from the day the 72-hour notification was submitted. If the incident is still ongoing at 30 days, submit an interim status report then and a final report within 30 days of resolution. Read the period as 30 calendar days, not “one month” — in a 31-day month that is stricter than Article 23(4)(d). The duty itself begins at the latest one year from delivery of the registration decision.

À quoi ressemble la preuve

  • An incident procedure stating 24 h / 72 h / 30 calendar days and who owns each
  • An incident log recording detection times, since the clocks run from detection
  • Copies of submitted reports and of NÚKIB’s 24-hour significance response
  • A tested fallback route: the designated email address and the datová schránka
Base juridique: Zákon č. 264/2025 Sb., o kybernetické bezpečnosti, § 15(1) · Zákon č. 264/2025 Sb., o kybernetické bezpečnosti, § 16 · Zákon č. 264/2025 Sb., o kybernetické bezpečnosti, § 17(1) · Zákon č. 264/2025 Sb., o kybernetické bezpečnosti, § 13(4), § 15(4)

Report incidents to the Národní CERT, with your own significance test applied

The same three conditions as the higher regime — manifested within the stanovený rozsah, originating in cyberspace, and intentional causation not excludable within the 24-hour window — plus a fourth: a self-assessed significant impact on the provision of the regulated service, measured against the tolerable level of harm you defined. The recipient is the Národní CERT and not NÚKIB. We do not name the organisation that operates the Národní CERT: the statute does not name it either, and we have not opened a source that does.

Quand: The § 16 timeline, identical to the higher regime: 24 hours after detection for the initial report, 72 hours after detection for the notification (24 hours for trust service providers), an interim report on request, and the final report within 30 days from the day the 72-hour notification was submitted; if still ongoing at 30 days, an interim status report and then a final report within 30 days of resolution.

À quoi ressemble la preuve

  • The significance assessment applying your únosná míra újmy to the incident
  • Copies of reports submitted to the Národní CERT, with timestamps
  • An incident procedure that routes to the Národní CERT rather than to NÚKIB
Base juridique: Zákon č. 264/2025 Sb., o kybernetické bezpečnosti, § 15(2)–(3) · Zákon č. 264/2025 Sb., o kybernetické bezpečnosti, § 16

En Estonie

Notify RIA on a 24-hour, 72-hour and one-month chain

An initial notification within 24 hours of becoming aware; an incident notification within 72 hours, or within 24 hours for a trust service provider; an interim report if RIA asks for one; and a final report within one month of submission of the 72-hour incident notification. If the incident is not resolved by then, that report counts as an interim report and a new final report is due within one month after resolution. Every notification runs to RIA: "CERT-EE" does not appear in KüTS at all, so do not go looking for a CERT-EE or NCSC portal to file with.

Quand: The one-month clock for the final report runs from submission of the 72-hour incident notification, not from the incident. Where the incident is still unresolved at that point, the month restarts from resolution.

À quoi ressemble la preuve

  • An incident procedure naming RIA as the recipient and stating the 24h / 72h / one-month steps
  • An incident log recording the time you became aware, not only the time of detection
  • Copies of the notifications actually filed, with their submission timestamps
Base juridique: Küberturvalisuse seadus (KüTS), § 8(1) · Küberturvalisuse seadus (KüTS), § 8(4¹)–(4³) · Küberturvalisuse seadus (KüTS), § 8(7)

Make sure the person who runs your system notifies you within 24 hours

Where you outsource the network or information system used for the service to another person, or host it with another person, you are responsible for ensuring that that person notifies you within 24 hours. This is a supply-chain pass-through duty with no analogue in the Directive: the clock does not move to your supplier, and responsibility for the notification chain stays with you.

Quand: Twenty-four hours, running to you rather than to RIA. Your own KüTS § 8 deadlines then run on top of it.

S’applique lorsque

  • The system is outsourced to, or hosted by, another person

À quoi ressemble la preuve

  • The contractual notification clause, with the 24-hour period stated in it
  • A list of the outsourcing and hosting providers the duty covers
  • Evidence that the notification path has been exercised at least once
Base juridique: Küberturvalisuse seadus (KüTS), § 8(1¹)

En Italie

Notify significant incidents to CSIRT Italia on a 24-hour, 72-hour and one-month chain

The recipient is CSIRT Italia, not ACN directly. An incident is significant if it has caused or is capable of causing severe operational disruption of services or financial loss to you, or has had or is capable of having repercussions on other natural or legal persons by causing considerable material or non-material loss — either limb is enough. The chain is a pre-notifica within 24 hours of becoming aware, indicating where possible whether the incident may be the result of unlawful or malicious acts or may have cross-border impact; a notifica dell’incidente within 72 hours with an initial assessment of severity and impact and any indicators of compromise; an intermediate report if CSIRT Italia asks; and a relazione finale within one month of the 72-hour notification, giving a detailed description, the root cause, the mitigation measures taken and under way, and the cross-border impact where known. Note the national vocabulary: Italy calls the 24-hour step a *pre-notifica*, where the directive’s own Italian says *preallarme*.

Quand: The 24-hour and 72-hour clocks both run from awareness, so they are not sequential. The one-month clock for the final report runs from submission of the 72-hour notification. The duty itself begins nine months from the ACN communication under art. 42(1)(c) — half the time allowed for the governance and measures duties.

S’applique lorsque

  • A public administration listed in allegato III, regardless of size
  • An allegato IV entity type, once identified under art. 3(13)
  • Already an operator of essential services under d.lgs. 65/2018

À quoi ressemble la preuve

  • An incident procedure naming CSIRT Italia and the 24h / 72h / one-month steps
  • An incident log recording the time you became aware, not only detection
  • Copies of pre-notifiche, notifiche and relazioni finali submitted
Base juridique: Decreto legislativo 4 settembre 2024, n. 138, art. 25 · Decreto legislativo 4 settembre 2024, n. 138, art. 42, comma 1, lettera c)

Correspond à

ISO27001 A.5.19ISO27001 A.5.20ISO27001 A.5.22ISO27001 A.5.24ISO27001 A.5.25ISO27001 A.5.26ISO27001 A.5.9ISO27001 A.6.8NISTCSF DE.AE-06NISTCSF DE.AE-08NISTCSF GV.SC-04NISTCSF GV.SC-08NISTCSF ID.AM-01NISTCSF RS.CO-02NISTCSF RS.CO-03NISTCSF RS.MA-01

Suivez cette obligation sous forme de contrôles et de preuves