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) | 107 |
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) | 39 |
CIP-002 R1 | CIP-002-5.1a R1 | 0 |
CIP-002 R1.1 | CIP-002-5.1a R1.1: Identify high impact BES Cyber Systems | 0 |
CIP-002 R1.2 | CIP-002-5.1a R1.2: Identify medium impact BES Cyber Systems | 0 |
CIP-002 R1.3 | CIP-002-5.1a R1.3: Identify assets containing low impact BES Cyber Systems | 0 |
CIP-002 R2 | CIP-002-5.1a R2 | 0 |
CIP-002 R2.1 | CIP-002-5.1a R2.1: Review the identifications at least every 15 calendar months | 0 |
CIP-002 R2.2 | CIP-002-5.1a R2.2: CIP Senior Manager approval of the identifications every 15 calendar months | 0 |
CIP-003 R1 | CIP-003-9 R1 | 0 |
CIP-003 R1.1 | CIP-003-9 R1.1: Cyber security policies for high and medium impact systems | 0 |
CIP-003 R1.2 | CIP-003-9 R1.2: Cyber security policies for assets containing low impact systems | 0 |
CIP-003 R2 | CIP-003-9 R2 | 0 |
CIP-003 R2 Att1 S1 | CIP-003-9 R2 Att1 S1: Low impact plan Section 1: cyber security awareness | 0 |
CIP-003 R2 Att1 S2 | CIP-003-9 R2 Att1 S2: Low impact plan Section 2: physical security controls | 0 |
CIP-003 R2 Att1 S3 | CIP-003-9 R2 Att1 S3: Low impact plan Section 3: electronic access controls | 0 |
CIP-003 R2 Att1 S4 | CIP-003-9 R2 Att1 S4: Low impact plan Section 4: Cyber Security Incident response | 0 |
CIP-003 R2 Att1 S5 | CIP-003-9 R2 Att1 S5: Low impact plan Section 5: Transient Cyber Asset and Removable Media malicious code mitigation | 0 |
CIP-003 R2 Att1 S6 | CIP-003-9 R2 Att1 S6: Low impact plan Section 6: vendor electronic remote access security controls | 0 |
CIP-003 R3 | CIP-003-9 R3: Identify the CIP Senior Manager by name | 0 |
CIP-003 R4 | CIP-003-9 R4: Documented delegation of CIP Senior Manager authority | 0 |
CIP-004 R1 | CIP-004-7 R1 | 0 |
CIP-004 R1.1 | CIP-004-7 R1.1: Quarterly security awareness reinforcement | 0 |
CIP-004 R2 | CIP-004-7 R2 | 0 |
CIP-004 R2.1 | CIP-004-7 R2.1: Cyber security training content | 0 |
CIP-004 R2.2 | CIP-004-7 R2.2: Training before access is granted | 0 |
CIP-004 R2.3 | CIP-004-7 R2.3: Training at least every 15 calendar months | 0 |
CIP-004 R3 | CIP-004-7 R3 | 0 |
CIP-004 R3.1 | CIP-004-7 R3.1: Personnel risk assessment: confirm identity | 0 |
CIP-004 R3.2 | CIP-004-7 R3.2: Personnel risk assessment: seven-year criminal history records check | 0 |
CIP-004 R3.3 | CIP-004-7 R3.3: Criteria to evaluate criminal history records checks | 0 |
CIP-004 R3.4 | CIP-004-7 R3.4: Verify contractor and vendor personnel risk assessments | 0 |
CIP-004 R3.5 | CIP-004-7 R3.5: Personnel risk assessment within the last seven years | 0 |
CIP-004 R4 | CIP-004-7 R4 | 0 |
CIP-004 R4.1 | CIP-004-7 R4.1: Authorize access based on need | 0 |
CIP-004 R4.2 | CIP-004-7 R4.2: Quarterly verification of access against authorization | 0 |
CIP-004 R4.3 | CIP-004-7 R4.3: Verify user accounts and privileges every 15 calendar months | 0 |
CIP-004 R5 | CIP-004-7 R5 | 0 |
CIP-004 R5.1 | CIP-004-7 R5.1: Remove access within 24 hours of a termination action | 0 |
CIP-004 R5.2 | CIP-004-7 R5.2: Revoke unneeded access on reassignment or transfer | 0 |
CIP-004 R5.3 | CIP-004-7 R5.3: Revoke non-shared accounts within 30 days of termination | 0 |
CIP-004 R5.4 | CIP-004-7 R5.4: Change shared account passwords after termination or transfer | 0 |
CIP-004 R6 | CIP-004-7 R6 | 0 |
CIP-004 R6.1 | CIP-004-7 R6.1: Authorize provisioned access to BCSI | 0 |
CIP-004 R6.2 | CIP-004-7 R6.2: Verify provisioned BCSI access every 15 calendar months | 0 |
CIP-004 R6.3 | CIP-004-7 R6.3: Remove BCSI access by the next calendar day after termination | 0 |
CIP-005 R1 | CIP-005-7 R1 | 0 |
CIP-005 R1.1 | CIP-005-7 R1.1: All routable Cyber Assets inside a defined ESP | 0 |
CIP-005 R1.2 | CIP-005-7 R1.2: External Routable Connectivity through an identified EAP | 0 |
CIP-005 R1.3 | CIP-005-7 R1.3: Inbound and outbound permissions with reasons, deny by default | 0 |
CIP-005 R1.4 | CIP-005-7 R1.4: Authenticate Dial-up Connectivity | 0 |
CIP-005 R1.5 | CIP-005-7 R1.5: Detect malicious communications at EAPs | 0 |
CIP-005 R2 | CIP-005-7 R2 | 0 |
CIP-005 R2.1 | CIP-005-7 R2.1: Interactive Remote Access through an Intermediate System | 0 |
CIP-005 R2.2 | CIP-005-7 R2.2: Encryption of Interactive Remote Access terminating at the Intermediate System | 0 |
CIP-005 R2.3 | CIP-005-7 R2.3: Multi-factor authentication for Interactive Remote Access | 0 |
CIP-005 R2.4 | CIP-005-7 R2.4: Determine active vendor remote access sessions | 0 |
CIP-005 R2.5 | CIP-005-7 R2.5: Disable active vendor remote access | 0 |
CIP-005 R3 | CIP-005-7 R3 | 0 |
CIP-005 R3.1 | CIP-005-7 R3.1: Determine authenticated vendor-initiated connections to EACMS and PACS | 0 |
CIP-005 R3.2 | CIP-005-7 R3.2: Terminate vendor-initiated connections to EACMS and PACS and control reconnection | 0 |
CIP-006 R1 | CIP-006-6 R1 | 0 |
CIP-006 R1.1 | CIP-006-6 R1.1: Operational or procedural controls to restrict physical access | 0 |
CIP-006 R1.10 | CIP-006-6 R1.10: Protect cabling outside a PSP within the same ESP | 0 |
CIP-006 R1.2 | CIP-006-6 R1.2: At least one physical access control into each PSP | 0 |
CIP-006 R1.3 | CIP-006-6 R1.3: Two or more physical access controls for high impact PSPs | 0 |
CIP-006 R1.4 | CIP-006-6 R1.4: Monitor for unauthorized physical access into PSPs | 0 |
CIP-006 R1.5 | CIP-006-6 R1.5: Alarm within 15 minutes of detected unauthorized PSP access | 0 |
CIP-006 R1.6 | CIP-006-6 R1.6: Monitor PACS for unauthorized physical access | 0 |
CIP-006 R1.7 | CIP-006-6 R1.7: Alarm within 15 minutes of unauthorized PACS access | 0 |
CIP-006 R1.8 | CIP-006-6 R1.8: Log entry of each authorized individual into each PSP | 0 |
CIP-006 R1.9 | CIP-006-6 R1.9: Retain physical access logs for 90 days | 0 |
CIP-006 R2 | CIP-006-6 R2 | 0 |
CIP-006 R2.1 | CIP-006-6 R2.1: Continuous escort of visitors within PSPs | 0 |
CIP-006 R2.2 | CIP-006-6 R2.2: Log visitor entry and exit | 0 |
CIP-006 R2.3 | CIP-006-6 R2.3: Retain visitor logs for 90 days | 0 |
CIP-006 R3 | CIP-006-6 R3 | 0 |
CIP-006 R3.1 | CIP-006-6 R3.1: Maintain and test PACS and PSP devices every 24 months | 0 |
CIP-007 R1 | CIP-007-6 R1 | 0 |
CIP-007 R1.1 | CIP-007-6 R1.1: Enable only needed logical network ports | 0 |
CIP-007 R1.2 | CIP-007-6 R1.2: Protect unnecessary physical input/output ports | 0 |
CIP-007 R2 | CIP-007-6 R2 | 0 |
CIP-007 R2.1 | CIP-007-6 R2.1: Patch management process with tracked sources | 0 |
CIP-007 R2.2 | CIP-007-6 R2.2: Evaluate security patches at least every 35 days | 0 |
CIP-007 R2.3 | CIP-007-6 R2.3: Apply patches or create or revise a mitigation plan within 35 days | 0 |
CIP-007 R2.4 | CIP-007-6 R2.4: Implement mitigation plans on time | 0 |
CIP-007 R3 | CIP-007-6 R3 | 0 |
CIP-007 R3.1 | CIP-007-6 R3.1: Deploy methods to deter, detect or prevent malicious code | 0 |
CIP-007 R3.2 | CIP-007-6 R3.2: Mitigate detected malicious code | 0 |
CIP-007 R3.3 | CIP-007-6 R3.3: Update signatures or patterns with testing | 0 |
CIP-007 R4 | CIP-007-6 R4 | 0 |
CIP-007 R4.1 | CIP-007-6 R4.1: Log security events | 0 |
CIP-007 R4.2 | CIP-007-6 R4.2: Alert on security events | 0 |
CIP-007 R4.3 | CIP-007-6 R4.3: Retain event logs for 90 days | 0 |
CIP-007 R4.4 | CIP-007-6 R4.4: Review logged events every 15 days | 0 |
CIP-007 R5 | CIP-007-6 R5 | 0 |
CIP-007 R5.1 | CIP-007-6 R5.1: Enforce authentication of interactive user access | 0 |
CIP-007 R5.2 | CIP-007-6 R5.2: Inventory default and generic account types | 0 |
CIP-007 R5.3 | CIP-007-6 R5.3: Identify individuals with access to shared accounts | 0 |
CIP-007 R5.4 | CIP-007-6 R5.4: Change known default passwords | 0 |
CIP-007 R5.5 | CIP-007-6 R5.5: Password length and complexity for password-only authentication | 0 |
CIP-007 R5.6 | CIP-007-6 R5.6: Password change at least every 15 months | 0 |
CIP-007 R5.7 | CIP-007-6 R5.7: Limit or alert on unsuccessful authentication attempts | 0 |
CIP-008 R1 | CIP-008-6 R1 | 0 |
CIP-008 R1.1 | CIP-008-6 R1.1: Processes to identify, classify and respond to Cyber Security Incidents | 0 |
CIP-008 R1.2 | CIP-008-6 R1.2: Criteria for attempts to compromise and reportability | 0 |
CIP-008 R1.3 | CIP-008-6 R1.3: Roles and responsibilities of response groups | 0 |
CIP-008 R1.4 | CIP-008-6 R1.4: Incident handling procedures | 0 |
CIP-008 R2 | CIP-008-6 R2 | 0 |
CIP-008 R2.1 | CIP-008-6 R2.1: Test response plans every 15 calendar months | 0 |
CIP-008 R2.2 | CIP-008-6 R2.2: Use the plan and document deviations | 0 |
CIP-008 R2.3 | CIP-008-6 R2.3: Retain incident records | 0 |
CIP-008 R3 | CIP-008-6 R3 | 0 |
CIP-008 R3.1 | CIP-008-6 R3.1: Lessons learned and plan update within 90 days | 0 |
CIP-008 R3.2 | CIP-008-6 R3.2: Update the plan within 60 days of role or technology changes | 0 |
CIP-008 R4 | CIP-008-6 R4 | 0 |
CIP-008 R4.1 | CIP-008-6 R4.1: Notification content: functional impact, attack vector, level of intrusion | 0 |
CIP-008 R4.2 | CIP-008-6 R4.2: Notification timelines: one hour and next calendar day | 0 |
CIP-008 R4.3 | CIP-008-6 R4.3: Updates within 7 days of new attribute information | 0 |
CIP-009 R1 | CIP-009-6 R1 | 0 |
CIP-009 R1.1 | CIP-009-6 R1.1: Conditions for activating recovery plans | 0 |
CIP-009 R1.2 | CIP-009-6 R1.2: Roles and responsibilities of responders | 0 |
CIP-009 R1.3 | CIP-009-6 R1.3: Backup and storage of recovery information | 0 |
CIP-009 R1.4 | CIP-009-6 R1.4: Verify backups and address failures | 0 |
CIP-009 R1.5 | CIP-009-6 R1.5: Preserve data for determining incident cause | 0 |
CIP-009 R2 | CIP-009-6 R2 | 0 |
CIP-009 R2.1 | CIP-009-6 R2.1: Test recovery plans every 15 calendar months | 0 |
CIP-009 R2.2 | CIP-009-6 R2.2: Test a representative sample of backup information | 0 |
CIP-009 R2.3 | CIP-009-6 R2.3: Operational exercise every 36 months for high impact | 0 |
CIP-009 R3 | CIP-009-6 R3 | 0 |
CIP-009 R3.1 | CIP-009-6 R3.1: Lessons learned and plan update within 90 days of a test or recovery | 0 |
CIP-009 R3.2 | CIP-009-6 R3.2: Update recovery plans within 60 days of changes | 0 |
CIP-010 R1 | CIP-010-4 R1 | 0 |
CIP-010 R1.1 | CIP-010-4 R1.1: Baseline configuration | 0 |
CIP-010 R1.2 | CIP-010-4 R1.2: Authorize and document baseline changes | 0 |
CIP-010 R1.3 | CIP-010-4 R1.3: Update the baseline within 30 days of a change | 0 |
CIP-010 R1.4 | CIP-010-4 R1.4: Verify CIP-005 and CIP-007 controls are unaffected by changes | 0 |
CIP-010 R1.5 | CIP-010-4 R1.5: Test changes in a test environment for high impact systems | 0 |
CIP-010 R1.6 | CIP-010-4 R1.6: Verify software source identity and integrity before changes | 0 |
CIP-010 R2 | CIP-010-4 R2 | 0 |
CIP-010 R2.1 | CIP-010-4 R2.1: Monitor for baseline changes every 35 days | 0 |
CIP-010 R3 | CIP-010-4 R3 | 0 |
CIP-010 R3.1 | CIP-010-4 R3.1: Vulnerability assessment every 15 calendar months | 0 |
CIP-010 R3.2 | CIP-010-4 R3.2: Active vulnerability assessment every 36 months for high impact | 0 |
CIP-010 R3.3 | CIP-010-4 R3.3: Active vulnerability assessment before adding new Cyber Assets | 0 |
CIP-010 R3.4 | CIP-010-4 R3.4: Document assessment results and remediation action plans | 0 |
CIP-010 R4 | CIP-010-4 R4 | 0 |
CIP-010 R4 Att1 1.1 | CIP-010-4 R4 Att1 1.1: Transient Cyber Assets managed by the entity: management approach | 0 |
CIP-010 R4 Att1 1.2 | CIP-010-4 R4 Att1 1.2: Transient Cyber Assets managed by the entity: authorization | 0 |
CIP-010 R4 Att1 1.3 | CIP-010-4 R4 Att1 1.3: Transient Cyber Assets managed by the entity: software vulnerability mitigation | 0 |
CIP-010 R4 Att1 1.4 | CIP-010-4 R4 Att1 1.4: Transient Cyber Assets managed by the entity: malicious code mitigation | 0 |
CIP-010 R4 Att1 1.5 | CIP-010-4 R4 Att1 1.5: Transient Cyber Assets managed by the entity: unauthorized use mitigation | 0 |
CIP-010 R4 Att1 2.1 | CIP-010-4 R4 Att1 2.1: Third-party Transient Cyber Assets: software vulnerability mitigation | 0 |
CIP-010 R4 Att1 2.2 | CIP-010-4 R4 Att1 2.2: Third-party Transient Cyber Assets: malicious code mitigation | 0 |
CIP-010 R4 Att1 2.3 | CIP-010-4 R4 Att1 2.3: Third-party Transient Cyber Assets: additional mitigation before connection | 0 |
CIP-010 R4 Att1 3.1 | CIP-010-4 R4 Att1 3.1: Removable Media: authorization of users and locations | 0 |
CIP-010 R4 Att1 3.2 | CIP-010-4 R4 Att1 3.2: Removable Media: detect and mitigate malicious code before connection | 0 |
CIP-011 R1 | CIP-011-3 R1 | 0 |
CIP-011 R1.1 | CIP-011-3 R1.1: Methods to identify BCSI | 0 |
CIP-011 R1.2 | CIP-011-3 R1.2: Methods to protect and securely handle BCSI | 0 |
CIP-011 R2 | CIP-011-3 R2 | 0 |
CIP-011 R2.1 | CIP-011-3 R2.1: Prevent BCSI retrieval before reuse of Cyber Assets | 0 |
CIP-011 R2.2 | CIP-011-3 R2.2: Prevent BCSI retrieval or destroy media before disposal | 0 |
CIP-012 R1 | CIP-012-2 R1 | 0 |
CIP-012 R1.1 | CIP-012-2 R1.1: Mitigate unauthorized disclosure and modification of real-time data between Control Centers | 0 |
CIP-012 R1.2 | CIP-012-2 R1.2: Mitigate loss of the ability to communicate real-time data | 0 |
CIP-012 R1.3 | CIP-012-2 R1.3: Initiate recovery of communication links | 0 |
CIP-012 R1.4 | CIP-012-2 R1.4: Identify where the mitigation methods are implemented | 0 |
CIP-012 R1.5 | CIP-012-2 R1.5: Allocate responsibilities between Control Center owners | 0 |
CIP-013 R1 | CIP-013-2 R1 | 0 |
CIP-013 R1.1 | CIP-013-2 R1.1: Identify and assess supply chain cyber risks in procurement planning | 0 |
CIP-013 R1.2 | CIP-013-2 R1.2 | 0 |
CIP-013 R1.2.1 | CIP-013-2 R1.2.1: Vendor notification of vendor-identified incidents | 0 |
CIP-013 R1.2.2 | CIP-013-2 R1.2.2: Coordination of responses to vendor-identified incidents | 0 |
CIP-013 R1.2.3 | CIP-013-2 R1.2.3: Vendor notification when access should end | 0 |
CIP-013 R1.2.4 | CIP-013-2 R1.2.4: Vendor disclosure of known vulnerabilities | 0 |
CIP-013 R1.2.5 | CIP-013-2 R1.2.5: Verify integrity and authenticity of vendor software and patches | 0 |
CIP-013 R1.2.6 | CIP-013-2 R1.2.6: Coordinate controls for vendor-initiated remote access | 0 |
CIP-013 R2 | CIP-013-2 R2: Implement the supply chain risk management plan | 0 |
CIP-013 R3 | CIP-013-2 R3: Review and approve the plan every 15 calendar months | 0 |
CIP-014 R1 | CIP-014-3 R1: Transmission risk assessment of qualifying stations and substations | 0 |
CIP-014 R1.1 | CIP-014-3 R1.1: Frequency of subsequent risk assessments | 0 |
CIP-014 R1.2 | CIP-014-3 R1.2: Identify primary control centers | 0 |
CIP-014 R2 | CIP-014-3 R2: Unaffiliated third-party verification of the risk assessment | 0 |
CIP-014 R2.1 | CIP-014-3 R2.1: Qualified verifying entity | 0 |
CIP-014 R2.2 | CIP-014-3 R2.2: Verification completed within 90 days | 0 |
CIP-014 R2.3 | CIP-014-3 R2.3: Act on verifier recommendations within 60 days | 0 |
CIP-014 R2.4 | CIP-014-3 R2.4: Protect sensitive information shared with the verifier | 0 |
CIP-014 R3 | CIP-014-3 R3: Notify the Transmission Operator of identified primary control centers | 0 |
CIP-014 R3.1 | CIP-014-3 R3.1: Notify the Transmission Operator of removals | 0 |
CIP-014 R4 | CIP-014-3 R4: Evaluate physical threats and vulnerabilities | 0 |
CIP-014 R5 | CIP-014-3 R5: Develop and implement physical security plans | 0 |
CIP-014 R5.1 | CIP-014-3 R5.1: Plan attribute: deter, detect, delay, assess, communicate and respond | 0 |
CIP-014 R5.2 | CIP-014-3 R5.2: Plan attribute: law enforcement contact and coordination | 0 |
CIP-014 R5.3 | CIP-014-3 R5.3: Plan attribute: timeline for enhancements | 0 |
CIP-014 R5.4 | CIP-014-3 R5.4: Plan attribute: evaluating evolving threats | 0 |
CIP-014 R6 | CIP-014-3 R6: Unaffiliated third-party review of the evaluation and plan | 0 |
CIP-014 R6.1 | CIP-014-3 R6.1: Qualified third-party reviewer | 0 |
CIP-014 R6.2 | CIP-014-3 R6.2: Review completed within 90 days | 0 |
CIP-014 R6.3 | CIP-014-3 R6.3: Act on reviewer recommendations within 60 days | 0 |
CIP-014 R6.4 | CIP-014-3 R6.4: Protect sensitive information shared with the reviewer | 0 |
CIP-015 | CIP-015 Internal Network Security Monitoring (subject to future enforcement) | 0 |
DEFINITIONS | Key NERC Glossary terms as currently enforced | 0 |
STANDARD | NERC CIP: the Critical Infrastructure Protection Reliability Standards | 0 |
STATUS | Status on 2026-09-25: what is in force, and the versions subject to future enforcement | 0 |