AI Incident Commander
An AI-driven data exposure is live and the clock is running: regulators, customers, legal, engineering and the board all want something different. Run the incident — decide, communicate and document under pressure.
SEV1 — 'AI assistant disclosed customer records to a third party'
Incident commander
Legal
Privacy
Comms
Engineering lead
120 minutes · expert
Execution trace
00:00:00alertDLP
Customer records posted to an external endpoint
Confirmed egress, volume still unknown.
00:05:00enterpriseengineering
attack step
Engineer restarts the service to 'clear it'
In-memory trace context is lost.
00:15:00enterprisecomms
attack step
Two conflicting statements circulate
Sales tells customers one thing, support another.
01:00:00policylegal
attack step
72-hour clock started at first awareness
Scope still unknown, deadline already running.