Best practice

Secure remote access for OT vendors: a 2026 baseline

Remote access remains one of the most common routes into OT. A clear, achievable baseline for vendor and engineering access in 2026.

Remote access is essential for OT operations and one of the most common entry points for attackers. Vendors, integrators and your own engineers need to reach systems quickly. The goal is not to block access but to make every path known, approved, protected and recorded.

The baseline

  1. One controlled path. All remote access terminates in the industrial DMZ on a dedicated gateway or jump host. No direct VPNs into control networks, no vendor-installed remote desktop tools, no forgotten cellular modems.
  2. Individual identities and MFA. Every person has a named account. Shared vendor accounts are retired.
  3. Just-in-time approval. Vendor access is disabled by default and enabled per request, for a defined time and system.
  4. Least access. Each vendor reaches only the systems they support.
  5. Session control. Sessions can be watched, recorded and terminated by site staff.
  6. Logging and review. Access logs go to monitoring and are reviewed periodically.
  7. Contracts that require it. Supplier agreements reflect these rules, supporting NIS2 supply-chain duties, IEC 62443-2-4 and standards such as Saudi Aramco SACS-002.

Finding what already exists

Most sites have more access paths than they think. Combine firewall rule reviews, contract lists, site walkdowns and interviews. Our remote access use case describes the process and a typical result.

Making it practical for operations

  • Give the control room a simple way to approve or deny a session.
  • Agree an emergency process for out-of-hours support.
  • Keep the vendor register current with contacts and contract end dates.

Measuring progress

Track a few simple indicators: number of known access paths, percentage behind the controlled gateway, shared accounts remaining and sessions reviewed. These numbers make progress visible to management.

How OTVista helps

Third-party & Remote Access keeps the path inventory, vendor register and approval records together, linked to Identity & Access Review. Our architecture review service can design the target access model.

Topics: OT remote access, vendor remote access security, secure remote access ICS, jump host OT, supply chain security OT, MFA OT

Frequently asked questions

How should vendors access OT systems remotely?

Through a single controlled gateway in the industrial DMZ, with individual accounts, MFA, just-in-time approval, least access and recorded sessions.

Are shared vendor accounts acceptable in OT?

They should be retired. Named accounts make access traceable and allow access to be removed when people or contracts change.

What standards address OT remote access?

IEC 62443-2-4 and 3-3, NIS2 supply-chain measures, NERC CIP-005 and supplier standards such as Saudi Aramco SACS-002 all include remote access requirements.

See OTVista in action

Book a demo of the platform or talk to us about your OT security priorities.

Book a demo