Skip to main content

Guide

NIS2 reporting deadlines: Plan reminders with a reliable starting point

Design NIS2 reminders: distinguish awareness, classification, ownership and submission evidence. Includes a failure test.

NIS2 reporting deadlines: Plan reminders with a reliable starting point
Julian Köhn
|Read time: 3 minutes

A reminder can be timely only if its starting point is correct. An arbitrary ticket timestamp is not automatically suitable. Technical detection, substantive assessment and awareness of a significant security incident may occur at different times.

Plan an external reminder workflow with a documented deadline anchor, deputies and failure tests. Regulatory submission remains a separate step; this guide does not assume a built-in Kopexa NIS2 timer.

Document the relevant time

Under the general notification obligations in section 32 BSIG, the early warning must be made without undue delay and no later than 24 hours after becoming aware of a significant security incident. The subsequent notification follows no later than 72 hours after the same awareness point. Check sector-specific provisions first.

Store event time, detection time and substantively confirmed awareness time separately. Record who made the classification and the information supporting it. A later correction must not hide the original state.

Put internal deadlines before the outer limit

A reminder immediately before expiry leaves little time for review and submission. Define internal preparation and escalation dates. Their intervals depend on on-call coverage and the reporting procedure; they are not additional statutory deadlines.

Name the responsible role and deputy. Notification must also work when the owner is absent or the normal communication system is affected.

Distinguish reminders, handling and submission

StatusWhat it actually means
Dispatch acceptedThe notification channel accepted the message for delivery
Handling acknowledgedA responsible person is working on the case
Report submittedTransmission was carried out
Receipt confirmedConfirmation from the designated reporting route is available

No state may silently substitute for the next. A green automation log does not prove a regulator received a report.

A fictional test for your workflow

An incident is classified in the evening; more information arrives later. Check that reminders use the same incident ID, time calculation remains stable and a deputy can act. Also test duplicate triggers, a missing recipient and an unavailable delivery service.

Use unambiguous timestamps with time zones in integrations. Daylight saving changes and local display must not lose an hour. Log retries without unnecessarily distributing sensitive incident data.

Test failure of the reminder route too

If the incident affects normal IT, the planned notification channel may fail too. Define how on-call staff can identify and take over the case independently of that primary route. A second message in the same disrupted system is not independent escalation.

Record dispatch and confirmed ownership by a responsible role. If acknowledgement is absent, the agreed fallback must apply. Set escalation intervals for your operation; they do not extend statutory maximum deadlines.

A correction must not secretly restart the clock

If the substantive classification changes, preserve the original time, new assessment and reasoning. Editing a ticket must not reset the deadline anchor to “last modified”.

Test this explicitly with the responsible specialist function. The technical workflow should submit changes for review and preserve traceability of the existing calculation. The scheduler does not decide the legal consequences of new information.

Ongoing operation also needs an owner for token expiry, failed runs and changes to underlying rules. Reminders become dependable support once the business process and failure routes have been tested.

Connect the workflow to incident management

Incident management provides roles and workflows. An incident exercise tests them under disruption. Then assess which API fields and actions are available for external automation. The substantive notification decision remains explicit.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

Does the statutory deadline always start when a ticket is created?

No. The relevant point is awareness or classification as defined in the applicable rules. A ticket may be created earlier or later.

Sources

  1. BSIG section 32: Reporting obligations — Bundesministerium der Justiz [Accessed ]
  2. BSIG section 28: Scope — Bundesministerium der Justiz [Accessed ]