Key takeaways
- Part 1.10 traces to a FERC directive and a NERC-petitioned interpretation (Docket No.
- Part 2.1 — "Require continuous escorted access of visitors ...
- CIP-006-6 is the standard enforced today, but a successor is already locked in.
- Match access control strength to impact rating before anything else.
NERC CIP-006-6, "Cyber Security — Physical Security of BES Cyber Systems," is the mandatory, FERC-approved Reliability Standard that governs how utilities and grid operators control physical access to BES Cyber Systems — the counterpart to CIP-005's electronic access controls. Per its own Purpose clause it exists "to manage physical access to Bulk Electric System (BES) Cyber Systems by specifying a physical security plan in support of protecting BES Cyber Systems against compromise that could lead to misoperation or instability in the Bulk Electric System (BES)." CIP-006-6 was approved by FERC on 21 January 2016 in Order No. 822 (Docket No. RM15-14-000), published in the Federal Register at 81 FR 4177 alongside six other CIP version 5 standards (CIP-003-6, CIP-004-6, CIP-007-6, CIP-009-6, CIP-010-2 and CIP-011-2); it became effective and enforceable on 1 July 2016 and remains the enforceable version today, even though a virtualization-focused successor, CIP-006-7.1, is already FERC-approved for a 2028 compliance date (see below).
Who must comply
CIP-006 applies to Balancing Authorities, Distribution Providers that own certain load-shedding, special protection, under-voltage/under-frequency load-shedding, or Transmission Protection Systems, Generator Operators and Owners, Interchange Coordinators/Authorities, Reliability Coordinators, and Transmission Operators and Owners. The substantive obligations attach to High and Medium Impact BES Cyber Systems — categorized under the separate CIP-002 process — plus their associated Physical Access Control Systems (PACS) and, for several parts, Electronic Access Control or Monitoring Systems (EACMS) and Protected Cyber Assets (PCA).
R1: the Physical Security Plan's ten parts
Requirement R1 requires "one or more documented physical security plan(s) that collectively include all of the applicable requirement parts in CIP-006-6 Table R1 — Physical Security Plan." The ten parts scale obligations by impact rating and connectivity:
| Part | Requirement (quoted from the standard) | Applies to |
|---|---|---|
| 1.1 | Define operational or procedural controls to restrict physical access | Medium Impact systems without External Routable Connectivity, and their PACS |
| 1.2 | "Utilize at least one physical access control to allow unescorted physical access ... to only those individuals who have authorized unescorted physical access" | Medium Impact systems with External Routable Connectivity, and associated EACMS/PCA |
| 1.3 | "Utilize two or more different physical access controls ... to collectively allow unescorted physical access ... to only those individuals who have authorized" access | High Impact systems and associated components |
| 1.4 | Monitor for unauthorized access through a physical access point into a Physical Security Perimeter | High and Medium Impact systems with External Routable Connectivity |
| 1.5 | Issue an alarm or alert in response to detected unauthorized physical access "within 15 minutes of detection," to identified incident response personnel | Same scope as 1.4 |
| 1.6 | Monitor each Physical Access Control System for unauthorized physical access to the PACS itself | High Impact and Medium Impact systems with External Routable Connectivity |
| 1.7 | Issue an alarm or alert for unauthorized PACS access "within 15 minutes," to identified personnel | Same scope as 1.6 |
| 1.8 | Log entry of each individual with authorized unescorted physical access into each Physical Security Perimeter, identifying the individual and date/time of entry | High and Medium Impact systems |
| 1.9 | "Retain physical access logs of entry ... for at least ninety calendar days" | Same scope as 1.8 |
| 1.10 | Restrict physical access to cabling and other nonprogrammable communication components; where that restriction isn't implemented, document and implement an alternative (e.g., encryption or alarmed monitoring) | High Impact systems |
Part 1.10 traces to a FERC directive and a NERC-petitioned interpretation (Docket No. RD10-13-000) that identified encryption and circuit monitoring as acceptable alternatives when physical cable protection isn't feasible — entities should not assume cabling restriction is the only compliant option.
R2: the Visitor Control Program
Requirement R2 requires a documented visitor control program with three parts, scoped to High and Medium Impact systems with External Routable Connectivity:
- Part 2.1 — "Require continuous escorted access of visitors ... within each Physical Security Perimeter, except during CIP Exceptional Circumstances."
- Part 2.2 — "Require manual or automated logging of visitor entry into and exit from the Physical Security Perimeter that includes date and time of the initial entry and last exit, the visitor's name, and the name of an individual point of contact," except during Exceptional Circumstances.
- Part 2.3 — "Retain visitor logs for at least ninety calendar days."
R3: PACS maintenance and testing
Requirement R3 requires "maintenance and testing of each Physical Access Control System and locally mounted hardware or devices at the Physical Security Perimeter at least once every 24 calendar months to ensure they function properly," for High Impact systems and Medium Impact systems with External Routable Connectivity. Unlike the 90-day log retention in R1 and R2, this is a recurring functional-test cycle, not a records-retention window — a badge reader that logs correctly but hasn't been functionally tested in over two years is a gap under R3 even if its access logs look complete.
Evidence retention: three calendar years
Per CIP-006-6's Compliance section, "the applicable entity shall retain evidence of each requirement in this standard for three calendar years" — the same retention period used across the CIP suite (see CIP-010 and CIP-011). This three-year evidence window is separate from, and longer than, the 90-day log retention that R1 Part 1.9 and R2 Part 2.3 require for the underlying access and visitor logs themselves — entities need a process to preserve or summarize 90-day logs into evidence that survives for the full three-year compliance retention period.
CIP-006-7.1 is already approved — the 2028 compliance clock is running
CIP-006-6 is the standard enforced today, but a successor is already locked in. On 19 March 2026 the Federal Energy Regulatory Commission issued Order No. 919 (Docket No. RM24-8-000), approving 11 modified CIP Reliability Standards together as part of NERC's Project 2016-02 virtualization package — published in the Federal Register on 24 March 2026 at 91 FR 13957, naming "CIP-006-7.1 (Cyber Security—Physical Security of BES Cyber Systems)" alongside CIP-002-7, CIP-003-10, CIP-004-8, CIP-005-8, CIP-007-7.1, CIP-008-7.1, CIP-009-7.1, CIP-010-5, CIP-011-4.1 and CIP-013-3. The order itself states "this final action is effective May 26, 2026."
Per NERC's implementation plan, the revised standards take effect on the later of 1 April 2026 or "the first day of the first calendar quarter that is 24 months after" the order's effective date. NERC's own July 2026 Standards, Compliance, and Enforcement Bulletin confirms the resulting literal date, listing "CIP-006-7.1 – Cyber Security — Physical Security of BES Cyber Systems" among standards for which "the revised standards will become effective July 1, 2028." The package's substantive driver is the same across all 11 standards: four new NERC Glossary terms (Cyber System, Management Interface, Shared Cyber Infrastructure, Virtual Cyber Asset) and revisions to existing defined terms, needed so the CIP suite applies cleanly to virtualized infrastructure. This guide found no indication that CIP-006's R1-R3 substantive physical-security obligations change beyond that scoping update — confirm exact redlined wording against NERC's and FERC's own published CIP-006-7.1 text before compliance planning.
A workable starting point
Match access control strength to impact rating before anything elseA single physical access control (Part 1.2) is sufficient for Medium Impact systems with External Routable Connectivity, but High Impact systems need two or more different controls (Part 1.3) — confirm impact categorization under CIP-002 first, since it drives which Part 1 sub-requirements apply. Treat the 15-minute alarm window as a hard operational SLA, not a logging nicetyParts 1.5 and 1.7 require alerting "within 15 minutes of detection" to identified incident response personnel — this needs a tested notification path, not just a system capable of generating an alert. Don't confuse the 90-day log retention with the three-year evidence retentionR1 Part 1.9 and R2 Part 2.3 only require keeping the raw access/visitor logs for 90 days; the Compliance section separately requires evidence of each requirement for three calendar years — build a process that captures compliance evidence before the 90-day logs age out. Schedule PACS functional testing on a 24-month calendar, separate from access reviewsR3's test-and-maintain cycle is about hardware functioning correctly, not about who has access — a badge system with clean logs can still fail an R3 audit if it hasn't been tested in over two years. Start tracking CIP-006-7.1's Shared Cyber Infrastructure and Virtual Cyber Asset definitions nowWith a FERC-approved 1 July 2028 compliance date already set, entities planning virtualized access-control or monitoring infrastructure should evaluate the new Glossary terms ahead of the mandatory date rather than retrofitting afterward.
SoftWSP's OT asset assessments can help document the physical access control, visitor-log and PACS maintenance evidence CIP-006 requires: see OT Snapshot.
This guide quotes NERC's own published text of CIP-006-6 and the Federal Register text of FERC Order Nos. 822 and 919; it is not a substitute for the full standard, NERC's Implementation Plan, or compliance/legal advice. CIP-006-6 remains the enforceable standard as of this guide's publication — CIP-006-7.1 is approved but not yet mandatory.
Sources
- NERC: CIP-006-6 — Cyber Security – Physical Security of BES Cyber Systems (currently effective standard, full text: Purpose, Applicability, Requirements R1-R3 with Tables, Compliance, Evidence Retention)
- NERCipedia: CIP-006-6 — Cyber Security — Physical Security of BES Cyber Systems (standard summary, secondary corroboration of Purpose, Requirements and retention text)
- Federal Register: Order No. 822; Revised Critical Infrastructure Protection Reliability Standards, 81 FR 4177 (FERC, Docket No. RM15-14-000, issued 2016-01-21, published 2016-01-26) — approves CIP-006-6 among seven CIP v5 standards
- Federal Register: Order No. 919; Virtualization Reliability Standards, 91 FR 13957 (FERC, Docket No. RM24-8-000, issued 2026-03-19, published 2026-03-24, effective 2026-05-26) — lists CIP-006-7.1 among the 11 approved standards
- NERC: Standards, Compliance, and Enforcement Bulletin, 6-12 July 2026 — confirms CIP-006-7.1 becomes effective 1 July 2028
Frequently asked questions
What is NERC CIP-006-6, and who must comply?
CIP-006, "Cyber Security — Physical Security of BES Cyber Systems," is the mandatory, FERC-approved NERC Reliability Standard that governs how utilities and grid operators control physical access to BES Cyber Systems. Per its own Purpose clause, it exists "to manage physical access to Bulk Electric System (BES) Cyber Systems by specifying a physical security plan in support of protecting BES Cyber Systems against compromise that could lead to misoperation or instability in the Bulk Electric System (BES)." The currently enforceable version, CIP-006-6, was approved by FERC on 21 January 2016 in Order No. 822 (Docket No. RM15-14-000), published in the Federal Register at 81 FR 4177, and became effective and enforceable on 1 July 2016. It applies to Balancing Authorities, Distribution Providers meeting specific ownership criteria, Generator Operators and Owners, Interchange Coordinators/Authorities, Reliability Coordinators, and Transmission Operators and Owners, for High and Medium Impact BES Cyber Systems categorized under the separate [CIP-002](/guides/nerc-cip-002-bes-cyber-system-categorization/) process, plus their associated Physical Access Control Systems (PACS) and, for some parts, Electronic Access Control or Monitoring Systems (EACMS).
What does Requirement R1's Physical Security Plan actually require?
R1 requires one or more documented physical security plans covering ten parts (CIP-006-6 Table R1). Key obligations, quoted from the standard's own requirement table: Part 1.2 requires entities to "utilize at least one physical access control to allow unescorted physical access ... to only those individuals who have authorized unescorted physical access" for Medium Impact systems with External Routable Connectivity; Part 1.3 raises that to "two or more different physical access controls" for High Impact systems; Parts 1.4/1.5 require monitoring for unauthorized access through a physical access point and issuing an alarm or alert "within 15 minutes of detection"; Parts 1.6/1.7 require the same monitoring and 15-minute alerting for unauthorized access to the Physical Access Control System itself; Parts 1.8/1.9 require logging each authorized individual's entry (identity, date, time) and retaining those logs "for at least ninety calendar days"; and Part 1.10 requires restricting physical access to cabling and other nonprogrammable communication components, or — where that restriction isn't implemented — documenting and implementing an alternative such as encryption or alarmed monitoring.
What do Requirement R2 (Visitor Control) and R3 (PACS Maintenance) require?
R2 requires a visitor control program with three parts: Part 2.1 requires "continuous escorted access of visitors ... within each Physical Security Perimeter, except during CIP Exceptional Circumstances" for High and Medium Impact systems with External Routable Connectivity; Part 2.2 requires manual or automated logging of visitor entry and exit, including "date and time of the initial entry and last exit, the visitor's name, and the name of an individual point of contact"; and Part 2.3 requires retaining those visitor logs "for at least ninety calendar days." R3 requires "maintenance and testing of each Physical Access Control System and locally mounted hardware or devices at the Physical Security Perimeter at least once every 24 calendar months to ensure they function properly," for High Impact systems and Medium Impact systems with External Routable Connectivity. Per the Compliance section, evidence for all three requirements must be retained "for three calendar years."
Is CIP-006-6 already being replaced, and by when do entities need to comply?
Yes — a successor, CIP-006-7.1, is already FERC-approved, though CIP-006-6 remains the enforceable standard today. On 19 March 2026 the Federal Energy Regulatory Commission issued Order No. 919 (Docket No. RM24-8-000), published in the Federal Register on 24 March 2026 at 91 FR 13957, approving 11 modified CIP Reliability Standards as part of NERC's Project 2016-02 virtualization package — explicitly naming "CIP-006-7.1 (Cyber Security—Physical Security of BES Cyber Systems)" alongside CIP-002-7, CIP-003-10, CIP-004-8, CIP-005-8, CIP-007-7.1, CIP-008-7.1, CIP-009-7.1, CIP-010-5, CIP-011-4.1 and CIP-013-3. The order's own text states the final action "is effective May 26, 2026." NERC's own July 2026 Standards, Compliance, and Enforcement Bulletin confirms the resulting literal date, listing "CIP-006-7.1 – Cyber Security — Physical Security of BES Cyber Systems" among standards for which "the revised standards will become effective July 1, 2028."
In this cluster


