NERC CIP evidence retention: how long to keep what, and why three years is not the whole answer
NERC CIP evidence retention: the three-calendar-year rule, longer holds after a violation, the 90-day CIP-007 log rule, and the gap since your last audit.
Every NERC CIP standard ends with a short compliance section, and inside it is a paragraph most people skim: Evidence Retention. It decides how long your records have to exist, and getting it wrong is a quiet way to fail an audit even when the work itself was done.
This post covers what that paragraph says, the one place where a requirement sets its own clock (CIP-007 event logs), and the gap that catches people out: the time since your last audit.
The rule written into each CIP standard
The wording is nearly identical across CIP-003-9, CIP-004-7, CIP-007-6 and CIP-012-2. Each standard says the entity must retain evidence of each requirement in the standard for three calendar years, unless its Compliance Enforcement Authority (CEA, usually your Regional Entity) directs it to keep specific evidence longer as part of an investigation.
Two more sentences follow, and both matter:
- If you are found non-compliant, you keep the information related to that non-compliance until mitigation is complete and approved, or for the three calendar years, whichever is longer.
- The CEA keeps the last audit records and everything requested and submitted since. The auditor will have your previous submission to compare against.
Why three years is not the whole answer
The same section opens with a sentence that changes how to read the rule: where the retention period is shorter than the time since the last audit, the CEA may ask for other evidence to show you were compliant for the full period since that audit.
So the practical question is not only how long a record must be kept, but whether you can show compliance for every day since your last audit. If your audits are more than three years apart, records you were allowed to discard may still be the easiest way to answer that. Many programs keep CIP evidence at least back to the last audit for this reason.
Where a requirement sets its own clock: CIP-007 event logs
CIP-007-6 Part 4.3 is about keeping operational data, not proving a process ran. For high impact BES Cyber Systems, and medium impact BES Cyber Systems at Control Centers, with their associated EACMS, PACS and PCAs, it requires you, where technically feasible, to retain the event logs identified in Part 4.1 for at least the last 90 consecutive calendar days, except under CIP Exceptional Circumstances.
These are two separate obligations. The logs themselves must cover a rolling 90 days. The evidence that you did this falls under the three-calendar-year rule like everything else.
What to keep, by kind of record
- Approvals and plans: CIP-003 policies and CIP Senior Manager approvals, the low impact cyber security plan, CIP-012 plans. Keep each version with its approval date, not only the current one.
- Recurring activities: training completion and access reviews (CIP-004), patch evaluations at least once every 35 calendar days (CIP-007 R2), baseline and change records (CIP-010). Keep the dated record of each cycle, because auditors sample across the period.
- Event-driven records: access revocations, incident response, CIP Exceptional Circumstances. Keep the trigger, the timestamps and what was done.
- Operational data with its own clock: CIP-007 event logs for at least 90 consecutive days where Part 4.3 applies.
Common ways retention goes wrong
- A ticketing or logging system with a default purge shorter than the retention you need.
- Only the current policy kept, so the auditor cannot see what was approved, and when, during the audit period.
- Evidence held by a contractor or vendor and lost when the contract changes.
- Screenshots with no date or source system, which prove little on their own.
General guidance, not legal or compliance advice. The Evidence Retention section of each standard, and your Regional Entity, are authoritative.