Skip to main content
Intelligent Security Governance — 340+ Frameworks Powered by Ayurak AI
Blog/Compliance Guides

NERC CIP-014 (Physical Security): Requirements and Compliance Guide

CIP-014 is the NERC reliability standard for physical security of critical transmission stations, substations and control centers. Here is who it covers, what R1-R6 require and how to prepare.

NERC CIP-014 (Physical Security): Requirements and Compliance Guide

NERC CIP-014 is the one standard in the NERC CIP family that deals with physical attacks on the grid itself, not on cyber assets. It requires owners and operators of the most critical transmission stations, substations and control centers to find out which of them matter most, assess the threats to them and carry out a physical security plan that has been independently reviewed. This article covers only CIP-014, not the wider CIP suite.

What it is

CIP-014 is titled "Physical Security." It is a mandatory reliability standard developed by the North American Electric Reliability Corporation (NERC) and approved by the U.S. Federal Energy Regulatory Commission (FERC). It exists because of the 2013 attack on a California transmission substation. After that incident FERC directed NERC to develop a standard to protect against physical attacks that could cause widespread instability or cascading outages on the bulk power system.

The standard has been revised since its first approval. Check NERC's current standards listing for the version in force and any pending revisions before you write procedures against a specific version.

CIP-014 is risk-based and outcome-focused. It does not prescribe fences, cameras or guard staffing. It prescribes a process: identify critical facilities, verify that identification, evaluate threats, write a plan and have the evaluation and plan reviewed by a qualified third party. The security measures themselves are up to the entity, as long as they can be defended.

Who it applies to

The standard applies to specific registered entities in the bulk power system, mainly:

  • Transmission Owners that own certain transmission stations and substations, together with their associated primary control centers.
  • Transmission Operators that operate a primary control center with operational control of an identified transmission station or substation.

Applicability depends on the facility, not only the company. The standard's applicability section uses criteria such as transmission voltage class, how a station connects to other stations, and an aggregate weighted value assigned through a table in the standard. It also covers facilities that a Planning Coordinator has identified as critical to the derivation of Interconnection Reliability Operating Limits. Read the current applicability section and the associated table directly to see whether your facilities are in scope; do not rely on a summary.

NERC standards apply across the interconnected North American system, including parts of Canada, where they are adopted through provincial authorities. FERC's enforcement role covers the U.S. portion. A Transmission Owner can be subject to CIP-014 at only a few facilities, or at none. The first step of compliance is establishing that.

Key requirements

CIP-014 is organized as six requirements. They form a sequence in which each step depends on the output of the previous one.

R1: Risk assessment

The Transmission Owner performs an initial risk assessment, then repeats it at intervals set in the standard. It identifies the transmission stations and substations (and their primary control centers) that, if rendered inoperable or damaged, could lead to widespread instability, uncontrolled separation or cascading within an interconnection. The analysis is usually a transmission planning study, so it draws on power-system engineering expertise as well as security.

R2: Third-party verification of the risk assessment

An entity unaffiliated with the Transmission Owner must verify the R1 assessment. The standard lists who qualifies, such as certain registered planning or operating entities, or a third party with demonstrated transmission planning or analysis experience. The owner must also address the reviewer's recommendations, by changing the list or by documenting why it did not.

R3: Notification to control center operators

If the Transmission Owner does not operate the primary control center for an identified facility, it must notify the Transmission Operator that does, within a short, fixed window. This lets the operator evaluate its own obligations. Once notified, operators of an identified primary control center have their own obligations under R4 to R6.

R4: Threat and vulnerability evaluation

For each identified facility, the owner or operator evaluates the potential threats and vulnerabilities of a physical attack. The standard names factors to consider, including the unique characteristics of the facility, prior history of attacks on similar facilities (taking into account frequency, geographic proximity and severity), and intelligence or threat warnings from sources such as the E-ISAC, law enforcement and government agencies. The evaluation is specific to each site.

R5: Physical security plan

The owner or operator develops and implements a documented physical security plan covering each identified facility, within a set period after the third-party verification is complete. The plan must include resiliency or security measures designed collectively to deter, detect, delay, assess, communicate and respond to physical threats. It should also include a timeline for implementing the plan and link back to the R4 evaluation. Plans are expected to show why a given measure addresses an identified threat.

R6: Third-party review of the evaluation and plan

An unaffiliated reviewer with appropriate expertise (the standard describes acceptable categories, which include experience in physical security of this kind) reviews the R4 evaluation and R5 plan. The owner must address the recommendations or document why it did not. The standard also requires procedures to protect sensitive or confidential information produced by these steps.

The handling of information deserves attention. The list of critical facilities and the security plans are sensitive by design, so CIP-014 evidence has to be controlled much more tightly than the evidence of most other standards.

Assessment, audit and enforcement

CIP-014 is enforced under the reliability provisions of the Federal Power Act. NERC oversees the Regional Entities, which carry out compliance monitoring: audits, spot checks, self-reports and self-certifications. FERC retains oversight of the standards and can enforce them. Violations can lead to financial penalties and mitigation requirements under the NERC Compliance Monitoring and Enforcement Program. Penalty size depends on the violation's severity and other factors; consult the program documents for specifics.

Auditors will look for evidence at each step: the R1 assessment and its inputs, the verifier's qualifications and written findings, how recommendations were handled, dated threat evaluations, the security plan and proof of implementation, and the notifications under R3. Because the standard is process-driven, missed deadlines between steps and undocumented dispositions of reviewer comments are common weak points.

Audit teams also commonly check how entities protect the sensitive material itself. Expect questions on who has access to the list of identified facilities and to the security plans.

A practical path to meeting CIP-014

  1. Confirm applicability. Check your NERC registration and test each station, substation and control center against the standard's applicability criteria. Record the conclusion, including for facilities you find out of scope.
  2. Assign ownership. Name leads from transmission planning, physical security, operations and compliance. R1 needs system-study skills, and R4 and R5 need security expertise.
  3. Run and document the R1 assessment. Keep the study inputs, methodology, assumptions and results, and set a calendar for the next required assessment.
  4. Select a qualified verifier. Check the candidate against the standard's criteria and your own independence rules, and keep evidence of qualifications. Allow time for review and for responding to recommendations.
  5. Handle notifications. If another entity operates the control center, send and record the R3 notice within the deadline.
  6. Evaluate threats per site. Collect incident history, local crime and intelligence data, and site vulnerabilities, such as access, line of sight to critical equipment and response times. Document how each factor was weighed.
  7. Write the physical security plan. Tie each measure to a threat and a function (deter, detect, delay, assess, communicate, respond). Include an implementation schedule and owners.
  8. Obtain the R6 review. Respond to each recommendation in writing, either by adopting it or by documenting why not.
  9. Implement and keep evidence. Track completion of plan items, and keep dated records of installations, drills, maintenance and changes.
  10. Protect and re-run. Restrict access to the sensitive records, and re-run the cycle on the standard's schedule or after a significant change in the grid or threat picture.

How it maps to other frameworks

CIP-014 overlaps with other frameworks only in part, and none is equivalent.

  • Other NERC CIP standards: CIP-006 covers physical access controls for BES Cyber Systems, which is a different scope. CIP-014 concerns the physical vulnerability of whole facilities to attack. Evidence such as access logs may be reused, but the obligations do not substitute for each other. CIP-002 (BES Cyber System categorization) uses its own impact criteria and is a separate process from the R1 risk assessment, although the analyses can inform each other.
  • ISO 27001: The physical and environmental controls in Annex A address facility protection in general terms. They do not require a grid-impact study or independent verification.
  • NIST CSF: The Protect and Identify functions share themes with CIP-014's risk and protective measures. The overlap is conceptual only.
  • SOC 2: Physical access criteria exist, but the scope is service-organization systems, not grid facilities.

FAQs

Is CIP-014 a cybersecurity standard?

No. It addresses physical attacks on transmission stations, substations and primary control centers. Cybersecurity for the grid is covered by other CIP standards.

Does it apply to every substation?

No. It applies only to facilities that meet the applicability criteria and that the R1 risk assessment identifies as critical. Many owners have few or no identified facilities.

Who can be the third-party verifier?

The standard lists acceptable categories of unaffiliated entities and individuals, based on registration or demonstrated expertise. Check the current text, and document why your choice qualifies.

Do I have to follow every reviewer recommendation?

No, but you must address each one. That means either changing your assessment or plan, or documenting why you did not.

Can I share my CIP-014 documents with auditors by email or a shared drive?

The standard requires procedures to protect sensitive information. Use controlled channels and limit access, and agree on handling with your Regional Entity before the audit.

How Aristiun helps

Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. CIP-014 work is document-heavy and sequential, and the same capabilities that support other compliance frameworks apply to its evidence trail and threat analysis.

  • Evidence collection and audit-ready reports: gather evidence automatically from connected systems and generate auditor-friendly reports with evidence pre-mapped to controls and organized by framework requirements.
  • Gap analysis and control monitoring: check that evidence meets auditor expectations, spot gaps early and get alerts when controls drift.
  • Cross-framework mapping: map controls across 340+ frameworks so shared evidence supports several obligations from a single evidence base.
  • Automated threat modeling: generate threat models from code, IaC and architecture diagrams using methodologies such as STRIDE, PASTA, LINDDUN and MAESTRO, which can complement the security analysis around connected systems.

Found this insightful?

Share it with your security team or save it for later.

Get Started

Ready to secure your organization?

See how Aristiun automates compliance and strengthens your security posture across 340+ frameworks.