Key takeaways
- CIP-012-2 did not originate from an industry-identified weakness — FERC created the mandate for it the moment it approved the prior version.
- Treat Parts 1.2 and 1.3 as new obligations, not refinements.
NERC CIP-012-2, "Cyber Security — Communications between Control Centers," is the mandatory, FERC-approved Reliability Standard protecting the data Control Centers exchange with each other — the only CIP standard focused specifically on inter-Control-Center communications rather than a single facility's cyber assets. Per its own Purpose clause, it exists "to protect the confidentiality, integrity, and availability of Real-time Assessment and Real-time monitoring data transmitted between Control Centers." CIP-012-2 was adopted by the NERC Board of Trustees on 12 December 2023 under Project 2020-04 and approved by FERC on 23 May 2024 (Docket No. RD24-3-000); per NERC's own implementation plan, it became effective 1 July 2026, retiring its predecessor, CIP-012-1, in the process — meaning CIP-012-2, not CIP-012-1, is the version currently enforceable as of this guide's publication.
Who must comply
CIP-012 applies to Balancing Authorities, Generator Operators, Generator Owners, Reliability Coordinators, Transmission Operators and Transmission Owners — collectively "Responsible Entities" — that own or operate a Control Center. Three exemptions apply: Cyber Assets at facilities regulated by the Canadian Nuclear Safety Commission; systems, structures and components regulated by the U.S. Nuclear Regulatory Commission under 10 C.F.R. § 73.54; and a Control Center that transmits Real-time Assessment or Real-time monitoring data pertaining only to a generation resource or Transmission station/substation co-located with it.
Requirement R1: the five-part plan
R1 requires each Responsible Entity to implement, except under CIP Exceptional Circumstances, "one or more documented plan(s) to mitigate the risks posed by unauthorized disclosure, unauthorized modification, and loss of availability, of data used in Real-time Assessment and Real-time monitoring while such data is being transmitted between any applicable Control Centers." The Responsible Entity is not required to include oral communications in its plan. Violation Risk Factor is Medium, with a Time Horizon of Operations Planning.
| Part | Requirement | Example evidence per the standard's own Measures |
|---|---|---|
| 1.1 | Methods mitigating unauthorized disclosure and modification of the data in transit | "data masking, encryption/decryption"; physical access restrictions to unencrypted portions of the network |
| 1.2 | Methods mitigating the risk of losing the ability to communicate the data at all | Alternative communication paths; procedures for alternative systems; carrier service-level agreements with high-availability provisions; equipment uptime reports |
| 1.3 | Methods to initiate recovery of communication links | Standard operating procedures; "applicable sections of CIP-009 recovery plan(s)"; vendor contact procedures to initiate/verify restoration |
| 1.4 | Identification of where Parts 1.1 and 1.2 methods are implemented | Logical diagrams; identification of infrastructure points; third-party agreements where methods are implemented by a third party |
| 1.5 | If Control Centers are owned or operated by different Responsible Entities, identification of each entity's responsibilities for Parts 1.1-1.3 | Contracts, memoranda of understanding, meeting minutes, or other agreements |
Per the Compliance section, Responsible Entities "shall keep data or evidence of each Requirement in this Reliability Standard for three calendar years," and if found non-compliant, must retain non-compliance-related information until mitigation is complete and approved, whichever is longer.
Why CIP-012-2 exists: FERC's own availability gap
CIP-012-2 did not originate from an industry-identified weakness — FERC created the mandate for it the moment it approved the prior version. On 23 January 2020, FERC approved CIP-012-1 in Order No. 866 (Docket No. RM18-20-000), but found that the standard "did not address protections for the availability of communications links and data communicated between Control Centers." Per NERC's own implementation plan, FERC's order directed NERC to "develop modifications to the CIP Reliability Standards to require protections regarding the availability of communication links and data communicated between bulk electric system Control Centers." CIP-012-1's Requirement R1 had only three parts — identification of security protection, where it was applied, and cross-entity responsibilities — covering disclosure and modification but not availability at all.
CIP-012-2 directly answers that directive: its Purpose clause adds the word "availability" alongside confidentiality and integrity, and Requirement R1 grows from three parts to five, inserting Part 1.2 (loss-of-communication mitigation) and Part 1.3 (recovery-initiation methods) between the original disclosure/modification part and the where-implemented/responsibilities parts that carried over from CIP-012-1.
When CIP-012-2 took effect, and what retired
Per NERC's implementation plan, Reliability Standard CIP-012-2 "shall become effective on the first day of the first calendar quarter that is twenty-four (24) calendar months after the effective date of the applicable governmental authority's order approving the standard, or as otherwise provided for by the applicable governmental authority." FERC approved CIP-012-2 on 23 May 2024; 24 months later lands in late May 2026, so the next calendar-quarter start — 1 July 2026 — is the resulting effective date, a figure corroborated by multiple industry NERC CIP compliance trackers. This guide was unable to independently fetch FERC's approval order itself to confirm its own stated effective date, so treat the exact day-level mechanics as sourced to NERC's implementation-plan formula plus secondary corroboration rather than a directly quoted FERC order text.
The same implementation plan specifies that "Reliability Standard CIP-012-1 shall be retired immediately prior to the effective date of CIP-012-2 in the particular jurisdiction in which the revised standard is becoming effective" — so as of this guide's publication, CIP-012-1 is retired and CIP-012-2 is the sole enforceable version.
A workable starting point
Treat Parts 1.2 and 1.3 as new obligations, not refinementsIf a Responsible Entity's CIP-012 plan was built against CIP-012-1, it almost certainly addresses disclosure and modification (today's Part 1.1) but has no documented method for loss-of-availability mitigation or recovery initiation — gaps an auditor checking against CIP-012-2 will look for directly. Reuse CIP-009 recovery plan content for Part 1.3 where it already covers the relevant linksThe standard's own Measures name "applicable sections of CIP-009 recovery plan(s)" as acceptable evidence, so a CIP-009 recovery plan that already addresses the communication links in question may not need a separate CIP-012 artifact. Document cross-entity responsibilities (Part 1.5) explicitly wherever Control Centers are owned or operated by different Responsible Entities— a gap here is one of the more straightforward compliance findings, since the standard requires a clear allocation in writing, not an assumption that "someone" handles it. Confirm which standard your evidence was built againstGiven the 1 July 2026 effective date, any CIP-012 documentation that predates mid-2026 should be reviewed against CIP-012-2's five-part structure rather than assumed compliant under the retired three-part CIP-012-1 structure.
SoftWSP's OT asset assessments can help document the confidentiality, integrity and availability controls CIP-012-2 requires for Real-time Assessment and Real-time monitoring data: see OT Snapshot.
This guide quotes NERC's own published text of CIP-012-2, CIP-012-1, and NERC's Project 2020-04 implementation plan; it is not a substitute for the full standard, NERC's implementation plan, or compliance/legal advice.
Sources
- NERC: CIP-012-2 — Cyber Security – Communications between Control Centers (currently effective standard, full text: Purpose, Applicability, Requirement R1 with Parts 1.1-1.5 and Measures, Compliance, Version History)
- NERC: CIP-012-1 — Cyber Security – Communications between Control Centers (retired predecessor standard, full text, for comparison)
- NERC: Implementation Plan, Project 2020-04 Modifications to CIP-012-2 (November 2023) — FERC Order No. 866 background/directive quote, effective-date formula, CIP-012-1 retirement clause
Frequently asked questions
What is NERC CIP-012-2, and who must comply?
CIP-012, "Cyber Security — Communications between Control Centers," is the mandatory, FERC-approved NERC Reliability Standard protecting the data Control Centers exchange with each other. Per its own Purpose clause, the currently enforceable version, CIP-012-2, exists "to protect the confidentiality, integrity, and availability of Real-time Assessment and Real-time monitoring data transmitted between Control Centers." It applies to Balancing Authorities, Generator Operators, Generator Owners, Reliability Coordinators, Transmission Operators and Transmission Owners — collectively "Responsible Entities" — that own or operate a Control Center. Three exemptions apply: Cyber Assets at facilities regulated by the Canadian Nuclear Safety Commission; systems regulated by the U.S. Nuclear Regulatory Commission under 10 C.F.R. § 73.54; and a Control Center that transmits data pertaining only to a generation resource or Transmission station/substation co-located with it. CIP-012-2 was adopted by the NERC Board of Trustees on 12 December 2023 under Project 2020-04 and approved by FERC on 23 May 2024 (Docket No. RD24-3-000); per NERC's own implementation plan, it became effective 1 July 2026, at which point its predecessor, CIP-012-1, retired.
What does Requirement R1's five-part plan actually require?
R1 requires each Responsible Entity to implement, except under CIP Exceptional Circumstances, "one or more documented plan(s) to mitigate the risks posed by unauthorized disclosure, unauthorized modification, and loss of availability, of data used in Real-time Assessment and Real-time monitoring while such data is being transmitted between any applicable Control Centers" — oral communications are explicitly excluded. The plan must include five parts: Part 1.1, identification of methods mitigating unauthorized disclosure and modification (the standard's own Measures cite examples such as "data masking, encryption/decryption" and physical access restrictions to unencrypted network segments); Part 1.2, identification of methods mitigating the risk of losing the ability to communicate the data at all — an availability control with no equivalent in the prior version; Part 1.3, identification of methods to "initiate the recovery of communication links," for which the standard's Measures explicitly point to applicable sections of a [CIP-009](/guides/nerc-cip-009-recovery-plans/) recovery plan as acceptable evidence; Part 1.4, identification of where the Part 1.1/1.2 methods are implemented; and Part 1.5, where Control Centers are owned or operated by different Responsible Entities, identification of each entity's responsibilities for Parts 1.1-1.3. Violation Risk Factor is Medium, and per the Compliance section, Responsible Entities "shall keep data or evidence of each Requirement in this Reliability Standard for three calendar years."
How is CIP-012-2 different from CIP-012-1, and why did it change?
CIP-012-1's Purpose was narrower — "to protect the confidentiality and integrity" only — and its Requirement R1 had just three parts covering disclosure/modification protection, where it was applied, and cross-entity responsibilities, with no availability obligation. FERC itself created the gap that CIP-012-2 closes: in approving CIP-012-1 on 23 January 2020 (Order No. 866, Docket No. RM18-20-000), FERC found that the standard "did not address protections for the availability of communications links and data communicated between Control Centers" and, per NERC's own implementation plan, directed NERC to "develop modifications to the CIP Reliability Standards to require protections regarding the availability of communication links and data communicated between bulk electric system Control Centers." CIP-012-2 directly answers that directive by adding the word "availability" to the Purpose clause and adding Parts 1.2 and 1.3 (loss-of-communication mitigation and recovery-initiation methods) to Requirement R1. Per NERC's implementation plan, CIP-012-2 became effective "on the first day of the first calendar quarter that is twenty-four (24) calendar months after the effective date of the applicable governmental authority's order approving the standard" — 23 May 2024 plus 24 months lands in late May 2026, so the next calendar-quarter start is 1 July 2026, a date corroborated by multiple industry compliance trackers though this guide was unable to independently fetch FERC's approval order to confirm its own stated effective date. The same implementation plan retires CIP-012-1 "immediately prior to the effective date of CIP-012-2" in each jurisdiction.
In this cluster


