Incident Management
From event to regulator, on one record.
Capture, categorise and track incidents, report them on time, and export what the regulator asks for, against the same risks and controls the rest of the platform already holds.
On the record
Four things the module does, and nothing it pretends to.
Select a station to see what the record carries there. Sastrum records and reports incidents; it does not run your response for you.
01Capture
The incident is recorded as a register entry rather than an email thread.
On capture
- Incident register entry
Module structure verified in the application, 18 Sep 2026. Empty in the reviewed tenant.
Operational, not isolated
An incident is never a dead end.
The register sits on the same foundation as everything else, so an incident points back at what it affected and forward at who is doing something about it.
- Risks and controlsIncidents link to the risks they realised and the controls that were meant to stop them.
- Task ManagementActions raised from an incident are tracked in the same workspace as every other task.
- Audit trailEvery recorded change is filterable by module, event, actor and date.
- Treatment plansAdd-onRisk treatment plans sit in the Assurance add-on, licensed per tenant.
Record it once, report it on time.
The demo opens the incident register beside the risks and controls it points at, and the export the regulator receives.