Incident Centre · Preview
One incident, every clock you adopted, and a person files.
Report an incident once, confirm the domains in scope, and see its obligations before the record exists. The clock for each clause you adopted runs from awareness, the notification is drafted against the clause, and the incident owner files it. The Incident Centre is in preview in the app.
Ransomware on shared file servers
Incident Centre · reported 06:40
NIS2 early warning clock
24 h left
Ready
Step 1 of 6
DraftIncident reported
Shared file servers are encrypted and a ransom note is found. The responder reports it through the incident intake.
Elin Dahl, security operations
Log
Nothing logged yet
Six steps inside the 24 hour clock. Tomas Varga, CISO and incident owner, reviews the early warning, files it with the authority and records the reference. Nothing is filed until Tomas decides.
Scripted demo with fictional data. Agents draft, and a named person reviews every step before anything is final.
01 · How it works
Two mechanisms behind the clock
The engine computes when a notification is due. A person decides whether to notify, and files.
Obligation engine
Clocks from the clauses you adopted
Each adopted clause starts its own clock from its anchor, here awareness. Under NIS2 the early warning is due 24 hours from awareness and the incident notification 72 hours from awareness, side by side on the incident. Clocks run only for clauses your organisation adopted.
- NIS2 early warning, from awareness
- 24h
Notification drafts
Drafted against the clause, filed by a person
The notification is drafted from what the clause requires and cites it. A draft with weak grounding or no anchored citation is forced into human review. Nothing is sent from the platform: the incident owner, who holds the notify permission, files it and records the reference.
