OT Patch Management demo

What the demo shows

A workflow solution for OT engineers that tracks every patch evaluation against its deadline.

Six agents check each patch source every morning, match each supplier notice to the Cyber Assets by model and firmware, draft the applicability decision with the sentence that proves it, fit installs to the next outage and, when an install cannot beat the deadline, fill the mitigation plan template. Each patch is a bead on a 35-day clock; at day 31 it turns red. The OT engineer signs, the CIP Senior Manager's delegate approves extensions, and each date is logged as evidence.

Transcript

1. 0:00OT Patch Management gives every control system patch a 35-day clock for OT engineers.
2. 0:10CIP-007 allows 35 days to evaluate, then 35 to install or plan.
3. 0:20Each patch is a bead, the inner ring to evaluate, the outer to act.
4. 0:27Today, a Halvard RTU notice reaches day 31 unevaluated.
5. 0:32It turns red. Agents check the inventory.
6. 0:3711 RTUs affected. 7 fit outages.
7. 0:40Core veins 4 do not.
8. 0:44The mitigation plan template opens.
9. 0:46Filled in. Web interface off.
10. 0:49Port blocked. Nor signs on day zero, with all 35 days to spare.
11. 0:57Every asset model is checked for a patch source, so nothing goes unwatched.
12. 1:04Built on Botminds: agents, data, screens, and governance on one platform.

Transcribed from the film’s narration. Captions are on the player.