The INL CIE Framework Explained: The 12 Principles in Working Terms

National laboratory campus at dusk

The INL CIE Framework Explained: The 12 Principles in Working Terms

Idaho National Laboratory’s Cyber-Informed Engineering framework rests on twelve principles. Here is what each one asks an engineering team to do.

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

Idaho National Laboratory’s CIE Implementation Guide organizes Cyber-Informed Engineering into twelve principles. The first group concerns design and operations; the second concerns the organization around the system. The guide pairs each principle with questions to ask at every phase of a system’s life, from concept through retirement. What follows is each principle translated into the question it puts to a working engineer.

Design and Operational Principles

1. Consequence-Focused Design

What are the worst outcomes this system could produce, and which of them can a digital failure or attack cause? Everything else in CIE is prioritized from this answer.

2. Engineered Controls

For each of those outcomes, is there a control that does not depend on software: a relief valve, a mechanical stop, a hardwired trip? Prefer eliminating or physically limiting the hazard over adding a digital safeguard.

3. Secure Information Architecture

Which data flows does the function truly need, in which direction, and who can change what? Design the paths deliberately instead of connecting everything and restricting later.

4. Design Simplification

What features, protocols, ports, and devices are present but not required? Remove them. A function that does not exist cannot be misused.

5. Resilient Layered Defenses

If one protective layer is defeated, does the next one fail the same way? Layers that share a network, a vendor, or an engineering tool are less independent than the drawing suggests.

6. Active Defense

If something abnormal is happening in the control system, who would notice, how quickly, and what are they authorized to do about it? Plan the response before it is needed.

Organizational Principles

7. Interdependency Evaluation

What does this system need from others, and what do others need from it? Power, communications, water, fuel, and shared services can carry a failure across boundaries.

8. Digital Asset Awareness

Do you know every programmable device in the system, what it can command, and what firmware it runs? You cannot reason about consequences from an incomplete inventory.

9. Cyber-Secure Supply Chain Controls

What do procurement documents require of vendors and integrators, and how is it verified? Security properties not written into the specification rarely appear in the delivered system.

10. Planned Resilience

If the digital system is unavailable or untrusted, can the facility keep its critical function running in a degraded mode, and for how long? This is the principle that keeps manual operation alive. We look at it in Mission Assurance for Industrial Plants.

11. Engineering Information Control

Who can see the drawings, settings files, logic, and network diagrams? Detailed engineering records are a map for an attacker and deserve handling rules of their own.

12. Cybersecurity Culture

Does everyone who touches the system, from designers to maintenance contractors, understand that their decisions affect its security? The other eleven principles depend on this one.

How the Principles Are Used

The principles are not a scoring system or a certification. They are prompts for design reviews. A team does not need to address all twelve at once; a first pass through the first four on a single critical system usually surfaces the most valuable changes.

Why It Matters

The value of the framework is that it gives engineers and security staff a shared vocabulary. A statement like “this trip has no engineered control behind it” is something a process engineer, a controls engineer, and a security analyst can all act on.

The Relationship to CCE

INL also developed Consequence-driven Cyber-informed Engineering (CCE), a four-phase method: consequence prioritization, system-of-systems analysis, consequence-based targeting, and mitigations and protections. CCE is an intensive assessment for an organization’s most critical functions; the twelve CIE principles are the broader practice meant for everyday engineering work.

For an introduction see What Is Cyber-Informed Engineering?; to put the principles to work, use the CIE Implementation Checklist.

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