Segmenting a Flat OT Network Cell by Cell: A Step-by-Step Migration Plan

OT network segmentation migration: traffic baseline, communication matrix, cell boundaries, rules in monitoring mode, wave plan, verification and rollback steps.
Technical summary
Technology
VLAN, SPAN/TAP, tshark, industrial firewall, PROFINET, EtherNet/IP, IEC 62443
Topic
Dividing a single-VLAN OT network into zones without stopping production
Level
Intermediate–advanced
Prerequisites
  • Knowledge of VLANs, subnets and ACLs
  • Basic knowledge of PLC/HMI communication structure
  • Experience with packet analysis in Wireshark
In this article8 sections

In many factories, the OT network has grown over the years, addition by addition, into a single VLAN and a single subnet: PLCs, HMIs, SCADA servers, engineering workstations, cameras and sometimes even office printers are in the same broadcast domain. Everyone knows it needs to be split. The real question is how to do it with planned windows and limited impact on production. Below, we describe a method for segmenting a flat OT network with a plan that is based on traffic measurement, proceeds cell by cell and makes every step reversible.

The risks of a flat network and the goal of the migration

The problem with a flat network is not just security. The risks fall under three headings:

  • Spread: Malware that infects an engineering workstation reaches every PLC and server on the network directly. There is no point in between where filtering can be done.
  • Fault impact: Traffic produced by a broadcast storm, a loop or a faulty device hits all lines at the same time. The whole plant is affected until the location of the fault is found. In the field, we usually see it like this: a maintenance technician plugs a cable with both ends going to the same field switch, and within a few seconds every HMI drops into a communication alarm.
  • Invisibility: Nobody knows who is talking to whom; a newly added device or an unexpected connection is not easily noticed.

The goal is not to “separate everything”. The goal is to create zones based on measured communication needs and to restrict flows between zones to only those that are necessary. For the zone and conduit framework, see the article the zone and conduit approach in IEC 62443. The topic here is not IT–OT separation but the division of the OT network itself.

Building the traffic baseline and communication matrix

The segmentation decision is made by measurement, not by assumption. The first step is a passive traffic capture. The port mirroring configuration or TAP installation required for the capture is planned separately. Traffic is copied with SPAN (port mirroring) on the core or distribution switch, or with a TAP placed in the link, and sent to a collection device. An example of VLAN-based SPAN on a Cisco IOS-based switch:

monitor session 1 source vlan 10
monitor session 1 destination interface GigabitEthernet1/0/24
show monitor session 1

SPAN uses switch resources and can drop packets under heavy traffic; on high-traffic links, a TAP is more reliable. Also watch the speed of the destination port: if the total traffic of the source VLAN exceeds the destination port, the capture comes in incomplete and nobody notices. Once the capture is taken, conversation lists are extracted. With tshark, Wireshark’s command-line tool:

tshark -r ot-line3.pcapng -q -z conv,ip
tshark -r ot-line3.pcapng -q -z conv,eth
tshark -r ot-line3.pcapng -q -z io,phs

The first command gives conversations at IP level, the second at Layer 2 level, and the third the protocol hierarchy. Do not skip the Layer 2 summary. Traffic that does not use IP, such as PROFINET RT, does not appear in the IP summary. For a more comprehensive approach, passive asset discovery tools can be used; the method and its limits are in the guide passive asset discovery in OT networks.

Each row of the communication matrix derived from the raw data contains source, destination, protocol/port, direction and purpose. Most of the effort goes into the purpose column: for each flow, the question “what is this for, and who owns it” is answered together with the production and maintenance teams. Flows whose purpose is unknown are marked separately. They are either a forgotten dependency or a connection that should be removed. No rules are written until the two are told apart.

Defining the target segment structure

Once the matrix is ready, the zone boundaries are drawn. Rules that work in the field:

  • The cell is the boundary of Layer 2 dependency: PROFINET IO traffic runs at Layer 2; the IO controller and IO devices stay in the same segment. If multicast is used for EtherNet/IP implicit (I/O) messaging, producer and consumer devices may need to be on the same subnet; the default multicast TTL value usually does not allow routing.
  • Shared services in a separate zone: SCADA servers, historians, OT domain controllers and the patch server are grouped in an “OT server” zone.
  • Engineering workstations in a separate zone: Systems with write access to PLCs are kept separate from operator HMIs.
  • Non-OT devices out: Cameras, printers, building automation and office devices are moved to their own segments. This is often the easiest and lowest-risk first step.

The target structure, in writing, includes: one VLAN/subnet per zone, a boundary that filters between zones (ACLs on a Layer 3 switch or an industrial firewall) and a rule list derived from the communication matrix. If a firewall is to be placed at the cell boundary, choosing the operating mode is covered in detail in the article cell-level firewalls: transparent mode or routed mode. For separating multicast traffic in cells using EtherNet/IP, the article IGMP snooping in EtherNet/IP networks will also be useful.

Applying rules in monitoring mode

Rules are not put into blocking mode from day one. First, the boundary device is installed and run with a single general rule that passes all traffic but logs every flow. Then the allow rules derived from the matrix are added above this general rule; each one is logged. After a while, the flows still hitting the general rule are reviewed. These are the flows missing from the matrix.

This phase ends when no flows hit the general rule any more, or when it has been decided that every remaining flow will be deliberately denied. Only then is the general rule at the bottom changed from “allow and log” to “deny and log”. This change is also a change and is made in a window. A common mistake is never taking this last step: the firewall stays in monitoring mode for years, and segmentation exists on paper but not in practice.

Wave plan: moving cell by cell

The migration is divided into independent waves. Each wave is small enough to finish in a single change window. An example plan:

Wave Scope Window Risk
0 Management network and monitoring infrastructure During production Low
1 Moving out cameras, printers, building automation During production Low
2 OT server zone and engineering zone Weekend Intermediate
3 Pilot cell (least critical line) Planned downtime Intermediate
4..n Remaining cells, one or two per window Planned downtime High
Final Switching the general rule to deny Weekend Intermediate

Don’t underestimate wave 0. If there is no management path to network devices independent of production traffic, a wrong VLAN change in a later wave cuts off access to the device, and someone has to climb a ladder to a field cabinet. For the design of this path, see the article OT management networks and out-of-band access. Each wave is also a change window in its own right; the plan template and go/no-go approach are based on the method in the article change window engineering in OT.

Verification and rollback for each wave

At the start of each wave, the switch configurations, address definitions in PLC/HMI projects and the firewall rule base are backed up. The move is done in this order: preparing the new VLAN and subnet on the boundary device, adding the rules in monitoring mode, moving the cell ports to the new VLAN, changing device addresses and gateways if needed, functional testing. The frequently overlooked point is the gateway: the PLC’s IP address changes but the gateway in the project stays old; communication inside the cell works, communication outside the cell does not.

Verification is done by showing that the process works, not the network. Ping is not enough.

  • There are no connection errors between the PLC and IO devices; no new error entries in the diagnostic buffer.
  • HMI and SCADA read all tags with current values; there are no communication alarms.
  • There are no gaps in the historian data for the cell.
  • An online connection to the PLC can be established from the engineering workstation.
  • Required data exchange between cells (interlocks, signal sharing) works.
  • On the boundary device, there are no unexpected flows hitting the general rule for the wave.

The rollback criterion and method are written in advance: ports go back to the old VLAN, device addresses back to their old values, and the old configuration is restored. The rollback time must have been measured and must fit within the window.

Migration checklist

  • The traffic capture covers all normal operating cycles; Layer 2 and Layer 3 conversations were extracted separately.
  • The purpose and owner of every flow in the communication matrix are known; those with unknown purposes have been decided on.
  • Zone boundaries do not split Layer 2 dependencies.
  • The management network is ready before the segmentation waves.
  • For each wave, the backup, implementation steps, verification list and rollback criterion are written down.
  • Rules are in monitoring mode first; the switch to deny is planned as a separate change.
  • The current network diagram, VLAN/subnet table and rule list are updated after each wave.

The job is not over when segmentation is finished. Monitoring flows between zones and noticing newly added devices and rule drift require continuity. To build the traffic baseline of your existing network and set up the migration plan together, see our factory OT infrastructure survey, industrial network monitoring and fault analysis and OT cybersecurity and segmentation pages. All of Wireshark’s statistics options are described in the Wireshark documentation.

Frequently asked questions

How long should traffic be recorded for the baseline?

There is no fixed period; the capture must cover all of the plant’s normal operating cycles. That means at least one full shift cycle, one recipe or product change, weekly backup and reporting jobs and, if possible, a maintenance job. With short captures, flows that run rarely but are needed, such as a month-end report or licence validation, drop out of the matrix.

Do all devices’ IP addresses have to change for segmentation?

Not always. Moving a cell to a new VLAN and subnet usually requires an IP change. If there are many hard-coded addresses in PLC and HMI projects, in the first phase a boundary can be created without an IP change by placing a firewall in transparent mode in front of the cell. Readdressing is done later, together with a planned modernisation.

Can PROFINET devices be split across different VLANs?

PROFINET IO real-time traffic runs at Layer 2; an IO controller and the IO devices connected to it must stay in the same broadcast domain. That is why the split is made along cell boundaries containing a PLC together with its I/O devices. If data exchange between cells is needed, it is designed via routable communication or devices acting as gateways.

If a problem occurs in one wave, does the whole project have to be rolled back?

No. If waves are planned independently of each other, rollback covers only the problematic wave. Each wave has its own rollback steps, a backup of the old VLAN and port configuration and a pre-written decision criterion. Completed waves stay in place.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Industrial

PLC, PROFINET/PROFIBUS and SCADA communication, IT/OT network segmentation and industrial field connectivity. We install and monitor without stopping the production line.

Knowledge Center

Other articles