North America (United States under FERC; Canadian provinces by adoption)

NERC CIP

211 controls. 128 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

211 controls 128 frameworks share controls with it North America (United States under FERC; Canadian provinces by adoption) 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

211 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

CodeControlAlso in
NERCCIP-1BES Cyber System Categorization and Security Management Controls (CIP-002 + CIP-003)0
NERCCIP-2Personnel and Training (CIP-004)0
NERCCIP-3Electronic Security Perimeters + Control Center Communications (CIP-005 + CIP-012)0
NERCCIP-4Physical Security of BES Cyber Systems + Transmission Stations (CIP-006 + CIP-014)0
NERCCIP-5System Security Management + Configuration Change Management and Vulnerability Assessments (CIP-007 + CIP-010)107
NERCCIP-6Incident Reporting and Response Planning + Recovery Plans (CIP-008 + CIP-009)66
NERCCIP-7BES Cyber System Information Protection (CIP-011)0
NERCCIP-8Supply Chain Risk Management (CIP-013)39
CIP-002 R1CIP-002-5.1a R10
CIP-002 R1.1CIP-002-5.1a R1.1: Identify high impact BES Cyber Systems0
CIP-002 R1.2CIP-002-5.1a R1.2: Identify medium impact BES Cyber Systems0
CIP-002 R1.3CIP-002-5.1a R1.3: Identify assets containing low impact BES Cyber Systems0
CIP-002 R2CIP-002-5.1a R20
CIP-002 R2.1CIP-002-5.1a R2.1: Review the identifications at least every 15 calendar months0
CIP-002 R2.2CIP-002-5.1a R2.2: CIP Senior Manager approval of the identifications every 15 calendar months0
CIP-003 R1CIP-003-9 R10
CIP-003 R1.1CIP-003-9 R1.1: Cyber security policies for high and medium impact systems0
CIP-003 R1.2CIP-003-9 R1.2: Cyber security policies for assets containing low impact systems0
CIP-003 R2CIP-003-9 R20
CIP-003 R2 Att1 S1CIP-003-9 R2 Att1 S1: Low impact plan Section 1: cyber security awareness0
CIP-003 R2 Att1 S2CIP-003-9 R2 Att1 S2: Low impact plan Section 2: physical security controls0
CIP-003 R2 Att1 S3CIP-003-9 R2 Att1 S3: Low impact plan Section 3: electronic access controls0
CIP-003 R2 Att1 S4CIP-003-9 R2 Att1 S4: Low impact plan Section 4: Cyber Security Incident response0
CIP-003 R2 Att1 S5CIP-003-9 R2 Att1 S5: Low impact plan Section 5: Transient Cyber Asset and Removable Media malicious code mitigation0
CIP-003 R2 Att1 S6CIP-003-9 R2 Att1 S6: Low impact plan Section 6: vendor electronic remote access security controls0
CIP-003 R3CIP-003-9 R3: Identify the CIP Senior Manager by name0
CIP-003 R4CIP-003-9 R4: Documented delegation of CIP Senior Manager authority0
CIP-004 R1CIP-004-7 R10
CIP-004 R1.1CIP-004-7 R1.1: Quarterly security awareness reinforcement0
CIP-004 R2CIP-004-7 R20
CIP-004 R2.1CIP-004-7 R2.1: Cyber security training content0
CIP-004 R2.2CIP-004-7 R2.2: Training before access is granted0
CIP-004 R2.3CIP-004-7 R2.3: Training at least every 15 calendar months0
CIP-004 R3CIP-004-7 R30
CIP-004 R3.1CIP-004-7 R3.1: Personnel risk assessment: confirm identity0
CIP-004 R3.2CIP-004-7 R3.2: Personnel risk assessment: seven-year criminal history records check0
CIP-004 R3.3CIP-004-7 R3.3: Criteria to evaluate criminal history records checks0
CIP-004 R3.4CIP-004-7 R3.4: Verify contractor and vendor personnel risk assessments0
CIP-004 R3.5CIP-004-7 R3.5: Personnel risk assessment within the last seven years0
CIP-004 R4CIP-004-7 R40
CIP-004 R4.1CIP-004-7 R4.1: Authorize access based on need0
CIP-004 R4.2CIP-004-7 R4.2: Quarterly verification of access against authorization0
CIP-004 R4.3CIP-004-7 R4.3: Verify user accounts and privileges every 15 calendar months0
CIP-004 R5CIP-004-7 R50
CIP-004 R5.1CIP-004-7 R5.1: Remove access within 24 hours of a termination action0
CIP-004 R5.2CIP-004-7 R5.2: Revoke unneeded access on reassignment or transfer0
CIP-004 R5.3CIP-004-7 R5.3: Revoke non-shared accounts within 30 days of termination0
CIP-004 R5.4CIP-004-7 R5.4: Change shared account passwords after termination or transfer0
CIP-004 R6CIP-004-7 R60
CIP-004 R6.1CIP-004-7 R6.1: Authorize provisioned access to BCSI0
CIP-004 R6.2CIP-004-7 R6.2: Verify provisioned BCSI access every 15 calendar months0
CIP-004 R6.3CIP-004-7 R6.3: Remove BCSI access by the next calendar day after termination0
CIP-005 R1CIP-005-7 R10
CIP-005 R1.1CIP-005-7 R1.1: All routable Cyber Assets inside a defined ESP0
CIP-005 R1.2CIP-005-7 R1.2: External Routable Connectivity through an identified EAP0
CIP-005 R1.3CIP-005-7 R1.3: Inbound and outbound permissions with reasons, deny by default0
CIP-005 R1.4CIP-005-7 R1.4: Authenticate Dial-up Connectivity0
CIP-005 R1.5CIP-005-7 R1.5: Detect malicious communications at EAPs0
CIP-005 R2CIP-005-7 R20
CIP-005 R2.1CIP-005-7 R2.1: Interactive Remote Access through an Intermediate System0
CIP-005 R2.2CIP-005-7 R2.2: Encryption of Interactive Remote Access terminating at the Intermediate System0
CIP-005 R2.3CIP-005-7 R2.3: Multi-factor authentication for Interactive Remote Access0
CIP-005 R2.4CIP-005-7 R2.4: Determine active vendor remote access sessions0
CIP-005 R2.5CIP-005-7 R2.5: Disable active vendor remote access0
CIP-005 R3CIP-005-7 R30
CIP-005 R3.1CIP-005-7 R3.1: Determine authenticated vendor-initiated connections to EACMS and PACS0
CIP-005 R3.2CIP-005-7 R3.2: Terminate vendor-initiated connections to EACMS and PACS and control reconnection0
CIP-006 R1CIP-006-6 R10
CIP-006 R1.1CIP-006-6 R1.1: Operational or procedural controls to restrict physical access0
CIP-006 R1.10CIP-006-6 R1.10: Protect cabling outside a PSP within the same ESP0
CIP-006 R1.2CIP-006-6 R1.2: At least one physical access control into each PSP0
CIP-006 R1.3CIP-006-6 R1.3: Two or more physical access controls for high impact PSPs0
CIP-006 R1.4CIP-006-6 R1.4: Monitor for unauthorized physical access into PSPs0
CIP-006 R1.5CIP-006-6 R1.5: Alarm within 15 minutes of detected unauthorized PSP access0
CIP-006 R1.6CIP-006-6 R1.6: Monitor PACS for unauthorized physical access0
CIP-006 R1.7CIP-006-6 R1.7: Alarm within 15 minutes of unauthorized PACS access0
CIP-006 R1.8CIP-006-6 R1.8: Log entry of each authorized individual into each PSP0
CIP-006 R1.9CIP-006-6 R1.9: Retain physical access logs for 90 days0
CIP-006 R2CIP-006-6 R20
CIP-006 R2.1CIP-006-6 R2.1: Continuous escort of visitors within PSPs0
CIP-006 R2.2CIP-006-6 R2.2: Log visitor entry and exit0
CIP-006 R2.3CIP-006-6 R2.3: Retain visitor logs for 90 days0
CIP-006 R3CIP-006-6 R30
CIP-006 R3.1CIP-006-6 R3.1: Maintain and test PACS and PSP devices every 24 months0
CIP-007 R1CIP-007-6 R10
CIP-007 R1.1CIP-007-6 R1.1: Enable only needed logical network ports0
CIP-007 R1.2CIP-007-6 R1.2: Protect unnecessary physical input/output ports0
CIP-007 R2CIP-007-6 R20
CIP-007 R2.1CIP-007-6 R2.1: Patch management process with tracked sources0
CIP-007 R2.2CIP-007-6 R2.2: Evaluate security patches at least every 35 days0
CIP-007 R2.3CIP-007-6 R2.3: Apply patches or create or revise a mitigation plan within 35 days0
CIP-007 R2.4CIP-007-6 R2.4: Implement mitigation plans on time0
CIP-007 R3CIP-007-6 R30
CIP-007 R3.1CIP-007-6 R3.1: Deploy methods to deter, detect or prevent malicious code0
CIP-007 R3.2CIP-007-6 R3.2: Mitigate detected malicious code0
CIP-007 R3.3CIP-007-6 R3.3: Update signatures or patterns with testing0
CIP-007 R4CIP-007-6 R40
CIP-007 R4.1CIP-007-6 R4.1: Log security events0
CIP-007 R4.2CIP-007-6 R4.2: Alert on security events0
CIP-007 R4.3CIP-007-6 R4.3: Retain event logs for 90 days0
CIP-007 R4.4CIP-007-6 R4.4: Review logged events every 15 days0
CIP-007 R5CIP-007-6 R50
CIP-007 R5.1CIP-007-6 R5.1: Enforce authentication of interactive user access0
CIP-007 R5.2CIP-007-6 R5.2: Inventory default and generic account types0
CIP-007 R5.3CIP-007-6 R5.3: Identify individuals with access to shared accounts0
CIP-007 R5.4CIP-007-6 R5.4: Change known default passwords0
CIP-007 R5.5CIP-007-6 R5.5: Password length and complexity for password-only authentication0
CIP-007 R5.6CIP-007-6 R5.6: Password change at least every 15 months0
CIP-007 R5.7CIP-007-6 R5.7: Limit or alert on unsuccessful authentication attempts0
CIP-008 R1CIP-008-6 R10
CIP-008 R1.1CIP-008-6 R1.1: Processes to identify, classify and respond to Cyber Security Incidents0
CIP-008 R1.2CIP-008-6 R1.2: Criteria for attempts to compromise and reportability0
CIP-008 R1.3CIP-008-6 R1.3: Roles and responsibilities of response groups0
CIP-008 R1.4CIP-008-6 R1.4: Incident handling procedures0
CIP-008 R2CIP-008-6 R20
CIP-008 R2.1CIP-008-6 R2.1: Test response plans every 15 calendar months0
CIP-008 R2.2CIP-008-6 R2.2: Use the plan and document deviations0
CIP-008 R2.3CIP-008-6 R2.3: Retain incident records0
CIP-008 R3CIP-008-6 R30
CIP-008 R3.1CIP-008-6 R3.1: Lessons learned and plan update within 90 days0
CIP-008 R3.2CIP-008-6 R3.2: Update the plan within 60 days of role or technology changes0
CIP-008 R4CIP-008-6 R40
CIP-008 R4.1CIP-008-6 R4.1: Notification content: functional impact, attack vector, level of intrusion0
CIP-008 R4.2CIP-008-6 R4.2: Notification timelines: one hour and next calendar day0
CIP-008 R4.3CIP-008-6 R4.3: Updates within 7 days of new attribute information0
CIP-009 R1CIP-009-6 R10
CIP-009 R1.1CIP-009-6 R1.1: Conditions for activating recovery plans0
CIP-009 R1.2CIP-009-6 R1.2: Roles and responsibilities of responders0
CIP-009 R1.3CIP-009-6 R1.3: Backup and storage of recovery information0
CIP-009 R1.4CIP-009-6 R1.4: Verify backups and address failures0
CIP-009 R1.5CIP-009-6 R1.5: Preserve data for determining incident cause0
CIP-009 R2CIP-009-6 R20
CIP-009 R2.1CIP-009-6 R2.1: Test recovery plans every 15 calendar months0
CIP-009 R2.2CIP-009-6 R2.2: Test a representative sample of backup information0
CIP-009 R2.3CIP-009-6 R2.3: Operational exercise every 36 months for high impact0
CIP-009 R3CIP-009-6 R30
CIP-009 R3.1CIP-009-6 R3.1: Lessons learned and plan update within 90 days of a test or recovery0
CIP-009 R3.2CIP-009-6 R3.2: Update recovery plans within 60 days of changes0
CIP-010 R1CIP-010-4 R10
CIP-010 R1.1CIP-010-4 R1.1: Baseline configuration0
CIP-010 R1.2CIP-010-4 R1.2: Authorize and document baseline changes0
CIP-010 R1.3CIP-010-4 R1.3: Update the baseline within 30 days of a change0
CIP-010 R1.4CIP-010-4 R1.4: Verify CIP-005 and CIP-007 controls are unaffected by changes0
CIP-010 R1.5CIP-010-4 R1.5: Test changes in a test environment for high impact systems0
CIP-010 R1.6CIP-010-4 R1.6: Verify software source identity and integrity before changes0
CIP-010 R2CIP-010-4 R20
CIP-010 R2.1CIP-010-4 R2.1: Monitor for baseline changes every 35 days0
CIP-010 R3CIP-010-4 R30
CIP-010 R3.1CIP-010-4 R3.1: Vulnerability assessment every 15 calendar months0
CIP-010 R3.2CIP-010-4 R3.2: Active vulnerability assessment every 36 months for high impact0
CIP-010 R3.3CIP-010-4 R3.3: Active vulnerability assessment before adding new Cyber Assets0
CIP-010 R3.4CIP-010-4 R3.4: Document assessment results and remediation action plans0
CIP-010 R4CIP-010-4 R40
CIP-010 R4 Att1 1.1CIP-010-4 R4 Att1 1.1: Transient Cyber Assets managed by the entity: management approach0
CIP-010 R4 Att1 1.2CIP-010-4 R4 Att1 1.2: Transient Cyber Assets managed by the entity: authorization0
CIP-010 R4 Att1 1.3CIP-010-4 R4 Att1 1.3: Transient Cyber Assets managed by the entity: software vulnerability mitigation0
CIP-010 R4 Att1 1.4CIP-010-4 R4 Att1 1.4: Transient Cyber Assets managed by the entity: malicious code mitigation0
CIP-010 R4 Att1 1.5CIP-010-4 R4 Att1 1.5: Transient Cyber Assets managed by the entity: unauthorized use mitigation0
CIP-010 R4 Att1 2.1CIP-010-4 R4 Att1 2.1: Third-party Transient Cyber Assets: software vulnerability mitigation0
CIP-010 R4 Att1 2.2CIP-010-4 R4 Att1 2.2: Third-party Transient Cyber Assets: malicious code mitigation0
CIP-010 R4 Att1 2.3CIP-010-4 R4 Att1 2.3: Third-party Transient Cyber Assets: additional mitigation before connection0
CIP-010 R4 Att1 3.1CIP-010-4 R4 Att1 3.1: Removable Media: authorization of users and locations0
CIP-010 R4 Att1 3.2CIP-010-4 R4 Att1 3.2: Removable Media: detect and mitigate malicious code before connection0
CIP-011 R1CIP-011-3 R10
CIP-011 R1.1CIP-011-3 R1.1: Methods to identify BCSI0
CIP-011 R1.2CIP-011-3 R1.2: Methods to protect and securely handle BCSI0
CIP-011 R2CIP-011-3 R20
CIP-011 R2.1CIP-011-3 R2.1: Prevent BCSI retrieval before reuse of Cyber Assets0
CIP-011 R2.2CIP-011-3 R2.2: Prevent BCSI retrieval or destroy media before disposal0
CIP-012 R1CIP-012-2 R10
CIP-012 R1.1CIP-012-2 R1.1: Mitigate unauthorized disclosure and modification of real-time data between Control Centers0
CIP-012 R1.2CIP-012-2 R1.2: Mitigate loss of the ability to communicate real-time data0
CIP-012 R1.3CIP-012-2 R1.3: Initiate recovery of communication links0
CIP-012 R1.4CIP-012-2 R1.4: Identify where the mitigation methods are implemented0
CIP-012 R1.5CIP-012-2 R1.5: Allocate responsibilities between Control Center owners0
CIP-013 R1CIP-013-2 R10
CIP-013 R1.1CIP-013-2 R1.1: Identify and assess supply chain cyber risks in procurement planning0
CIP-013 R1.2CIP-013-2 R1.20
CIP-013 R1.2.1CIP-013-2 R1.2.1: Vendor notification of vendor-identified incidents0
CIP-013 R1.2.2CIP-013-2 R1.2.2: Coordination of responses to vendor-identified incidents0
CIP-013 R1.2.3CIP-013-2 R1.2.3: Vendor notification when access should end0
CIP-013 R1.2.4CIP-013-2 R1.2.4: Vendor disclosure of known vulnerabilities0
CIP-013 R1.2.5CIP-013-2 R1.2.5: Verify integrity and authenticity of vendor software and patches0
CIP-013 R1.2.6CIP-013-2 R1.2.6: Coordinate controls for vendor-initiated remote access0
CIP-013 R2CIP-013-2 R2: Implement the supply chain risk management plan0
CIP-013 R3CIP-013-2 R3: Review and approve the plan every 15 calendar months0
CIP-014 R1CIP-014-3 R1: Transmission risk assessment of qualifying stations and substations0
CIP-014 R1.1CIP-014-3 R1.1: Frequency of subsequent risk assessments0
CIP-014 R1.2CIP-014-3 R1.2: Identify primary control centers0
CIP-014 R2CIP-014-3 R2: Unaffiliated third-party verification of the risk assessment0
CIP-014 R2.1CIP-014-3 R2.1: Qualified verifying entity0
CIP-014 R2.2CIP-014-3 R2.2: Verification completed within 90 days0
CIP-014 R2.3CIP-014-3 R2.3: Act on verifier recommendations within 60 days0
CIP-014 R2.4CIP-014-3 R2.4: Protect sensitive information shared with the verifier0
CIP-014 R3CIP-014-3 R3: Notify the Transmission Operator of identified primary control centers0
CIP-014 R3.1CIP-014-3 R3.1: Notify the Transmission Operator of removals0
CIP-014 R4CIP-014-3 R4: Evaluate physical threats and vulnerabilities0
CIP-014 R5CIP-014-3 R5: Develop and implement physical security plans0
CIP-014 R5.1CIP-014-3 R5.1: Plan attribute: deter, detect, delay, assess, communicate and respond0
CIP-014 R5.2CIP-014-3 R5.2: Plan attribute: law enforcement contact and coordination0
CIP-014 R5.3CIP-014-3 R5.3: Plan attribute: timeline for enhancements0
CIP-014 R5.4CIP-014-3 R5.4: Plan attribute: evaluating evolving threats0
CIP-014 R6CIP-014-3 R6: Unaffiliated third-party review of the evaluation and plan0
CIP-014 R6.1CIP-014-3 R6.1: Qualified third-party reviewer0
CIP-014 R6.2CIP-014-3 R6.2: Review completed within 90 days0
CIP-014 R6.3CIP-014-3 R6.3: Act on reviewer recommendations within 60 days0
CIP-014 R6.4CIP-014-3 R6.4: Protect sensitive information shared with the reviewer0
CIP-015CIP-015 Internal Network Security Monitoring (subject to future enforcement)0
DEFINITIONSKey NERC Glossary terms as currently enforced0
STANDARDNERC CIP: the Critical Infrastructure Protection Reliability Standards0
STATUSStatus on 2026-09-25: what is in force, and the versions subject to future enforcement0

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
  • BCSI classification methodology
  • BCSI inventory
  • Handling procedures (physical and electronic)
  • Disposal/sanitization records

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