TroutTrout

Zero Trust for OT networks. Runs on site. Nothing to install on machines.

Most OT devices cannot run security agents. So Zero Trust for OT enforces identity-based access at the network boundary, on site. This hub links Trout's architecture guides, comparisons and CISA-aligned playbooks for doing it without disrupting production.

Last updated:

What is Zero Trust for OT?

Zero Trust for OT means no connection to an operational technology asset is trusted by default. Every user, device, and session must be authenticated and authorized before accessing PLCs, HMIs, SCADA systems, or any other OT resource. Unlike IT Zero Trust, OT Zero Trust must work without endpoint agents, without disrupting production, and often without internet connectivity. Trout Access Gate enforces it in front of the equipment, with MFA tied to the corporate directory and every session recorded.

Zero Trust for OT at a glance

Why OT Zero Trust is different.

Four properties separate OT Zero Trust from IT Zero Trust. Each one has architectural implications. Each one is endorsed in the joint CISA guidance published on April 29, 2026.

Nothing to install on the asset.

PLCs, HMIs running Windows XP, SCADA servers, and ten-year-old engineering workstations cannot host an agent. CISA's April 2026 guidance endorses agentless deployment for legacy OT and recommends pairing it with active enforcement at the network boundary, not just passive monitoring.

Control who reaches what, without a redesign.

Conventional microsegmentation requires VLAN redesign and re-IP'ing, which most production plants cannot accept. Overlay-based microsegmentation enforces per-asset, per-protocol, per-session policy on top of the existing physical network. The Layer 2 topology does not change.

Compensating controls for the ICAM gap.

Most installed-base OT predates Active Directory, SAML, or OIDC. CISA endorses compensating controls above the device level, including segmentation as a valid compensating control. Identity is enforced at the network boundary, on behalf of assets that cannot present it themselves.

Stop lateral movement from IT to OT.

Volt Typhoon, the actor in CISA advisory AA24-038A (February 2024), and similar groups compromise IT, then pivot to OT through whatever access path exists. Air-gapping alone is not a control: CISA explicitly warns against the false sense of isolation. Every IT-to-OT session must be authenticated, authorized, and logged, not merely inventoried.

IT and OT Zero Trust compared

How Zero Trust changes when the asset is a PLC.

Question
Where the policy is enforced
IT Zero Trust
On the endpoint, by an agent, or in a cloud broker
OT Zero Trust
On site, at the network boundary in front of the asset
Question
How a user proves identity
IT Zero Trust
Single sign-on and MFA on the device
OT Zero Trust
MFA at the gate, on behalf of a PLC or HMI that cannot ask for it
Question
What runs on the asset
IT Zero Trust
An agent on every laptop and server
OT Zero Trust
Nothing. A 20-year-old controller is covered like a new one
Question
Internet dependency
IT Zero Trust
The policy engine is usually a cloud service
OT Zero Trust
Enforcement works with no internet link, including on air-gapped sites
Question
What a failure must not do
IT Zero Trust
Lock users out of an application
OT Zero Trust
Stop the process. The control is deployed beside the network first, with failover
Question
Reference guidance
IT Zero Trust
NIST SP 800-207 (2020), CISA Zero Trust Maturity Model 2.0 (2023)
OT Zero Trust
Joint CISA guidance for OT (April 29, 2026), NIST SP 800-82r3 (2023), IEC 62443-3-3
In production

Where it runs today.

55
lift sites on one management plane at STBMA, a French ski resort with no security staff
4 hours
to deploy each restricted environment at Thales, fully on premises
1,300
assets and 660 users managed at a large manufacturer in North Carolina
13 of 14
core criteria met in a NATO navy lab's Zero Trust evaluation
FAQ

Questions about Zero Trust for OT.

OT

Access Gate enforces Zero Trust at the network layer for OT. Nothing to install on endpoints. No production disruption.

IT Zero Trust typically uses endpoint agents, cloud identity providers, and software-defined perimeters. OT equipment often cannot run agents, may lack modern operating systems, and operates in environments where uptime is critical. OT Zero Trust must work at the network layer without touching endpoints. Trout Access Gate applies it from one appliance per site, connected beside the network, with nothing installed on the machines.

No. Access Gate enforces Zero Trust through overlay networking and proxy-based access control at the network layer. PLCs, HMIs, SCADA systems, and legacy equipment are protected without installing any software on them.

Yes. Access Gate is an appliance that connects beside your existing network. It creates an overlay network on top of the existing infrastructure. No IP changes, no VLAN reconfiguration, no recabling required.

Access Gate runs entirely on-premise with no cloud dependency. All policy enforcement, logging, and identity verification happen locally. It supports fully air-gapped, hybrid, and classified environments.

Access Gate works at the network layer and supports any IP-based protocol. Specific protocol awareness includes Modbus TCP, OPC UA, and common industrial protocols. The proxy layer can enforce access control per-protocol and per-session.

Firewalls filter traffic by IP and port rules. VLANs segment at the switch level. Neither verifies identity. Access Gate adds identity-based access control on top of existing firewalls and VLANs. It does not replace them. It adds the identity layer they were never designed to provide.

Deploy Zero Trust on your OT network.

Talk to the Trout team about your environment, deployment options, and compliance requirements.

Talk to sales