The Purdue model is an industrial network segmentation framework that separates enterprise IT from operational control layers. It helps define where remote access may be brokered, which layers are most sensitive, and why direct connectivity into lower OT levels creates unacceptable risk.
How the Purdue Model Organises Industrial Networks
The Purdue model is best understood as a segmentation framework for industrial environments, not as a security control by itself. It gives architects a layered way to separate business systems from control systems, place trust boundaries between levels, and decide where traffic should be inspected, brokered, or denied before it reaches sensitive OT layers.
That layered structure is valuable because OT environments often mix older protocols, long-lived assets, and processes that tolerate very little interruption. A clear model helps teams distinguish between systems that can accept ordinary enterprise connectivity and systems where even a small design mistake can create unsafe or high-impact exposure.
Why Segmentation Matters in OT
The Purdue model matters because direct flat connectivity removes the buffer that industrial operators rely on to contain faults, misuse, and compromise. It is especially useful for explaining why lower OT levels should not be reachable in the same way as enterprise resources, and why segmentation is usually paired with tightly controlled conduits rather than open routing.
In practice, the model supports a security conversation about trust boundaries, not just network diagrams. It helps teams justify why remote administration, vendor access, historians, and data exchanges should be mediated through OT Network Segmentation, Purdue Model and IEC 62443 Zones and Conduits Guide rather than extended end to end into control layers.
How It Is Used in Architecture and Remote Access
Architects use the Purdue model to decide where services belong, which connections require inspection, and which traffic should terminate in a demilitarised or brokered layer instead of crossing directly into controllers, engineering workstations, or safety-relevant segments. The model is therefore as much about access design as it is about topology.
This is also why OT remote access is usually treated as a special case. A good reference point is NIST SP 800-82 OT Security Guide, which ties the Purdue concept to layered defense, remote access, and OT control baselines. For broader OT context, OT Security Guide places the model alongside SCADA, industrial protocols, and segmentation choices that affect operational resilience.
Limits, Misuse, and Modern Interpretations
The Purdue model is useful, but it is not a complete security architecture and should not be treated as a substitute for asset inventory, identity control, protocol-aware monitoring, or zone policy. Many modern OT environments do not fit neatly into the classic levels, especially where cloud, remote vendors, edge compute, or converged IT and OT services are involved.
Its main limitation is that organisations sometimes use the model as a label without enforcing the controls that make it meaningful. A diagram that names levels but allows unrestricted pathways between them creates a false sense of safety. In that case, the model becomes documentation, not segmentation.
Risk and Threat Considerations
Weak Purdue-style segmentation increases the blast radius of compromise and makes it easier for an attacker, contractor mistake, or infected enterprise host to move toward control assets. The highest risk appears when remote access is inserted directly into lower levels, because the trust boundary has been bypassed rather than mediated.
Failure mechanism: A flat or loosely segmented OT design lets unauthorized traffic, stolen credentials, or malicious tooling traverse from enterprise zones into engineering and control layers with too little inspection or constraint.
Impact: The result can be manipulation of controller logic, loss of visibility, disruption of process operations, unsafe state changes, or broader production outage.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | SC-7 — Boundary Protection | Purdue-model layers depend on enforced network boundaries and controlled conduits. |
| AC-17 — Remote Access | The model is often used to decide where remote access may be brokered into OT. | |
| RA-3 — Risk Assessment | Segmentation choices in OT are driven by consequence, trust boundary, and exposure analysis. | |
| Recommendation — Enforce boundary controls between Purdue layers and broker all cross-zone traffic. Broker remote access through controlled entry points instead of direct lower-layer connectivity. Assess exposure from each Purdue-layer connection before approving it. | ||
| NIST CSF 2.0 | PR.AA-05 — Identity Management, Authentication and Access Control | OT segmentation only holds when access paths into layers are authenticated and constrained. |
| PR.DS-01 — Data-at-Rest Is Protected | Industrial architecture often protects sensitive control and telemetry data at layer boundaries. | |
| Recommendation — Apply access control to every pathway that crosses into sensitive OT layers. Protect sensitive OT data wherever it crosses or resides within segmented environments. | ||
Practitioner Guidance
Governance implication: Treat the Purdue model as a design baseline that must be translated into enforceable zones, conduits, and remote access rules. The practical question is not whether the diagram exists, but whether every crossing between layers is justified, documented, and technically controlled.
What to watch for: Dual-homed hosts, ad hoc vendor tunnels, shared jump points, and “temporary” exceptions are common signs that the model is being bypassed in practice. If those patterns exist, the architecture is already drifting away from the security intent the Purdue model is supposed to express.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org