OT DMZ Security: How to Design Safer Data Flows
To design safer data flows in an OT DMZ, you must isolate all external connections, enforce strict allow-listing of traffic, and place a jump host for all administrative access. This article explains the core principles, architecture, and practical steps for building a DMZ that protects industrial control systems while still enabling necessary data exchange.
Background: Why OT DMZs Exist
Operational Technology (OT) networks control physical processes—manufacturing lines, power grids, water treatment—and were historically air-gapped from corporate IT. Modern needs like remote monitoring, production analytics, and vendor support require connectivity, but direct links between IT and OT expose critical systems to malware, ransomware, and unauthorized access. A DMZ (demilitarized zone) is a buffer network that sits between the two, allowing only sanctioned data flows through controlled, inspectable paths. The concept comes from IT security but is adapted for OT’s real-time, safety-critical, and often legacy equipment constraints.
Core Architecture: The Three-Zone Model
The standard framework, described in IEC 62443 and ISA-99, divides the network into zones: IT (Level 4), DMZ (Level 3.5), and OT (Level 0-3). The DMZ is a separate security zone with its own firewalls on both sides—one facing IT, one facing OT. No traffic passes directly between IT and OT; everything must terminate in the DMZ. This means a compromised IT machine cannot reach an OT device without first breaching the DMZ, which has no direct route into the control network.
- IT firewall: Permits only specific protocols (e.g., HTTPS for historians, OPC UA for data) from IT to DMZ servers.
- OT firewall: Permits only the same protocols, but from DMZ servers to specific OT devices, and only on defined ports.
- Jump host: A hardened server in the DMZ that provides the only path for admin access to OT systems, with session recording and multi-factor authentication.
How to Design Data Flows: Step-by-Step
Designing data flows requires understanding what data must move, in which direction, and how often. Start with a data inventory and then apply the principle of least privilege.
- Identify data sources and consumers: List which OT devices (PLCs, HMIs, historians) produce data and which IT systems (ERP, analytics, dashboards) need it.
- Define the flow direction: Most flows are one-way—from OT to IT for monitoring. Rarely do you need to send commands from IT to OT; if you do, that requires a separate, tightly controlled path.
- Choose a protocol: Use modern, secure protocols like OPC UA with security policies, or MQTT with TLS, instead of raw OPC DA or Modbus. If legacy protocols are unavoidable, encapsulate them in a secure tunnel (e.g., VPN) that terminates in the DMZ.
- Map to DMZ servers: Place a data historian or protocol converter in the DMZ. OT devices send data to this server; IT systems read from it. The OT device never talks directly to IT.
- Implement allow-listing: On both firewalls, specify source IP, destination IP, protocol, and port. Deny everything else by default.
Choosing the Right Firewall and Rules
Not all firewalls are suitable for OT. Traditional IT firewalls may not understand industrial protocols or may introduce latency that disrupts real-time control. Look for firewalls that support deep packet inspection (DPI) for protocols like Modbus, DNP3, or OPC UA, and that can enforce allow-lists at the application layer. For rules, follow these guidelines:
- Use stateful inspection—allow return traffic only for established sessions.
- Set short timeouts for idle connections to prevent stale sessions.
- Log all denied traffic to a central SIEM for monitoring.
- Never allow FTP, Telnet, or other unencrypted protocols across the DMZ.
- If remote access is needed, use a VPN gateway in the DMZ with strong authentication and terminate the VPN there, not on OT devices.
Common Problems and Misconceptions
One common mistake is treating the DMZ as a simple firewall pair without proper segmentation. For example, placing a server in the DMZ that has dual NICs—one to IT, one to OT—creates a bridge that defeats the purpose. Another issue is allowing outbound internet access from the DMZ, which can be a vector for malware. Also, many assume that a DMZ is only for large enterprises; even small OT sites can use a single hardened server with two firewalls. A frequent misconception is that the DMZ eliminates all risk—it reduces it, but a compromised DMZ server can still be used as a pivot if not hardened and monitored.
Costs and Alternatives
Implementing a DMZ involves hardware costs (two firewalls, a server), software licenses (for DPI, VPN, monitoring), and ongoing maintenance. For small sites, a simpler alternative is a one-way data diode—a hardware device that physically allows data to flow in only one direction, often used for high-security OT. Another alternative is a virtual DMZ using software-defined networking (SDN) if the OT network already uses virtualized infrastructure, but this is less common in legacy environments. The cost of a DMZ is justified by the potential cost of a cyber incident, which can include production downtime, safety risks, and regulatory fines.
Safety and Monitoring
Safety is paramount in OT. Any data flow design must not interfere with safety systems (e.g., emergency shutdowns). These should be completely isolated, with no data flows to IT at all. For monitoring, deploy an IDS/IPS in the DMZ that can detect anomalies in industrial protocols—for example, a Modbus write to an unauthorized register. Regularly review firewall logs and alerts, and conduct penetration tests on the DMZ architecture. Also, ensure that all DMZ servers are patched, hardened (disable unnecessary services), and have antivirus, but test patches in a lab first to avoid compatibility issues with OT protocols.
Frequently Asked Questions
What is the difference between a DMZ and a firewall?
A firewall is a device that filters traffic based on rules. A DMZ is a network segment that uses firewalls to create a buffer zone. You can have a DMZ with one firewall (using three interfaces) or two firewalls, but the key is that the DMZ is a separate network where traffic terminates, not just a set of rules.
Can I use a single firewall for a DMZ?
Yes, a single firewall with three interfaces (IT, DMZ, OT) can create a DMZ. This is common for small sites and reduces cost. However, a compromise of that firewall could expose both networks, so two firewalls provide defense-in-depth. The choice depends on your risk tolerance and budget.
What protocols are safe to allow through an OT DMZ?
Use protocols with built-in security, such as OPC UA (with security policies), MQTT over TLS, HTTPS, and SSH (for admin). Avoid plain-text protocols like Modbus TCP, DNP3, or HTTP unless you can encapsulate them in a VPN or use a protocol converter that adds security. Always restrict to specific IPs and ports.
How do I handle remote vendor access?
Remote vendors should connect to a VPN gateway in the DMZ, not directly to OT devices. The VPN should require multi-factor authentication and be limited to specific times and IPs. From the DMZ, the vendor can access a jump host, and all sessions should be recorded. Never give vendors credentials to OT devices directly.
Is a data diode better than a DMZ?
A data diode is better for one-way data flows where you need absolute security—it physically prevents any return traffic. However, it is expensive and not suitable for two-way communication. A DMZ is more flexible and allows controlled two-way flows, making it the standard for most OT/IT integration. Use a diode for high-security environments like nuclear or military.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.