Vai al contenuto principale
Obblighi

Segnalare un incidente significativo

Confrontato fra 7 giurisdizioni

In Unione europea (base NIS2)

Segnalare gli incidenti significativi lungo la catena 24 ore, 72 ore, un mese

Un incidente è significativo se ha causato o è in grado di causare una grave perturbazione operativa o perdite finanziarie per te, oppure se ha colpito o è in grado di colpire altri causando danni materiali o immateriali considerevoli. Basta una delle due ipotesi, e conta anche un incidente che quel danno avrebbe soltanto potuto causarlo. Informa il tuo CSIRT o l’autorità competente: un preallarme entro 24 ore da quando ne sei venuto a conoscenza, indicando se si sospettano atti illegittimi o malevoli e se vi può essere un impatto transfrontaliero; una notifica dell’incidente entro 72 ore da quando ne sei venuto a conoscenza, con una valutazione iniziale di gravità e impatto e gli eventuali indicatori di compromissione; una relazione intermedia se richiesta; e una relazione finale entro un mese dalla notifica delle 72 ore. Se l’incidente è ancora in corso quando la relazione finale è dovuta, presenta allora una relazione sui progressi e la relazione finale entro un mese dalla conclusione della gestione.

Quando: I termini di 24 e 72 ore decorrono entrambi dalla conoscenza dell’incidente, quindi non sono in sequenza: la notifica delle 72 ore non è «72 ore dopo il preallarme». Il termine di un mese per la relazione finale decorre dalla trasmissione della notifica delle 72 ore. Un prestatore di servizi fiduciari ha 24 ore, non 72, per gli incidenti che incidono sui suoi servizi fiduciari.

Che aspetto hanno le evidenze

  • Una procedura per gli incidenti che indichi i termini di 24 h, 72 h e un mese e il responsabile di ciascuno
  • Un registro degli incidenti che annoti l’ora in cui se ne è avuta conoscenza, non solo quella del rilevamento
  • Un referente designato per nome e registrato presso il CSIRT nazionale
  • Copia dei preallarmi, delle notifiche e delle relazioni finali trasmessi
Base giuridica: 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

In Ucraina

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.

Quando: 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.

Sorge quando

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

Che aspetto hanno le evidenze

  • 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 giuridica: Постанова КМУ № 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

In Germania

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.

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

Che aspetto hanno le evidenze

  • 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 giuridica: 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.

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

Sorge quando

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

Che aspetto hanno le evidenze

  • 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 giuridica: 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

In Polonia

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.

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

Che aspetto hanno le evidenze

  • 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 giuridica: 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.

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

Che aspetto hanno le evidenze

  • A dated note of the last check of your competent authority’s official journal, with the recipient it resolved to
Base giuridica: 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

In Cechia

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.

Quando: 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.

Che aspetto hanno le evidenze

  • 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 giuridica: 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.

Quando: 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.

Che aspetto hanno le evidenze

  • 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 giuridica: Zákon č. 264/2025 Sb., o kybernetické bezpečnosti, § 15(2)–(3) · Zákon č. 264/2025 Sb., o kybernetické bezpečnosti, § 16

In Estonia

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.

Quando: 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.

Che aspetto hanno le evidenze

  • 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 giuridica: 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.

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

Sorge quando

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

Che aspetto hanno le evidenze

  • 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 giuridica: Küberturvalisuse seadus (KüTS), § 8(1¹)

In Italia

Notifica gli incidenti significativi al CSIRT Italia su catena 24 ore, 72 ore e un mese

Il destinatario è il CSIRT Italia, non direttamente l’ACN. Un incidente è significativo se ha causato o è in grado di causare una grave perturbazione operativa dei servizi o perdite finanziarie per te, oppure se ha avuto o è idoneo a provocare ripercussioni su altre persone fisiche o giuridiche con perdite materiali o immateriali considerevoli: basta una delle due ipotesi. La catena è una pre-notifica entro 24 ore da quando ne sei venuto a conoscenza, indicando ove possibile se l’incidente possa ritenersi il risultato di atti illegittimi o malevoli o possa avere impatto transfrontaliero; una notifica dell’incidente entro 72 ore con valutazione iniziale di gravità e impatto e gli indicatori di compromissione disponibili; una relazione intermedia su richiesta del CSIRT Italia; e una relazione finale entro un mese dalla notifica delle 72 ore, con descrizione dettagliata, causa originale, misure di attenuazione adottate e in corso e impatto transfrontaliero ove noto. Nota il lessico nazionale: l’Italia chiama *pre-notifica* il passaggio delle 24 ore, dove la versione italiana della direttiva dice *preallarme*.

Quando: I termini di 24 e 72 ore decorrono entrambi dalla conoscenza dell’incidente, quindi non sono in sequenza. Il termine di un mese per la relazione finale decorre dalla trasmissione della notifica delle 72 ore. L’obbligo decorre a nove mesi dalla comunicazione ACN ai sensi dell’art. 42, comma 1, lettera c) — metà del tempo concesso per governance e misure.

Sorge quando

  • Pubblica amministrazione elencata nell’allegato III, indipendentemente dalle dimensioni
  • Tipologia di soggetto dell’allegato IV, una volta individuata ai sensi dell’art. 3, comma 13
  • Già operatore di servizi essenziali ai sensi del d.lgs. 65/2018

Che aspetto hanno le evidenze

  • Una procedura di incidente che nomini il CSIRT Italia e i passaggi 24 h / 72 h / un mese
  • Un registro che annoti il momento della conoscenza, non solo del rilevamento
  • Copia delle pre-notifiche, delle notifiche e delle relazioni finali trasmesse
Base giuridica: Decreto legislativo 4 settembre 2024, n. 138, art. 25 · Decreto legislativo 4 settembre 2024, n. 138, art. 42, comma 1, lettera c)

Corrisponde a

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

Gestisci questo obbligo come controlli con evidenze