Track a filing after you submit it

On the reporting platform a notification is Submitted, then the coordinating CSIRT marks it Valid or Invalid, and it is eventually Closed. The commonest reason for invalid is a report sent to the wrong coordinating CSIRT. The platform has no API, so Declara records each change as you tell it, dated, with what the CSIRT said.

Before you start

• A stage recorded as submitted.
• cases.submit permission.

Steps

1. Open the case and the filed stage. Under it, On the platform shows the current status.
2. When the CSIRT acts, record it: Marked valid, Marked invalid (copy in the CSIRT's note, which is required), or Closed.
3. If it was marked invalid, correct the notification on the platform. It stays editable there until the final report is submitted. Then write what you corrected and press Record the correction. The status returns to Submitted.

What you should see

An invalid filing raises a banner at the top of the case until it is corrected. Every change is a case event and an audit entry, and the evidence pack shows each stage's platform status and the CSIRT's note.

The filed stage itself never changes: what was filed stays exactly as it was filed.

The platform's own 72-hour deadline

Once the early warning is filed, the platform shows the notification as due 48 hours after the early warning was submitted. ENISA calls this a known error (FAQ 26). The legal deadline is 72 hours from when you became aware (Art. 14(2)(b), 14(4)(b)). The case timeline shows both, labelled Platform shows beside the legal one, so a filer comparing screens is not alarmed. Reminders and overdue states follow the law only.

Related

• File the 72-hour notification
• Why your reporting clock works the way it does