Mapping a plant without touching production
On a production network, the rule is often to plug in nothing that talks to the equipment. Passive mapping respects it: the probe communicates with no device, it reads a copy of the traffic.
The principle: listening to a copy of the traffic
Industrial and office switches can copy the traffic of one or several ports to a dedicated port: the mirror port (SPAN), or its hardware equivalent, the TAP. The UMX Explorer probe plugs into that copy. It queries no device and sends no frame onto the observed network; a failure of the mirror port has no effect on production traffic.
A classic IT scanner queries the machines, which can disturb older PLCs. Passive listening only reads what already flows: Modbus requests, S7 sessions, OPC UA exchanges, supervision frames, discovery protocols. That traffic is enough to establish the inventory and the structure of the network.
What the map shows
- The inventory: PLCs, HMIs, SCADA stations, historian servers, gateways, network equipment, with their vendor and role inferred from the traffic.
- The layered architecture: each asset is placed in the Purdue model, from the field instrument (level 0) to business IT (level 4/5), with subnets and communication channels.
- Flows between levels: who communicates with whom, over which protocol. The map makes unexpected flows easy to spot, for example an office workstation reaching a PLC, an industrial protocol crossing the DMZ or a remote-maintenance link left open.
The observed map can differ from the architecture diagram: unlisted devices, links left over from a past project, IT/OT bridges installed as a temporary measure. A plant network evolves over years and changes hands; the observed map is the basis for protecting it.
On-site process
- Half a day on site to configure the mirror port with your integrator or IT department, plug in the probe and check the capture.
- A few days to a few weeks of listening, to cover production cycles: some links only communicate once per shift or per batch.
- A debrief: the annotated map, the inventory, segmentation findings and priorities, presented to the operations teams.
The site keeps its map, which is the basis for what follows: segmentation, IEC 62443 risk analysis, answers to principals' requirements.