Explained with a diagram · Industrial control systems
Purdue model: the levels of an industrial network, with a diagram
In short
The Purdue model is a reference model that arranges an industrial organisation's systems into hierarchical levels, from sensors and actuators at Level 0 up to the enterprise network at Level 5. Levels 0 to 3 are operational technology (OT), Levels 4 and 5 are information technology (IT), and a demilitarized zone (DMZ), often called Level 3.5, separates the two. It comes from the Purdue Enterprise Reference Architecture (PERA), developed in the early 1990s by Theodore J. Williams and the Industry-Purdue University Consortium for Computer Integrated Manufacturing, and it is widely used as a framework for segmenting industrial control system networks.
Updated · by the ChartCraft team · one of the patterns and models explained with a diagram
What does the Purdue model look like as a diagram?
The Purdue model is drawn as a vertical stack. The enterprise network is at the top, the physical process and its field devices are at the bottom, and a DMZ sits between the business network (Level 4) and site operations (Level 3). Each level talks only to the level directly above or below it.
Mermaid code for this diagram
flowchart TD
subgraph it["Information technology (IT): Levels 4 and 5"]
level5["Level 5: Enterprise network"]
level4["Level 4: Business network (site IT)"]
end
subgraph boundary["IT/OT boundary"]
dmz["DMZ (Level 3.5): firewalls, jump servers"]
end
subgraph ot["Operational technology (OT): Levels 0 to 3"]
level3["Level 3: Site operations (MES, historians)"]
level2["Level 2: Supervisory control (HMI, SCADA)"]
level1["Level 1: Controllers (PLCs, RTUs)"]
level0["Level 0: Field devices (sensors, actuators)"]
end
level5 -->|"enterprise WAN"| level4
level4 -->|"firewall"| dmz
dmz -->|"firewall"| level3
level3 --> level2
level2 --> level1
level1 --> level0
Paste it into any Mermaid renderer, or check and export it with the Mermaid syntax checker and Mermaid to PNG.
What are the levels of the Purdue model?
There are six levels, numbered 0 to 5, plus the DMZ between Levels 3 and 4. Moving down the stack, devices have more direct access to the physical process and fewer security features of their own.
| Part of the diagram | What it is | What it does |
|---|---|---|
| Level 5: Enterprise network | Enterprise IT | Corporate services for the whole organisation, usually in corporate data centres: directory, email, HR and document management systems, the security operations centre. |
| Level 4: Business network (site IT) | Site business IT | IT networks for business users at a site, with connectivity to the enterprise WAN. Direct internet access should not extend below this level. |
| DMZ (Level 3.5): firewalls, jump servers | The IT/OT boundary | A buffer zone of firewalls, proxies and jump servers. It mediates all communication between IT and OT so that the two never connect directly. |
| Level 3: Site operations (MES, historians) | Site-wide supervisory systems | Monitoring, supervision and operational support for a whole site: manufacturing execution systems, historians, alarm and management servers. |
| Level 2: Supervisory control (HMI, SCADA) | Local supervisory systems | Monitoring and supervisory control of a single process, cell or line: HMIs, SCADA software, control-room workstations. |
| Level 1: Controllers (PLCs, RTUs) | Local controllers | Automated control of the process: programmable logic controllers (PLCs), remote terminal units (RTUs) and other control processors. |
| Level 0: Field devices (sensors, actuators) | Field devices | The sensors and actuators that measure and move the physical process. Many cannot authenticate the data they send. |
What is Level 3.5 in the Purdue model?
Level 3.5 is the industrial demilitarized zone (DMZ) between Level 3 and Level 4. It is not one of the original numbered levels; it was added in later descriptions as IT and OT networks became connected, as a buffer that holds firewalls, proxies and jump servers.
The idea behind it is that shared services, such as a data mirror or a jump server for remote access, live in the DMZ, so that enterprise systems and plant systems each talk to the DMZ rather than to each other. NIST's guidance for operational technology describes a DMZ as an enforcement boundary between network segments and recommends firewall rules that only permit connections between adjacent levels.
Why do descriptions of the Purdue levels differ between sources?
Because two views of the same hierarchy are in use. Security guidance describes the levels as network zones and the equipment in them; the ISA-95 level list (IEC 62264) describes them as functions. The numbers match, but the wording of Levels 0 to 2 differs.
| Level | Network and security view | ISA-95 functional view |
|---|---|---|
| 5 | Enterprise network | Not listed; the functional list stops at Level 4 |
| 4 | Business network at the site | Business logistics systems (ERP): plant schedule, material use, shipping, inventory |
| 3 | Site-wide supervisory | Manufacturing operations systems (MES, batch management, historians) |
| 2 | Local supervisory (HMI, alarm servers) | Control systems: supervising, monitoring and controlling the process (DCS, HMI, SCADA) |
| 1 | Local controllers (PLCs, RTUs) | Intelligent devices: sensing and manipulating the process |
| 0 | Field devices (sensors, actuators) | The physical process itself |
Is the Purdue model still relevant?
Yes, as a conceptual framework. Critics point out that cloud services and industrial IoT devices cut across a strict hierarchy, and the model was never intended to be a cybersecurity reference model. It is still the common vocabulary for where a system sits and where a boundary belongs.
NIST SP 800-82 Rev. 3 lists the Purdue model, the ISA-95 levels and the three-tier industrial IoT architecture as industry-recognised models an organisation can use, alone or combined, to organise its OT network segmentation.
When should you use the Purdue model?
Use it to plan and explain network segmentation in any environment that mixes business IT with industrial control systems, such as a manufacturing plant or a utility. It tells you which systems belong together and where to put the boundaries.
Use it when
- You are segmenting an OT network and deciding where firewalls and a DMZ go.
- You need a shared vocabulary for where an asset sits (a Level 1 PLC, a Level 3 historian).
- You are reviewing which systems are allowed to talk to which.
Skip it when
- You need a complete security programme: the model shows where controls can go, not which controls to apply.
- Your devices send data straight to cloud services, which a strict level-by-level hierarchy does not describe well.
- The network is office IT only, with no industrial control systems.
What are common mistakes when applying the Purdue model?
The common mistakes all weaken the boundary between IT and OT or let traffic skip levels.
- Letting levels skip. Firewall rules should prevent a Level 4 device from talking directly to Level 2, 1 or 0; permit connections between adjacent levels only.
- Collapsing the DMZ into the business or plant network, which lets IT and OT systems reach each other directly.
- Assuming an air gap. A complete separation between IT and OT rarely exists in present-day plants; design for controlled connections instead.
- Filtering inbound traffic only. Outbound rules from the control network should be as strict as inbound ones.
- Allowing internet access below Level 4.
- Treating the model as a security standard. It is a way to organise systems, not a list of controls.
How do you draw a Purdue model diagram?
Stack the levels from 5 at the top to 0 at the bottom, group Levels 4 and 5 as IT and Levels 0 to 3 as OT, place the DMZ between them, and connect each level only to its neighbours.
What do real network and plant architecture diagrams look like?
Live diagrams from the public ChartCraft gallery, each generated from a plain-English description. Open one to see the prompt that produced it.
Questions
What is the Purdue model?
The Purdue model is a reference model that divides the systems of an industrial organisation into hierarchical levels, from field devices at Level 0 to the enterprise network at Level 5. It is used to separate operational technology (OT) from information technology (IT) and to plan network segmentation for industrial control systems.
What are the levels of the Purdue model?
Level 0 is field devices such as sensors and actuators, Level 1 is controllers such as PLCs, Level 2 is local supervisory control such as HMIs and SCADA, Level 3 is site-wide operations, Level 4 is the site business network and Level 5 is the enterprise network. A DMZ, often called Level 3.5, sits between Levels 3 and 4.
What is Level 3.5 in the Purdue model?
Level 3.5 is the industrial demilitarized zone between the plant (Level 3) and the business network (Level 4). It holds firewalls, proxies and jump servers and acts as a buffer so that IT and OT systems do not communicate directly.
Is it the Purdue model or the Perdue model?
It is the Purdue model, named after Purdue University, where the Purdue Enterprise Reference Architecture was created in the early 1990s. Perdue model is a common misspelling of the same thing.
Is the Purdue model still used?
Yes. Cloud and industrial IoT connections have blurred its strict hierarchy, and it was never designed as a security model, but it remains the standard way to describe where industrial systems sit. NIST SP 800-82 Rev. 3 names it as one of the recognised models for organising OT network segmentation.