CIP-012 explained: protecting data between Control Centers
What CIP-012-2 requires: who it covers, protecting real-time data between Control Centers from disclosure, modification and loss, and the co-located exemption.
CIP-012 is one of the shortest NERC CIP standards: one requirement with five parts. It covers the data operators use to run the grid in real time, while that data travels between Control Centers.
Who it applies to
CIP-012-2 applies to Balancing Authorities, Generator Operators, Generator Owners, Reliability Coordinators, Transmission Operators and Transmission Owners that own or operate a Control Center.
One exemption matters most for generation: a Control Center that sends Real-time Assessment or Real-time monitoring data to another Control Center is exempt when that data pertains only to the generation resource or Transmission station or substation co-located with the transmitting Control Center. Facilities regulated by the Canadian Nuclear Safety Commission, and systems under the NRC cyber security rule (10 C.F.R. 73.54), are also exempt.
What R1 requires
R1 asks you to implement, except under CIP Exceptional Circumstances, one or more documented plans to mitigate the risks of unauthorized disclosure, unauthorized modification and loss of availability of data used in Real-time Assessment and Real-time monitoring while it is transmitted between applicable Control Centers. Oral communications do not have to be in the plan. The plan must include:
- 1.1: the methods used to mitigate unauthorized disclosure and modification of the data in transit.
- 1.2: the methods used to mitigate loss of the ability to communicate that data.
- 1.3: the methods used to initiate recovery of the communication links.
- 1.4: where the methods in 1.1 and 1.2 are implemented.
- 1.5: if the Control Centers belong to different entities, each entity's responsibilities under 1.1 to 1.3.
What changed from CIP-012-1
CIP-012-1 covered unauthorized disclosure and unauthorized modification only. CIP-012-2 adds loss of availability, which is where Parts 1.2 and 1.3 (keeping the data flowing and recovering the links) come from.
Examples the standard gives
The measures section lists examples, not requirements. For Part 1.1: data masking or encryption in transit, and physical access restrictions to unencrypted portions of the network. For Part 1.2: alternative communication paths or methods, procedures for using them, and service level agreements with carriers. A typical plan names each link, the protection on it, the backup path, and the agreement with the entity at the other end.
Evidence an auditor will look for
- The documented plan, with Parts 1.1 to 1.5 each answered.
- Proof it is implemented, such as configuration showing the protection on the named links, the backup path and the carrier agreement.
- For links shared with another entity, the written split of responsibilities.
- Records kept for three calendar years, per the standard's Evidence Retention section.
General guidance, not legal or compliance advice. The standard text at nerc.com is authoritative; the CIP-012-2 implementation plan sets its effective date.