Cybersecurity Contract Clause Review demo
Cyber clauses agreed before an OT contract is signed. 1:14
What the demo shows
A workflow solution for procurement teams that checks vendor contracts for cyber terms.
The vendor's contract opens as a document with the utility's required cyber clauses ticked off in a rail beside it: met, weak or missing. The vendor's changes are struck through and the utility's redline is written in for every gap, each with a margin note quoting what the draft says. For each flagged clause a fallback ladder shows the preferred wording, the pre-approved fallbacks and the never-sign line, with how often each was accepted in past negotiations and whether this vendor signed it before. Clicking a rung rewrites the redline and changes who must approve. The procurement officer accepts, the security lead and counsel approve fallbacks, and every round is logged as CIP-013 evidence.
Transcript
- Cybersecurity Contract Clause Review checks vendor contracts for the cyber terms control systems need.
- Today, counsel reads every redline by hand, and a deleted clause slips through.
- Halvorsen's redline for 38 substations just arrived.
- Six agents checked 16 clauses.
- Nine meet the standard.
- For a week, three are missing.
- Incident notification was deleted.
- The agents proposed the 72 22-hour fallback, with a 24-hour early alert.
- Halvorsen signed that wording in 2024.
- Seven of nine vendors accepted it.
- Grace accepts all seven.
- The approvers sign off, and round three goes back by mid-morning.
- Every round is logged as CIP.
- 013 evidence, control by control.
- Built on Botminds: agents, data, screens, and governance on one platform.
Transcribed from the film’s narration. Captions are on the player.