• Cybersecurity Glossary
Secure Remote Access to OT: ZTNA vs VPN
Secure remote access to OT is about letting engineers and third party vendors reach industrial systems from outside the plant without exposing the network. The traditional tool, a VPN, places the user on the network and grants broad access, which is a serious risk in flat OT environments. ZTNA (Zero Trust Network Access) is the modern alternative: it grants per application access based on verified identity, and adds approval, time limited access windows and session recording. This page explains why the VPN is a risk, how ZTNA differs, and where Teldat fits with be.OT and ZTNA.
Why is OT remote access different?
Remote access to operational technology (OT) is not the same problem as remote access to IT. OT runs the physical processes of a plant, a utility or a factory: the controllers, HMIs and sensors that keep production moving and, often, keep people safe. When something goes wrong there, the consequence is not a slow application but a stopped line or a safety hazard.
Yet remote access to OT is unavoidable. Engineers need to diagnose equipment without driving to the site, and third party vendors need occasional access to the machines they supply and maintain. The question is not whether to allow remote access, but how to allow it without turning a convenience into an open door to the most sensitive part of the business.
That is where the choice between a VPN and ZTNA becomes decisive. Both let someone connect from outside, but they grant access in fundamentally different ways, and in an OT environment that difference is the difference between a contained connection and a broad exposure. The rest of this page explains why.
Why is a VPN a risk in OT?
A VPN was built for a simple goal: put a remote user onto the network as if they were in the building. Once connected, they are trusted broadly. In IT that is already a concern; in OT it is a serious risk, for several reasons.
None of this means a VPN is useless; it means it is the wrong model for reaching sensitive OT assets, where a single wrong action can stop production or endanger safety. The problem is the implicit, broad trust a VPN grants, and that is precisely what ZTNA removes.
How does ZTNA work for OT?
Zero Trust Network Access (ZTNA) starts from the opposite assumption to a VPN: no user or device is trusted by default, and access is granted to a single application or device rather than to the network.
When an engineer or vendor requests access, ZTNA verifies their identity and context and then opens a connection only to the specific asset they are authorized for, for example one HMI or one PLC. Everything else on the OT network stays invisible, which means it cannot be scanned, discovered or reached. This is sometimes called the dark cloud model, because unauthorized assets are hidden rather than merely blocked.
For OT this flips the risk. Instead of a remote session landing on the plant network and being trusted to roam, it lands on exactly one device and nothing more. A compromised remote laptop can no longer reach across the environment, because there is no network level access to inherit in the first place. Least privilege, which is hard to enforce with a VPN, becomes the default.
Per application, not per network: this is the core idea. A VPN answers the request “let me onto the network”; ZTNA answers the request “let me reach this one device.” In an OT environment, where the network is the crown jewels, granting access to one device instead of the whole network is the single biggest reduction in risk that remote access can make.
ZTNA vs VPN for OT compared
The table sets the two approaches side by side on the points that matter most for industrial remote access. The pattern is consistent: the VPN grants broad, standing, hard to audit access, while ZTNA grants narrow, temporary, fully observed access.
| Dimension | VPN | ZTNA |
|---|---|---|
| Access granted | The whole network | One application or device |
| Trust model | Broad, implicit once connected | Least privilege, verified per session |
| Visibility of other assets | Reachable on a flat network | Invisible (dark cloud) |
| If a device is compromised | Lateral movement across OT | Confined to one asset |
| Session approval | Typically none | Approval before the session starts |
| Time limits | Standing access | Time limited access windows |
| Auditability | Little to none | Session recording and logging |
| Fit for third party vendors | Persistent accounts, risky | Temporary, controlled, observed |
Read as a whole, the comparison explains why OT security teams are moving away from VPNs for access to critical assets. The VPN is not insecure by accident; it does exactly what it was designed to do, which is place a user on the network. For OT, that design is the problem, and ZTNA’s per application model is the answer.
Controls that matter for OT
Per application access is the foundation, but what makes ZTNA genuinely suitable for OT is the set of controls it adds around each session. These are the capabilities to look for when securing remote access to industrial systems.
Approval before access
A session can require explicit approval before it begins, so an operator at the plant authorizes a remote engineer or vendor in the moment, rather than access being always on. This keeps a human in control of who touches the process and when.
Time limited access windows
Access can be granted only for a defined maintenance window and then automatically closed, so a vendor who needs an hour gets an hour, not a standing account. Access that exists only when needed cannot be abused the rest of the time.
Session recording and monitoring
Everything done during a remote session can be recorded and logged, giving a full audit trail of who did what on which device. In OT, where a change can affect a physical process, this accountability is as important as prevention, and it supports compliance.
Verified identity and device posture
Before any of the above, ZTNA verifies the identity of the user and can check the posture of their device, so access is tied to a known person on an acceptable device, not merely to a credential that could be stolen.
ZTNA and segmentation together
Secure remote access does not stand alone. It works best on top of a well segmented OT network, and the two solve different halves of the same problem.
Network segmentation, including microsegmentation and the zone and conduit model promoted by standards such as IEC 62443, governs how systems inside the plant can talk to each other. It contains movement within the environment, so that even if something reaches one zone it cannot freely spread to others.
ZTNA governs how people and external systems reach into the plant from outside. It ensures that a remote session lands only on the intended asset. Put together, segmentation limits lateral movement inside, while ZTNA limits what remote access can touch from outside. A strong OT posture uses both: a segmented network means that even an authorized remote session is confined to its zone, so a single mistake or compromise stays contained.
Teldat be.OT and ZTNA
Teldat addresses secure remote access to OT by combining two parts of its portfolio: its OT security offering, be.OT, and the ZTNA built into be.Safe Pro. One maps and contains the environment, the other controls how it is reached from outside, and both are delivered from a European base.
be.OT: visibility and microsegmentation
be.OT provides visibility of industrial assets and microsegmentation of the OT network, so the environment is mapped and divided into zones rather than left flat. This is the foundation that makes remote access safe, because it means even an authorized session sits inside a contained segment.
ZTNA: per application remote access
On top of that, the ZTNA in be.Safe Pro provides per application remote access. An engineer or vendor reaches only the device they are authorized for, with identity verified and every other asset kept invisible, replacing the broad access of a VPN with least privilege access to one asset at a time.
One European solution, centrally managed
Because Teldat also makes the industrial routers and manages everything through the Cloud Net Manager (CNM) platform, segmentation and secure remote access are delivered and operated together rather than bolted on from different vendors. Network, OT security and remote access sit in one place.
Teldat’s approach: as a European manufacturer of industrial routers and security software, Teldat combines be.OT for OT visibility and microsegmentation with ZTNA for per application remote access, managed centrally on CNM, so remote access to OT lands on one asset on a segmented network rather than broadly on a flat one. It is made in Europe under European jurisdiction, supporting digital sovereignty. The specific remote access controls available, such as approval workflows, time limited access windows and session recording, should be verified with Teldat for a given product and software version.
FAQ’s about secure remote access to OT
❯ Why is a VPN a risk for OT remote access?
A VPN was designed to place a remote user onto the corporate network and trust them broadly once connected. In OT that is dangerous because industrial networks are often flat, so a VPN session can reach far more than the one machine the user actually needs. If the remote device is compromised, or a third party vendor credential is stolen, the attacker inherits that broad network access and can move laterally toward controllers and critical systems. A VPN also gives little visibility into what the remote user does once inside, and access tends to be standing rather than limited to a task. In an environment where a wrong action can stop production or endanger safety, broad, unmonitored access is exactly the wrong model.
❯ How is ZTNA different from a VPN for OT?
ZTNA grants access to a specific application or device rather than to the network. When a user connects, their identity and context are verified, and they are given a connection only to the asset they are authorized for, while everything else stays invisible. For OT this changes the model completely: instead of a remote engineer landing on the plant network, they reach one HMI or one PLC and nothing more. ZTNA also brings controls a VPN lacks, such as approval before a session starts, time limited access windows, and session recording for audit. The result is least privilege, per application access that is auditable and controllable, which fits the safety and uptime requirements of OT far better than broad VPN access.
❯ What controls does ZTNA add for third party vendor access?
Third party vendors are one of the biggest remote access risks in OT, because they often need occasional access to specific equipment but are outside the organization’s direct control. ZTNA addresses this with per application access so a vendor reaches only the device they service, approval workflows so a session must be authorized before it begins, time limited access windows so access exists only during the agreed maintenance window and then closes, and session recording so everything the vendor does is logged and auditable. Together these turn vendor access from a standing open door into a controlled, temporary and fully observed connection.
❯ Does ZTNA replace network segmentation in OT?
No, they work together. Network segmentation, including microsegmentation and the zone and conduit model of standards like IEC 62443, limits how systems inside the plant can talk to each other. ZTNA governs how people and external systems reach into the plant from outside. A strong OT security posture uses both: segmentation contains movement within the environment, while ZTNA ensures that remote access lands only on the intended asset and nothing else. Secure remote access is most effective when it sits on top of a well segmented network, so that even an authorized session is confined to its zone.
❯ How does Teldat secure remote access to OT?
Teldat approaches OT remote access by combining its OT security offering, be.OT, with the ZTNA built into be.Safe Pro. be.OT provides visibility of industrial assets and microsegmentation of the OT network, so the environment is mapped and contained rather than flat. ZTNA then provides per application remote access on top of that, so an engineer or vendor reaches only the authorized device, with identity verification and the connection kept invisible to everyone else. Because Teldat also makes the industrial routers and manages everything centrally through the CNM platform, segmentation and secure remote access are delivered as one European solution. The specific controls available, such as approval and session recording, should be verified with Teldat for a given product and software version.
Secure remote access to your OT with Teldat
Teldat combines be.OT for OT visibility and microsegmentation with ZTNA for per application remote access, managed centrally on CNM. Replace broad VPN access with least privilege access to one asset at a time, from Europe.

