CIE and NERC CIP: Compliance Is the Floor, Engineering Is the Structure

High-voltage transmission towers leading to a lit campus on the horizon

CIE and NERC CIP: Compliance Is the Floor, Engineering Is the Structure

NERC CIP tells a utility which cyber systems to protect and how to prove it. Cyber-Informed Engineering asks whether the grid asset can be made to hurt itself at all.

By Timothy Porritt · Porritt Inc. · November 21, 2026

For any registered entity on the North American bulk power system, cybersecurity begins with the NERC Critical Infrastructure Protection standards. They are mandatory, audited, and enforceable with substantial penalties. So when Cyber-Informed Engineering comes up, the first question from a utility is usually the practical one: is this another set of requirements, or does it help with the ones we already have?

The short answer is that CIE is not a compliance framework and creates no audit obligations. It addresses a different question from CIP, and the two work best together.

What NERC CIP Does

The CIP standards require entities to identify and categorize their BES Cyber Systems by impact, then apply controls scaled to that impact. Those controls cover security management, personnel and training, electronic security perimeters, physical security, system hardening and patching, incident response, recovery planning, configuration change management, information protection, and supply chain risk management, with a separate standard for the physical security of the most critical transmission stations.

The model is asset-centered and evidence-driven. An entity succeeds by showing that defined controls were applied to defined systems.

What CIP Leaves to Engineering

CIP does not ask whether a protection scheme should be remotely re-settable, whether a station could be operated safely with its automation untrusted, or whether a legitimate but malicious command could damage a transformer or generator. Those are design questions. A facility can be fully compliant and still have a single digital path to a severe physical outcome.

Categorization also draws lines. Low-impact assets carry lighter requirements, yet many low-impact stations acting together, or a large population of distributed resources, can add up to a consequence the categorization of each one does not capture.

Where the Two Overlap

CIE principle Related CIP subject area
Digital asset awareness BES Cyber System identification and categorization
Secure information architecture Electronic security perimeters and remote access
Engineering information control Information protection
Cyber-secure supply chain controls Supply chain risk management
Active defense and planned resilience Incident response and recovery planning
Consequence-focused design, engineered controls, design simplification No direct equivalent

The last row is the point. The principles with no CIP counterpart are the ones that change the physical design.

How CIE Can Reduce Compliance Burden

Design choices made for CIE reasons often shrink CIP scope. Removing unneeded routable connectivity, eliminating remote access that operations does not use, and simplifying station architecture all reduce the number of systems and interfaces that must be documented, monitored, and audited. Fewer digital functions means fewer controls to evidence.

A Practical Way to Combine Them

  • Use the existing CIP asset inventory as the starting list for a consequence review, then extend it to low-impact and non-BES systems that share technology or staff.
  • For each high-consequence function, record the engineered control that backs it up, alongside the CIP controls that protect it.
  • Bring protection, substation design, and operations engineers into the review, not only the compliance group.
  • Feed findings into design standards, so the next station is built with them instead of audited into them.

Why It Matters

Standards move through a deliberate development and approval process and will always trail the threat. Engineering decisions made in a design review take effect on the next project. Utilities that treat CIP as the floor and CIE as the structure above it get protection that does not depend on the standard catching up.

For the utility design perspective see CIE for Utilities; for the full list of principles see The INL CIE Framework Explained.

Related reading


Timothy Porritt is founder of Porritt Inc., building AI-powered tools for process safety, engineering compliance, and industrial operations. Based in Salt Lake City, Utah. Questions about applying Cyber-Informed Engineering to a specific facility: timothy@porrittinc.com.

Scroll to Top