INC-20261111-EF2C

• Early warningArticle 14(4)(a)

  Submitted
  filed 2026-11-12 12:13:57 UTC

  Within 24 hours of becoming aware, stating whether the incident is suspected of being caused by unlawful or malicious acts.

• Incident notificationArticle 14(4)(b)

  Running falls at a weekend
  in 31h due 2026-11-14 18:13:57 UTC

  Within 72 hours of becoming aware of the incident. · Draft it

• Final reportArticle 14(4)(c)

  Not started
  — starts on submitting the notification

  Within one month after the submission of the incident notification — counted from when you actually submitted it, not from the 72-hour deadline. · Draft it

• Early warningArticle 23(4)(a)

  Submitted
  filed 2026-11-12 13:13:57 UTC

  Within 24 hours of becoming aware of the significant incident.

• Incident notificationArticle 23(4)(b)

  Running falls at a weekend
  in 31h due 2026-11-14 18:13:57 UTC

  Within 72 hours of becoming aware, updating the early warning with an initial assessment. · Draft it

• Intermediate reportArticle 23(4)(c)

  Not requested
  — no deadline until they ask

  Only upon the request of the CSIRT or competent authority. No deadline until they ask.

• Final reportArticle 23(4)(d)

  Not started
  — starts on submitting the notification

  Not later than one month after the submission of the incident notification. · Draft it

• Final report after handlingArticle 23(4)(e)

  Not started
  — starts on the handling being completed

  Where the incident is still ongoing at the one-month point, a progress report is due then and the final report within one month of the handling being completed. · Draft it

Nothing attached. Screenshots of the portal acknowledgment, the sent notification, and the technical analysis live here.