When an organization first tries to extend its IT security tools to the plant floor, it usually hits the same wall: the endpoint agent either cannot be installed, or it can be installed but operations will not allow it. Operations has good reason to be cautious.
Below we go through the few basic differences that mean an OT environment needs its own class of tools, and look at how this works in practice.
Why conventional endpoint protection does not work
The operating systems are old. A large share of plant HMIs and engineering workstations run Windows 7, or even XP. The reason is that the control software on them is certified only for that version, and the equipment vendor does not support anything newer. Modern EDR agents either do not run on these systems or are not supported on them.
Resources are scarce. An industrial panel PC often has 2 GB of memory. An agent that scans continuously eats the headroom the control application needs, and latency here is not a matter of convenience.
There is no internet connection. In principle, a segmented OT network has no way out. A model built on daily signature updates does not work there.
A false positive stops production. If an EDR quarantines a file by mistake in an IT environment, someone gets annoyed. If the same happens to a component of a control application, production stops.
There is no vendor approval. For many machines, the supplier explicitly forbids installing third-party software; otherwise the warranty or the certification is void.
The principles of OT endpoint protection
Tools designed for this purpose follow a different logic.
An allowlist instead of a blocklist
The basic question in IT protection is: is this file malicious? Answering it takes a knowledge base that is updated all the time.
In OT protection the question is: is this file on the list of what is allowed to run? The software on a production-line HMI stays the same for months, often for years. Once you fix the list of approved applications, running anything else is blocked by default, whether or not the malware is known. This approach also protects against zero-day attacks and needs no daily updates.
This is called application lockdown or trust-list-based protection. The TXOne Stellar product family, for example, is built on this principle and handles modern and legacy systems separately.
Agentless scanning for machines where nothing can be installed
Some machines cannot take any software at all. For these, portable scanning is the answer: a USB device the engineer plugs in, runs the check with, and then takes to the next machine. Nothing is installed on the machine, no process is left running on it, and it uses none of its resources.
This also solves the problem of supplier devices: the laptop or USB stick of a technician who comes in for maintenance is scanned before it is allowed in. USB media is still one of the most common infection routes into isolated networks. That has not changed since Stuxnet. The TXOne Portable Inspector was made for this situation.
Virtual patching at the network level
If a vulnerable device cannot be updated, the protection has to go in front of it. An industrial IPS installed inline in the network recognizes traffic aimed at that specific vulnerability and blocks it, while the device itself stays untouched.
This is the virtual patch: it does not fix the flaw, but it prevents it from being exploited. In industrial environments it is often the only realistic answer to a CVE that will not get a vendor fix for years. The TXOne EdgeIPS and EdgeFire devices provide this layer, with deep inspection of industrial protocols (Modbus, S7comm, EtherNet/IP, DNP3).
Understanding industrial protocols
A general-purpose firewall sees Modbus traffic as a single TCP port. An OT-aware device also sees the function code: it can tell a read operation from a write, and normal operation from a program download.
That makes rules like this possible: “from this segment the PLCs are read-only; writing is allowed only from the engineering workstation, during a change window.” An IT firewall cannot control traffic at that level of detail.
How it fits into the bigger picture
Endpoint protection is not a program on its own. A useful order:
- Asset inventory, with passive discovery. Without it you do not know what to install where. We wrote about this in detail in our ICS/SCADA article.
- Segmentation: an industrial DMZ and zone boundaries. This gives you the largest reduction in risk.
- Network protection at the zone boundaries, with virtual patching for devices that cannot be updated.
- Endpoint protection where it can be installed; portable scanning where it cannot.
- Monitoring, watching for deviations from the baseline.
So endpoint protection is the fourth step, not the first. Teams that start installing agents before the inventory and the segmentation are done usually put in a lot of work for little reduction in risk.
Deployment considerations
Start in monitor mode. You cannot put an allowlist together on paper. The system first runs in learning mode and collects what actually runs on the machine, and you switch to enforcement mode only after reviewing that.
Talk to the equipment supplier. Many vendors now support or even recommend OT-specific protection tools. Settle the warranty question in advance.
Test on a spare device. If you have a spare HMI with the same configuration, validate the installation there before it goes on a live machine.
Plan for change management. When the equipment supplier updates the control software, the allowlist has to be updated as well. Make this part of the process so it does not come as a surprise later.
Use the compliance overlap. These tools also help meet the fifth NIS2 measure area (vulnerability handling) and the ninth (asset inventory, access control), so the deployment documentation serves two purposes.
In summary
OT endpoint protection is not a stripped-down version of the IT solution. It is built on different design principles: an allowlist instead of a blocklist, offline operation instead of cloud dependency, virtual patching instead of updates, and protocol awareness instead of port filtering.
As a TXOne Networks partner, ARLITECH deploys these tools in industrial environments. Deployment always starts with the inventory and segmentation, because a tool is only worth something once we know what we are protecting and from what.
If this topic is on your agenda, our OT endpoint protection service covers this area, and you will find our full offering on the OT services page.