New: the AI firewall watches the whole platform and explains each incident in plain words. See how it works

IoT network segmentation for plants: where sensors, gateways and the cloud link belong

Where sensors, gateways and the cloud link belong on a plant network, which few connections to allow between them, and how to stop the layout eroding with every project.

IoT network segmentation for a plant puts sensors, gateways and the cloud link into separate zones and allows only the connections each one needs. Field devices talk to their gateway, the gateway talks out to known platform addresses, and nothing outside can open a connection into the control network.

I work on security for plants in energy, water and food. Segmentation rarely fails on day one; it erodes project by project, each time someone adds a rule to make a sensor work.

Should IoT devices be on a separate VLAN?

Yes, but a VLAN only separates traffic; the rules between VLANs do the protecting. NIST SP 800-82 Rev. 3, the US guide to operational technology (OT) security, says segmentation is typically built with separate switches or with VLANs, and suggests physically separate switches for high-criticality devices such as safety systems.

The same guide warns that isolation between segments does nothing against lateral movement inside one, such as a worm spreading. So I draw zones around what must never share a segment: the safety system, the controllers that run the process, and a batch of new wireless sensors are three separate zones.

Which zones does a connected plant need?

Start from the data flows. NIST suggests grouping devices by criteria such as criticality, trust, data flow and location, and names the Purdue model, ISA-95 levels and the three-tier IIoT architecture as ways to organise them. This is the layout I start from:

ZoneHoldsMay talk to
ControlControllers, wired instruments, operator panelsIts own gateway or SCADA server
IoT sensorsWireless and retrofit sensorsTheir gateway only
GatewayDevices that collect field data and send it onThe zones it reads, and out to the platform
DMZServices shared by plant and officeOffice and plant, never field devices directly
EnterpriseOffice systemsThe DMZ only

Do I need a firewall between IoT and OT networks?

Yes. Put a boundary device with rules at every zone edge, for outbound as well as inbound traffic. NIST recommends rules that permit connections only between adjacent levels or zones, a deny-all, permit-by-exception policy where possible, and outbound rules as stringent as inbound ones.

Outbound is where IoT projects slip. A gateway allowed to reach any address on port 443 can send plant data to any server, and every server it reaches can answer on that connection. Pin it to the addresses and ports its platform publishes.

How do you connect a plant network to the cloud safely?

Let the plant connect out through one gateway or DMZ service over an encrypted protocol, and never open an inbound port to a controller. NIST advises limiting insecure protocols and using secure, authenticated protocols between the OT environment and other segments.

Hermetry connects field devices to live dashboards, rules and alerts: IoT telemetry and SCADA in one platform. On its side of the cloud link, a device profile can list Allowed networks, up to 64 IPv4 or IPv6 networks or single addresses, and refuses devices outside them (MQTT CONNACK 5, HTTP 403). MQTT uses TLS on port 8883 by default; plain MQTT on port 1883 stays off unless a profile allows it. The details are in device transport security.

How do you keep network segmentation from eroding?

Give every rule an owner and a reason, and record traffic before you write rules. When it is hard to tell which traffic is needed, NIST suggests temporarily allowing and recording all communication between segments, which can also reveal flows nobody documented.

Watch maintenance laptops and remote access too. NIST notes that maintenance devices may connect to two networks at once, and asks that temporary remote access be removed when the work is done.

Frequently asked questions

What is the Purdue model in network segmentation?

It is a reference model that sorts plant systems into numbered levels. NIST SP 800-82 Rev. 3 names it as one way to organise OT segmentation: field devices sit in Levels 0, 1 and 2, operations management in Level 3, and its example rules stop Level 4 devices from talking directly to Levels 0 to 2.

What is a data diode?

A data diode, or unidirectional gateway, lets data travel in one direction only. NIST lists it as an alternative to a firewall: placed between plant levels, it may protect the lower levels from a cyber incident at the higher ones, while data keeps flowing the one allowed way.

Does segmentation replace securing the devices themselves?

No. Segmentation limits who can reach a device; it does not stop an attack inside the segment. NIST also recommends least functionality: switch off services and ports a device does not need, such as an unused web or SSH server on a controller or operator panel.

Share

See your field data live this week

Start a trial in your region with your first devices, or book a demo and bring your own use case.