Olulisest intsidendist teatamine
Võrreldud 7 jurisdiktsioonis
Jurisdiktsioonis Euroopa Liit (NIS2 alus)
Teatage olulistest intsidentidest ahelas 24 tundi, 72 tundi, üks kuu
Intsident on oluline, kui see on põhjustanud või võib põhjustada teile tõsise talitlushäire või rahalise kahju või kui see on mõjutanud või võib mõjutada teisi, tekitades märkimisväärset varalist või mittevaralist kahju. Piisab kummastki alusest ja arvesse läheb ka intsident, mis sellist kahju üksnes võinuks põhjustada. Teavitage oma CSIRTi või pädevat asutust: varajane hoiatus 24 tunni jooksul teadasaamisest, märkides, kas kahtlustatakse ebaseaduslikku või pahatahtlikku tegevust ja kas võib olla piiriülene mõju; intsidenditeade 72 tunni jooksul teadasaamisest koos esialgse tõsiduse ja mõju hinnanguga ning olemasolevate rikkeindikaatoritega; vahearuanne, kui seda küsitakse; ja lõpparuanne ühe kuu jooksul 72 tunni teatest. Kui intsident lõpparuande tähtajaks veel kestab, esitage siis vahearuanne ja lõpparuanne ühe kuu jooksul pärast selle käsitlemise lõpetamist.
Millal: Nii 24 kui ka 72 tunni tähtaeg algab teadasaamisest, need ei ole seega järjestikused — 72 tunni teade ei ole „72 tundi pärast varajast hoiatust“. Lõpparuande ühekuune tähtaeg algab 72 tunni teate esitamisest. Usaldusteenuse osutajal on oma usaldusteenuseid mõjutavate intsidentide puhul aega 24, mitte 72 tundi.
Milline on tõend
- Intsidendimenetlus, mis sätestab 24 h / 72 h / ühe kuu tähtajad ja kummagi eest vastutaja
- Intsidendilogi, mis märgib teadasaamise aja, mitte üksnes avastamise aja
- Riikliku CSIRTi juures registreeritud nimeline kontaktisik
- Esitatud varajaste hoiatuste, teadete ja lõpparuannete koopiad
Jurisdiktsioonis Ukraina
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.
Millal: 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.
Tekib, kui
- The service is delivered through information and communication systems
- Systems processing state information resources report every incident
Milline on tõend
- 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
Jurisdiktsioonis Saksamaa
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.
Millal: 24 hours, then 72 hours, then one month from the 72-hour notification. Encode and diary "one month", never "30 days".
Milline on tõend
- 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
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.
Millal: Same deadlines as the ordinary report — the additional content is due with each filing.
Tekib, kui
- The KRITIS duty overlay: five duties that size alone never triggers
Milline on tõend
- A reporting template with fields for installation type, critical service and service impact
- A current mapping of installations to the critical services they support
Jurisdiktsioonis Poola
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.
Millal: 24 hours / 72 hours / one month, each running from detection. Trust service providers: 24 hours for the notification limb.
Milline on tõend
- 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
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.
Millal: Applies from 3 April 2026 until, sector by sector, the operational-capability communiqué is published. Re-check before every filing.
Milline on tõend
- A dated note of the last check of your competent authority’s official journal, with the recipient it resolved to
Jurisdiktsioonis Tšehhi
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.
Millal: 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.
Milline on tõend
- 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
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.
Millal: 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.
Milline on tõend
- 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
Jurisdiktsioonis Eesti
Teavitage RIA-t ahelas 24 tundi, 72 tundi ja üks kuu
Esmane teade 24 tunni jooksul teadasaamisest; intsidenditeade 72 tunni jooksul, usaldusteenuse osutajal 24 tunni jooksul; vahearuanne, kui RIA seda küsib; ja lõpparuanne ühe kuu jooksul 72 tunni intsidenditeate esitamisest. Kui intsident ei ole selleks ajaks lahendatud, loetakse see aruanne vahearuandeks ja uus lõpparuanne tuleb esitada ühe kuu jooksul pärast lahendamist. Kõik teated lähevad RIA-le: „CERT-EE“ ei esine KüTSis üldse, nii et ärge otsige CERT-EE ega NCSC portaali, kuhu esitada.
Millal: Lõpparuande ühekuune tähtaeg algab 72 tunni intsidenditeate esitamisest, mitte intsidendist. Kui intsident on sel hetkel veel lahendamata, algab kuu uuesti lahendamisest.
Milline on tõend
- Intsidendimenetlus, mis nimetab saajaks RIA ja sätestab 24 h / 72 h / ühe kuu sammud
- Intsidendilogi, mis märgib teadasaamise aja, mitte üksnes avastamise aja
- Koopiad tegelikult esitatud teadetest koos esitamise ajatemplitega
Tagage, et teie süsteemi käitav isik teavitab teid 24 tunni jooksul
Kui annate teenuse osutamiseks kasutatava võrgu- või infosüsteemi teise isiku hallata või majutate seda teise isiku juures, vastutate selle eest, et see isik teavitaks teid 24 tunni jooksul. See on tarneahela edasikandekohustus, millel direktiivis vastet ei ole: tähtaeg ei liigu teie tarnijale, ja vastutus teavitusahela eest jääb teile.
Millal: Kakskümmend neli tundi, jooksmisega teie poole, mitte RIA poole. Teie enda KüTSi § 8 tähtajad jooksevad sellele lisaks.
Tekib, kui
- Süsteem on antud teise isiku hallata või majutatud teise isiku juures
Milline on tõend
- Lepinguline teavitusklausel, milles on 24 tunni tähtaeg kirjas
- Loetelu allhanke- ja majutusteenuse osutajatest, keda kohustus puudutab
- Tõend, et teavitustee on vähemalt korra läbi proovitud
Jurisdiktsioonis Itaalia
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*.
Millal: 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.
Tekib, kui
- 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
Milline on tõend
- 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