NERC CIP Audit Evidence Management demo

Audit binders built each night, ahead of the audit request. 1:13

What the demo shows

A workflow solution for CIP teams that assembles and checks audit evidence by requirement.

One binder tab per CIP requirement, filled each night from the source systems. Each piece of evidence is read against the requirement's own words: the 35-day clock, the assets in scope, the signature. On the CIP-007 R2 tab most phrases are met; the missing patch record for two substation gateways is named, and a request is drafted to the asset owner. The compliance manager sends it, and the CIP Senior Manager signs the submission.

Transcript

  1. NERC CIP Audit Evidence Management builds the CIP Audit Binder, one requirement at a time.
  2. Today, proof sits in a dozen systems, and gaps surface only when the auditor samples.
  3. Every night, agents read each record against the requirement's own words.
  4. On Lumina's CIP-007 R2 tab, seven of eight checks are met, each with its evidence.
  5. One is missing. The Kestrel Hill gateway patch record due by the 8th of September.
  6. A request is already drafted to Tomas, the asset owner.
  7. Marianas sends it. The clocks show three years of patch cycles, so Amis shows the next day.
  8. Readiness is 89%, and every open gap has an owner and a date.
  9. Built on Botminds: agents, data, screens, and governance on one platform.

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