Zero Trust OT Remote Access: Putting the ZTNA Gateway on the Industrial Switch
On 16 November 2026 IIoT World published a summary of a session in which Cisco proposes running the ZTNA gateway directly on industrial switches, to close the ports left open after maintenance work. It is a vendor-driven proposal, but it comes with a checklist that is useful for any plant.
On 16 November 2026 IIoT World published a summary of a session held during the ICS Cybersecurity Day, devoted to zero trust remote access in OT networks. The speakers were Ruben Lobo and Pete Kavanagh of Cisco and Tim Householder of Worldwide Technology, moderated by Kevin Wood (Cisco). Because most of the speakers work for Cisco, the solution described is vendor-driven and should be read as such.
The problem: the "infinite" firewall rule
For a firmware update, a drive diagnosis or an integrator's check, a VPN tunnel or a firewall rule gets opened. Rarely is it closed again. The session called this the "infinite firewall rule" problem: connections into the control network pile up, and auditing them takes weeks or months, especially when each site handles remote access its own way.
There is also an operational cost: a plant technician often sits next to the vendor's laptop for the entire session to monitor what happens. That is maintenance time taken away from other work.
Port forwarding and undeclared connections
According to the report, in transportation and critical infrastructure, cellular modems with public IP addresses are installed and ports are forwarded to the assets. These often expose HTTP administration interfaces and have no firewall, so anyone who connects can move laterally to other devices on the same segment.
A second front is machine builders' shadow IT. Builders and integrators embed cellular gateways in machines for services such as predictive maintenance, and the plant owner often does not know. In one example cited, a customer discovered an undeclared connection to a cloud data historian during a review of data acquisition. SBOMs help with new supplies but do not solve the installed base; visibility tools and deep packet inspection often bring these hidden links to light.
Where to place the gateway
ZTNA verifies identity, device posture and authorization before granting access to specific resources. According to the speakers, most deployments place the gateway centrally, in the DMZ or at a higher Purdue level. Plants must then expose the IP addresses of drives, I/O and sensors upward through NAT and firewalls, flattening the segmentation they built with so much effort.
Cisco's approach makes the gateway a software function of industrial switches and routers, while the trust broker stays in the cloud (Cisco IoT Operations Dashboard). The gateway sits behind NAT and the zone firewall, reaches assets on their private IPs without exposing them, and the firewall needs just a single outbound rule on port 443. Integration with NAC is meant to prevent lateral movement: someone authorized on one drive cannot reach neighboring devices, and a firmware update session cannot be used to extract data from a PLC.
The claimed benefits are:
- time-limited sessions, with MFA and posture checks on the vendor's device;
- centralized session logging and scheduling;
- no dedicated gateway hardware, with lower costs and supply chain risk;
- no vendor laptops and no VDI extension into OT zones, which would weaken the Purdue/IEC 62443 conduits.
Costs and benefits are Cisco's claims: the article offers no independent data. In addition, the page we consulted cuts off before the section on how to get started, so the closing recommendations could not be verified. The underlying message is that zero trust in OT is a strategy, not the purchase of a single product.
What to do about it in a plant
Vendor remote access to machines and lines is routine in plants running MES and IIoT, so the checklist applies regardless of brand:
- audit permanent VPN and firewall rules and close those with no expiry;
- look for undeclared gateways inside machines, using network visibility tools;
- require access that is time-limited and bound to a single asset;
- write these requirements into contracts with machine builders and integrators.
Zero trust in OT is a strategy, not the purchase of a single product.
Whether you choose the gateway on the switch or another architecture, the point is the same: know who comes in, where, and for how long, and be able to prove that the access was closed.