TroutTrout
Back to Blog
Zero TrustNetwork SegmentationOT SecurityOverlay Networks

How to Segment a Flat OT Network Without VLANs or Downtime

Trout TeamLast updated: 4 min read

A flat OT network means every device can reach every other device. A compromised HMI can talk to every PLC. A vendor laptop on the wrong port can access SCADA. Lateral movement is trivial. The standard fix is VLAN segmentation. The problem: VLANs require switch reconfiguration, recabling, IP changes, and production downtime. For many facilities, that is a project measured in months with a change freeze operations cannot absorb.

Overlay networking segments the network in software, on top of the existing physical infrastructure, without any of that.

Why VLANs Are Hard in OT

Switch reconfiguration. Every port assignment must be planned, configured, and tested. In a facility with hundreds of ports across multiple switches, this is weeks of work.

IP address changes. Moving a device to a new VLAN often means a new IP subnet. OT devices frequently have hardcoded IPs in their configurations. Changing them requires reprogramming the device and testing the entire control loop.

Cabling changes. If a PLC and its HMI need to be on different VLANs, they may need to be on different switch ports. This means pulling new cable.

Downtime. Every change carries risk. A misconfigured VLAN can isolate a critical device. Testing requires taking equipment offline. Production teams resist any change that threatens uptime.

Ongoing maintenance. Every new device, every network change, every expansion requires VLAN reconfiguration. The operational burden never ends.

How Overlay Networking Works

An overlay network creates virtual network segments on top of your existing physical network. The underlay (your switches, cables, and IP addresses) stays exactly as it is. The overlay adds a new logical layer that controls which devices can communicate with which.

Step 1: Deploy the Access Gate. A physical appliance connects to your existing network. No changes to switches or cabling.

Step 2: Asset discovery. The Access Gate passively discovers every device on the network. No active scanning. No risk to operations.

Step 3: Define segments. Group assets into logical segments: CNC machines, SCADA controllers, HMI terminals, engineering workstations. Each segment gets its own access policy.

Step 4: Enforce. The overlay network routes traffic through identity-aware proxies. Devices in different segments cannot communicate unless a policy explicitly allows it. Everything else is denied and logged.

The overlay uses the 100.64.0.0/16 address space (CGNAT range), which does not conflict with existing private IP ranges. Your devices keep their original IPs. Your switches keep their original configurations.

Overlay vs. VLAN: Practical Comparison

FactorVLANsOverlay Network
Switch changesRequiredNone
IP address changesOften requiredNone
Cabling changesSometimes requiredNone
Production downtimeYesNone
Deployment timeWeeks to monthsA day
Ongoing maintenanceHighPolicy changes only
Identity-awareNoYes
Session loggingNoYes

What Segmentation Actually Prevents

On a flat network, a single compromised device can:

  • Scan and discover every other device
  • Attempt connections to PLCs, SCADA, and safety systems
  • Exfiltrate data from any accessible endpoint
  • Propagate ransomware across the entire network

With overlay segmentation, a compromised device can only reach the assets its policy allows. If the policy says "this HMI can talk to PLC-001 on Modbus TCP port 502 only," that is all it can do. Every other connection is dropped and logged.

The Lollipop Model

Each OT asset connects to the network through a single proxy endpoint. The proxy handles authentication, authorization, logging, and encryption. The direct path from the asset to any other device is blocked. The only way in or out is through the proxy.

This creates a topology that looks like a lollipop for each asset: one stick (the proxy path) and one candy (the asset). No lateral paths between assets. No unauthenticated connections.

The Overlay Networks Explained page walks through the four-step architecture in detail.


For more Zero Trust OT resources, architecture guides, and comparisons, visit the Zero Trust for OT Networks hub.

FAQ

Frequently Asked Questions

Does the overlay add latency?
Minimal. The proxy adds sub-millisecond overhead per session establishment. Once the session is established, traffic flows at near line rate. Industrial protocols are not latency-sensitive at the sub-millisecond scale.
Can I keep my existing VLANs?
Yes. The overlay works on top of VLANs. If you already have some VLAN segmentation, the overlay adds finer-grained identity-based control within and across those VLANs.
What happens if the Access Gate goes down?
Access Gate deploys adjacent to the network, not inline with production traffic. If the appliance goes offline, direct network paths remain operational. You lose enforcement and logging until the appliance is restored, but production does not stop.
How do I handle devices that need to communicate across segments?
Define explicit policies. If PLC-001 needs to send data to the historian server, create a policy allowing that specific connection on that specific protocol. Everything else remains denied.
Does this satisfy compliance requirements for segmentation?
Yes. CMMC and IEC 62443 both require network segmentation. Overlay segmentation with identity-based access control satisfies these requirements without the operational burden of VLAN reconfiguration.

Other Articles

Cold ChainOT Security

CISA Fact Sheet on Industrial Refrigeration and Cold Chain Controllers: The Eight Mitigations as a Checklist

On November 5, 2026, CISA, the FBI, HHS, USDA and DOT published a joint fact sheet on malicious activity against industrial refrigeration and cold chain monitoring systems. Attackers go after unpatched or internet-accessible temperature controllers and push units into continuous heating and defrost. The fact sheet lists eight mitigations. Most of them come down to taking the controllers off the internet and controlling how the refrigeration contractor connects.

ICS AdvisoriesOT Security

Hitachi Energy TRO600: Unauthenticated File Read Exposes Router Passwords (ICSA-26-302-02)

On October 29, 2026, CISA republished Hitachi Energy advisory 8DBD000224 as ICSA-26-302-02. It covers two CVEs in the TRO600 series of industrial cellular routers: an unauthenticated file read that exposes configuration files and password data, and a port-forwarding bypass that lets a logged-in user reach services meant for localhost only. Version 9.2.2.1 fixes both.

ICS AdvisoriesOT Security

Siemens SIMATIC WinCC, PCS 7 and Process Historian: NTLM Relay With No Fix (ICSA-26-321-08)

CISA's ICSA-26-321-08 republishes Siemens SSA-970803: CVE-2026-58114, an NTLM relay weakness in SIMATIC WinCC V7.5 to V8.1, WinCC Runtime Professional V17 to V21, PCS 7 V9.1, BATCH V9.1, Process Historian and Information Server. An on-path attacker can take over a user's session and run code with that user's rights. No product has a fix, and four will not get one, so the SQL traffic has to be encrypted and the servers closed off from every host that does not need them.