Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
OT network monitoring observes industrial traffic from a mirror port or TAP, decoding protocols to identify assets and detect abnormal commands without sending a single packet into the control network.

What Is OT Network Monitoring?
OT network monitoring is the practice of watching industrial traffic from a copy of it, rather than by interrogating devices. A sensor receives mirrored packets from a switch SPAN port or an inline network TAP, decodes the industrial protocols inside them, and builds two things from what it sees: a picture of which devices exist and how they talk, and a baseline of what normal looks like so that departures from it can be flagged.
Passive collection is not a stylistic preference. Control networks contain devices with small TCP connection tables and simple network stacks, and the industry has a long memory of controllers faulting under an ordinary port scan. If the monitoring system transmits nothing, it cannot cause an outage, and that property is what allows it to run continuously on a live plant.
Coverage follows the Purdue model. A single sensor at the industrial demilitarised zone sees traffic between IT and OT and nothing else, which is a start but leaves the control network dark. Practical deployments add a collector at the Level 2 supervisory switch stack in each plant area, and, where the consequence justifies it, at the Level 1 cell switches. Remote sites with low-bandwidth links usually run a small sensor locally that forwards metadata rather than packets.
Prefer a TAP over a SPAN port where the link is important: SPAN is a software function that a busy switch will drop under load, and dropped mirror packets look like silence rather than like an error. Where the mirror must cross a boundary, send it through a unidirectional gateway so the monitoring platform can never reach the control network.
Industrial traffic is far more repetitive than enterprise traffic, which makes behavioural baselining genuinely effective here. Useful detections include:
Commercial platforms from Nozomi Networks, Claroty, Dragos, and Forescout dominate the market and ship with maintained protocol dissectors and vulnerability matching. Where budget or scope is narrower, Zeek with industrial protocol parsers, Suricata with ICS rule sets, and CISA’s Malcolm distribution provide a capable open-source path, at the cost of building the asset model and tuning yourself. Whichever route is taken, the output should feed your SIEM and the alerts should be triaged by someone who can telephone a control engineer, not only by an analyst reading a signature name.
Passive monitoring cannot see a device that never transmits, nor read a configuration that is not exchanged over the wire. Most platforms therefore offer carefully constructed native queries — a single EtherNet/IP identity request, for example — that are treated as a change activity: scheduled, agreed with engineering, and limited to named devices. Treat that capability as an exception with a written justification rather than as a default setting.
UK operators assessed against the NCSC’s Cyber Assessment Framework will find Principle C1 asks for monitoring coverage proportionate to the essential function, with the data needed to investigate. Our SOC Maturation Services help teams turn industrial telemetry into detections that an on-call analyst can actually act on.
A receive-only sensor on a TAP or mirror port transmits no traffic onto the monitored segment at all. Some products additionally offer active queries, which do transmit; those are a separate feature that must be switched on deliberately. Confirm during procurement which mode you are buying and keep active polling disabled by default.
Asset discovery is largely complete within a week on a busy network. A behavioural baseline needs to span at least one full production cycle, including a shift pattern, a weekend, and ideally a planned maintenance window, so that legitimate rare events are learned rather than alerted on. Four to six weeks is typical before tuning settles.
Yes, with additional hardware. Serial taps and protocol converters let a sensor decode Modbus RTU or DNP3 over RS-485, and some platforms sell a dedicated serial collector. Where that is not practical, monitor the serial-to-Ethernet converter instead and treat the devices behind it as a group whose activity you infer rather than observe directly.
A joint process. The security operations centre performs the first triage, but validation nearly always requires a control engineer who knows whether a program download at 03:00 was a planned change. Agree escalation paths and out-of-hours contacts in advance, otherwise genuine alerts sit unactioned because nobody can confirm them.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.