What the demo shows
A search solution for OT responders that answers from playbooks, diagrams and reporting rules.
A responder types what is happening in plain words, and the plan's own playbook opens as a decision tree at the step they are on, each instruction quoted from its page. Every branch they answer moves the tree and writes the timeline; the zone drawing shows which firewall rule to apply and how many customers sit behind each RTU; the contact finder names the vendor's security line and clause. The reporting clock is chosen by the incident's facts: when the incident commander determines a Reportable Cyber Security Incident, the 1-hour CIP-008 clock starts on screen with the notification already drafted and cited. Agents never touch a control system; the incident commander decides every branch and signs.
Transcript
- OT Incident Response answers OT responders from their own playbooks, drawings, and reporting rules.
- At 3 a.m., the right step sits in a binder, while a 1-hour reporting clock may already run.
- Sam asks, suspicious traffic on the SCADA network?
- The playbook opens at Step 1, clock running.
- Each answer moves the tree.
- Source not approved. Control of the grid not affected.
- Contained at the ConWit.
- One firewall rule and 18,400 customers stay on supply.
- At 3.41, Alana determines it reportable.
- The rules swap the clock.
- Notify within one hour.
- The notice is drafted from the timeline.
- Signed at 4.02.
- Inside the hour, 39 minutes to spare.
- Built on Botminds: agents, data, screens, and governance on one platform.
Transcribed from the film’s narration. Captions are on the player.