8 controls
130 frameworks share controls with it
North America
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
NERC CIP Evidence & Implementation Kit
8 controls is the documentation set somebody has to write. This is that set,
already written: an adopt-ready artifact for every control in policy and procedure text you
edit rather than draft, and the evidence checklist an auditor asks for against each.
See what is in it, $249
The same set every buyer of this kit receives. Nothing here is produced on request.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
Every control
| Code | Control | Also in |
|---|
NERCCIP-1 | BES Cyber System Categorization and Security Management Controls (CIP-002 + CIP-003) | 0 |
NERCCIP-2 | Personnel and Training (CIP-004) | 0 |
NERCCIP-3 | Electronic Security Perimeters + Control Center Communications (CIP-005 + CIP-012) | 0 |
NERCCIP-4 | Physical Security of BES Cyber Systems + Transmission Stations (CIP-006 + CIP-014) | 0 |
NERCCIP-5 | System Security Management + Configuration Change Management and Vulnerability Assessments (CIP-007 + CIP-010) | 110 |
NERCCIP-6 | Incident Reporting and Response Planning + Recovery Plans (CIP-008 + CIP-009) | 66 |
NERCCIP-7 | BES Cyber System Information Protection (CIP-011) | 0 |
NERCCIP-8 | Supply Chain Risk Management (CIP-013) | 40 |
Tell me when NERC CIP files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What an auditor will ask you to produce
The artefacts named on the failure modes this framework speaks to.
- Patch management records and SLAs
- Privileged administration procedures
- Backup and restoration test records
- Evidence demonstrating: Patches, updates or other vendor mitigations for vulnerabilities in operating sy
- Evidence demonstrating: A vulnerability scanner is used at least fortnightly to identify missing patches
- Evidence demonstrating: Patches, updates or other vendor mitigations for vulnerabilities in office produ
How programmes fail on this
Failure modes named by this framework and others. Each opens the full record.
What this page is
A control-level reference for NERC CIP, drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition