Safeguard
Security Guides•

IT and OT network segmentation and the DMZ, explained simply

Separating IT and OT networks, with a DMZ for passing data, limits how far an intruder can travel. What it means, how to start and common mistakes.

Safeguard Security Team
3 min read

Segmentation means splitting your network so that an office compromise cannot reach controllers directly. CISA's May 2025 mitigations recommend separating IT and OT networks, using a demilitarized zone, or DMZ, for passing control data to enterprise systems. The aim is to let data through without letting attackers through.

The basic picture

Think of three areas. The enterprise network holds email, business apps and laptops. The OT network holds controllers, HMIs and engineering stations. The DMZ sits between them and holds only the systems that need to exchange data, such as a historian that copies readings out to business users.

Traffic flows to the DMZ from each side, not straight across. That gives you a place to inspect, log and restrict.

Why it matters

In CISA's Ukraine alert, attackers used VPN access and remote tools to reach operator interfaces, and the alert recommends isolating ICS networks from untrusted networks and locking down unused ports and services. The 2023 PLC advisory also recommends segmenting networks, for example using the Purdue model, and restricting unused ports and protocols.

Segmentation does not stop every attack. It limits what an attacker can do after a first foothold, and buys time to detect them.

How NIST frames it

NIST SP 800-82 Rev. 3 lists typical OT topologies and countermeasures among its topics. Check the full document for how it describes architectures and zones, and match it to your own site.

A starting plan

  1. Map what talks to what. Capture flows, preferably passively, before changing anything.
  2. Define zones. Group assets with similar security needs, as in CISA's inventory guidance.
  3. Place a DMZ for the few systems that must bridge networks.
  4. Write allow rules for the flows you identified, and deny the rest.
  5. Control remote access through the DMZ, not around it.
  6. Test with operations in a planned window, because a missed flow can stop a process.
  7. Review quarterly, since flows drift.

Common mistakes

  • A diagram that no longer matches reality, with an old modem or vendor link nobody removed.
  • Rules that say "any to any" for a "temporary" project.
  • Engineering laptops that move between networks, carrying anything they picked up.
  • A DMZ host that has direct access to everything, which makes it a new bridge.
  • Skipping logging, so nobody sees a blocked attempt.

Quick check

Is a firewall between IT and OT enough?

It is a start. CISA's guidance also asks for a DMZ for data exchange, strong remote access controls and monitoring.

What is the Purdue model?

A reference model that arranges industrial networks in levels. The 2023 PLC advisory names it as one way to segment networks.

Safeguard's policies, gates and guardrails apply to software delivery pipelines rather than plant networks, so they complement segmentation but do not replace it.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.