Meldung eines erheblichen Sicherheitsvorfalls
Verglichen über 7 Jurisdiktionen
In Europäische Union (NIS2-Basis)
Erhebliche Sicherheitsvorfälle in der Kette 24 Stunden, 72 Stunden, ein Monat melden
Ein Sicherheitsvorfall ist erheblich, wenn er schwerwiegende Betriebsstörungen oder finanzielle Verluste für Sie verursacht hat oder verursachen kann, oder wenn er andere durch erhebliche materielle oder immaterielle Schäden beeinträchtigt hat oder beeinträchtigen kann. Jede der beiden Varianten genügt, und ein Vorfall, der solchen Schaden lediglich verursachen konnte, zählt ebenfalls. Unterrichten Sie Ihr CSIRT oder die zuständige Behörde: eine Frühwarnung binnen 24 Stunden nach Kenntnisnahme mit der Angabe, ob rechtswidrige oder böswillige Handlungen vermutet werden und ob grenzüberschreitende Auswirkungen möglich sind; eine Meldung über den Sicherheitsvorfall binnen 72 Stunden nach Kenntnisnahme mit einer ersten Bewertung von Schweregrad und Auswirkungen sowie etwaigen Kompromittierungsindikatoren; auf Anfrage einen Zwischenbericht; und einen Abschlussbericht binnen eines Monats nach der 72-Stunden-Meldung. Dauert der Vorfall bei Fälligkeit des Abschlussberichts noch an, legen Sie zu diesem Zeitpunkt einen Fortschrittsbericht vor und den Abschlussbericht binnen eines Monats nach Abschluss Ihrer Bearbeitung.
Wann: Die 24- und die 72-Stunden-Frist laufen beide ab Kenntnisnahme, sie sind also nicht aufeinanderfolgend — die 72-Stunden-Meldung ist nicht „72 Stunden nach der Frühwarnung“. Die Monatsfrist für den Abschlussbericht läuft ab Übermittlung der 72-Stunden-Meldung. Ein Vertrauensdiensteanbieter hat für Vorfälle, die seine Vertrauensdienste betreffen, 24 Stunden, nicht 72.
Wie ein Nachweis aussieht
- Ein Vorfallverfahren, das die Fristen 24 h / 72 h / ein Monat und die jeweils Verantwortlichen benennt
- Ein Vorfallprotokoll, das den Zeitpunkt der Kenntnisnahme festhält, nicht nur den der Entdeckung
- Eine beim nationalen CSIRT registrierte, namentlich benannte Kontaktperson
- Kopien der übermittelten Frühwarnungen, Meldungen und Abschlussberichte
In 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.
Wann: 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.
Entsteht, wenn
- The service is delivered through information and communication systems
- Systems processing state information resources report every incident
Wie ein Nachweis aussieht
- 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
In Deutschland
Meldung an die gemeinsame Meldestelle von BSI und BBK nach dem Muster 24 Stunden, 72 Stunden, ein Monat
Erstmeldung innerhalb von 24 Stunden, Meldung innerhalb von 72 Stunden, Zwischenmeldung auf Anforderung und Abschlussmeldung innerhalb eines Monats. Dauert der Vorfall nach Ablauf des Monats noch an, ist zu diesem Zeitpunkt eine Fortschrittsmeldung und einen Monat nach Abschluss der Bearbeitung die Abschlussmeldung zu erstatten. Zwei deutsche Besonderheiten: Adressat ist die gemeinsame Meldestelle von BSI und BBK, nicht das BSI allein, und das Gesetz sagt „einen Monat“ — nicht 30 Tage. In einem Monat mit 31 Tagen ist das ein echter Tag Unterschied.
Wann: 24 Stunden, dann 72 Stunden, dann ein Monat ab der 72-Stunden-Meldung. Fristenkalender auf „einen Monat“ führen, nie auf „30 Tage“.
Wie ein Nachweis aussieht
- Melde- und Reaktionsprozess, der die gemeinsame Meldestelle von BSI und BBK als Adressat benennt
- Vorfallprotokoll mit dem Zeitpunkt der Kenntniserlangung, nicht nur der Detektion
- Kopien der abgegebenen Erst-, 72-Stunden- und Abschlussmeldung
Betreiber kritischer Anlagen übermitteln in jeder Meldung drei zusätzliche Angaben
Zusätzlich zum allgemeinen Meldeinhalt übermittelt der Betreiber einer kritischen Anlage die Art der betroffenen Anlage, die betroffene kritische Dienstleistung und die Auswirkungen auf diese Dienstleistung. Das ist ein Inhalts-, kein Fristenthema: Es gilt dieselbe Kette aus 24 Stunden, 72 Stunden und einem Monat.
Wann: Dieselben Fristen wie bei der allgemeinen Meldung — die Zusatzangaben sind mit jeder Meldung fällig.
Entsteht, wenn
- Das KRITIS-Pflichtenpaket: fünf Pflichten, die Größe allein nie auslöst
Wie ein Nachweis aussieht
- Meldevorlage mit Feldern für Anlagenart, kritische Dienstleistung und Auswirkungen
- Aktuelle Zuordnung der Anlagen zu den von ihnen getragenen kritischen Dienstleistungen
In Polen
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.
Wann: 24 hours / 72 hours / one month, each running from detection. Trust service providers: 24 hours for the notification limb.
Wie ein Nachweis aussieht
- 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.
Wann: Applies from 3 April 2026 until, sector by sector, the operational-capability communiqué is published. Re-check before every filing.
Wie ein Nachweis aussieht
- A dated note of the last check of your competent authority’s official journal, with the recipient it resolved to
In Tschechien
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.
Wann: 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.
Wie ein Nachweis aussieht
- 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.
Wann: 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.
Wie ein Nachweis aussieht
- 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
In Estland
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.
Wann: 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.
Wie ein Nachweis aussieht
- 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
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.
Wann: Twenty-four hours, running to you rather than to RIA. Your own KüTS § 8 deadlines then run on top of it.
Entsteht, wenn
- The system is outsourced to, or hosted by, another person
Wie ein Nachweis aussieht
- 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
In Italien
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*.
Wann: 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.
Entsteht, wenn
- 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
Wie ein Nachweis aussieht
- 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