The Purdue Model for ICS Security and Its Limits
The Purdue model explained level by level for ICS security, where the industrial DMZ fits, and where cloud, IIoT and remote access break the classic hierarchy.
Almost every OT security conversation eventually draws the same picture: a stack of numbered levels, with sensors at the bottom, the enterprise at the top, and a DMZ somewhere in between. That picture is the Purdue model. It is the shared vocabulary of plant engineers, integrators, vendors and security teams, and it is the starting point for most segmentation designs.
It is also more than 30 years old. This guide explains each level, how security people use the model, and where modern architectures no longer fit the hierarchy.
Where the model comes from
The Purdue model traces back to work at Purdue University on computer integrated manufacturing. NIST SP 800-82 Rev. 3 cites it as Theodore J. Williams' A Reference Model for Computer Integrated Manufacturing (CIM), published by the Instrument Society of America in 1989. That work grew into the Purdue Enterprise Reference Architecture (PERA). The functional hierarchy was later formalized in ISA-95, published internationally as IEC 62264, which defines the levels of enterprise and control integration that manufacturing systems (MES, ERP) still use today.
Important point: the original model was a functional reference for integrating manufacturing systems, not a security architecture. Security practitioners adopted its levels as a way to describe where systems sit and which levels should talk to each other.
The levels
The numbering below is the common security usage. Exact names vary between sources.
Level 0: physical process
Sensors, actuators, drives, valves, motors and instruments. They measure and move the physical world. Traditionally connected by 4 to 20 mA loops, discrete wiring or fieldbuses (HART, PROFIBUS, Foundation Fieldbus), and increasingly by Ethernet-based protocols such as EtherNet/IP, PROFINET and IO-Link masters. NIST SP 800-82 Rev. 3 has a dedicated section on "Field I/O (Purdue Level 0) Security Considerations", noting that many devices and protocols at this level have no authentication.
Level 1: basic control
The controllers that read inputs and drive outputs: PLCs, DCS controllers, RTUs, protection relays and safety instrumented system (SIS) logic solvers. Safety systems are often drawn as a separate zone alongside level 1 because they must remain independent from the basic process control system.
Level 2: area supervisory control
What operators look at and use: HMIs, SCADA servers for an area, operator workstations, alarm servers, and often engineering workstations used to program the controllers in that area.
Level 3: site operations
Site-wide functions: historians, manufacturing execution systems (MES), batch management, site-level SCADA, OT domain controllers, patch and antivirus servers for OT, backup servers and the central engineering workstations.
Level 3.5: industrial DMZ
Not part of the original model. The industrial demilitarized zone (IDMZ) was added by industry practice as a buffer between site operations and the enterprise. No traffic should cross it directly. Instead, it hosts brokered services: a historian replica that business users query, a remote access gateway and jump host, patch and antivirus staging servers, and file transfer services. See OT network segmentation and the industrial DMZ for a concrete design.
Levels 4 and 5: enterprise
Business logistics (ERP, email, planning) at level 4 and the corporate network and internet-facing services at level 5. Many diagrams merge these into one enterprise zone.
How security teams use the model
The model gives you three practical tools.
A location for every asset. When you build an inventory, recording the Purdue level of each asset tells you how close it is to the physical process and how much damage its compromise could cause. See OT asset inventory.
A default rule for traffic. The common rule of thumb is that communication should only flow between adjacent levels, and that nothing should pass directly between level 4 and levels 3 or below. A firewall policy derived from the model might look like this:
| Source | Destination | Allowed example |
|---|---|---|
| Level 4 | Level 3.5 | HTTPS to historian replica, RDP gateway with MFA |
| Level 3.5 | Level 3 | Historian replication, jump host to engineering workstation |
| Level 3 | Level 2 | Historian collector pulling from SCADA, OT domain services |
| Level 2 | Level 1 | HMI polling PLCs over the vendor protocol |
| Level 4 | Level 3 or below | Nothing |
A shared language. "Is that a level 2 or a level 3 system?" is a question both a control engineer and a firewall administrator understand. That alone makes the model valuable in cross-functional work.
Mapping Purdue to IEC 62443 zones
IEC 62443 does not mandate Purdue levels. It asks you to group assets into zones with common security requirements and to define conduits for the communication between them. In practice, many sites start by turning Purdue levels into zones and then split further:
- by process area or production line, so an incident in one line does not reach another,
- by criticality, for example a separate zone for the SIS,
- by trust, for example a zone for vendor-managed packaged units.
Each zone gets a target security level based on risk. The Purdue model gives you the vertical structure; IEC 62443 gives you the method for deciding boundaries and requirements. See IEC 62443 explained.
Where the model breaks down
The model assumes a hierarchical plant where data moves up one level at a time and every connection is wired, on-premises and owned by the asset owner. Modern sites often look different.
Cloud and IIoT data paths
Industrial IoT sensors, edge gateways and vendor analytics platforms frequently send data directly to a cloud service, skipping levels 2 to 4. A vibration sensor at level 0 that publishes MQTT to a cloud broker over a cellular link does not fit any adjacent-level rule. NIST SP 800-82 Rev. 3 addresses this by showing the Purdue model side by side with a three-tier IIoT architecture (edge, platform, enterprise) rather than forcing one into the other.
What to do: treat each IIoT path as its own conduit. Document it, require outbound-only connections initiated from the OT side, terminate them on a dedicated gateway in a controlled zone, and verify that the cloud path cannot be used to write back to controllers unless that is a designed and risk-assessed function.
Remote access everywhere
Vendors and integrators expect remote support. Cellular routers installed in a cabinet by a machine builder create a direct path from the internet to level 1. The Purdue diagram on the wall rarely shows them. Finding and controlling these paths matters more than perfecting the level boundaries. See secure remote access for OT vendors.
Smart field devices
Level 0 used to be dumb. Today drives, analyzers, smart instruments and safety devices have Ethernet ports, web servers and firmware. The line between level 0 and level 1 is blurred, and devices at the bottom of the stack can be targets in their own right.
Virtualization and converged infrastructure
SCADA servers, HMIs and historians increasingly run as virtual machines on shared hypervisors, and some vendors offer virtual or software-defined controllers. A single cluster can host workloads from levels 2, 3 and 3.5. The hypervisor management network then becomes a path around your level boundaries. Keep management interfaces in their own zone and do not let VMs from different levels share uncontrolled virtual switches.
Flat networks in practice
Many brownfield sites never implemented the levels. A single flat layer 2 network with HMIs, PLCs and an office printer is still common. The Purdue model describes the target, not the current state, so start from what the traffic actually shows.
Lateral movement is not vertical
The model focuses on north-south flows. Real attacks also move east-west: from one HMI to all PLCs in the area, or from one production line to another. Segment within levels as well as between them.
Is the Purdue model obsolete?
Some vendors argue that zero trust and cloud architectures make the Purdue model obsolete. A more useful position is that the model is a reference, not a rule.
Keep it for:
- describing where assets sit and how close they are to the physical process,
- explaining why the enterprise should never talk directly to controllers,
- structuring the first cut of segmentation and the industrial DMZ.
Supplement it with:
- IEC 62443 zones and conduits for risk-based boundaries,
- explicit documentation of every non-hierarchical path (cloud, cellular, vendor),
- identity-based access controls for people and applications, which do not depend on network position alone,
- monitoring of east-west traffic within levels.
The 2015 Ukraine attack, described in ICS attack case studies, is a good test of a design. The attackers moved from the enterprise network into control systems using stolen credentials and VPN access, then operated breakers through the SCADA tools. Ask of your own design: which conduit would they have used, and what would have stopped or detected them there?
Quick checklist
- Draw your real network next to the Purdue reference, and mark every difference.
- Assign a level and a zone to every asset in your inventory.
- List every flow that crosses more than one level, and justify or remove it.
- Ensure nothing crosses from level 4 to level 3 or below without terminating in the IDMZ.
- Document cloud, IIoT, cellular and vendor paths as explicit conduits.
- Add east-west segmentation within level 2 and level 1 where the process allows it.
Next, see how the protocols at levels 1 and 2 behave in ICS protocol security, and how NIST frames architecture in the NIST SP 800-82 overview.
References
- NIST SP 800-82 Rev. 3, Guide to Operational Technology (OT) Security (section 5, OT Cybersecurity Architecture)
- ISA-95 Series of Standards: Enterprise-Control System Integration (ISA)
- ISA/IEC 62443 Series of Standards (ISA)
- CISA: ICS Recommended Practices
- MITRE ATT&CK for ICS: Network Segmentation mitigation (M0930)
- MITRE ATT&CK for ICS: 2015 Ukraine Electric Power Attack (C0028)