Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Secure Remote Access in OT?

Secure remote access in OT gives engineers and vendors a single brokered, authenticated, and recorded route into industrial systems, instead of the direct tunnels that cause most industrial incidents.

Illustration for the cybersecurity term Secure Remote Access in OT
Home / Blog / Cybersecurity Terms / What Is Secure Remote Access in OT?
17 November 2026

What Is Secure Remote Access in OT?

What Is Secure Remote Access in OT?

Remote access is how most attackers get into industrial environments, and it is also how most plants are kept running. A turbine vendor in Denmark adjusts a control parameter. An integrator in Manchester debugs a batch sequence at three in the morning. An on-call engineer checks an alarm from home. Removing remote access is not an option; making it a single, controlled, observed path is.

Two incidents frame the problem. The ransomware attack on Colonial Pipeline in May 2021 began with a password for a legacy virtual private network account that was still active and not protected by multi-factor authentication. In February 2021, an operator at a water treatment plant in Oldsmar, Florida watched the sodium hydroxide setpoint change on screen during a session established through a shared remote desktop tool; the city later indicated the change may have been an employee action rather than an intruder, but the shared, unmonitored access path was real either way.

What Good Looks Like

  1. One way in. All remote access terminates at a single brokered gateway in the industrial demilitarised zone. No direct VPN into a control network, no modem on a panel, no vendor appliance with its own cellular connection.
  2. Strong authentication, always. Multi-factor authentication for every account including vendor accounts, with phishing-resistant factors where the platform supports them.
  3. No shared credentials. Named accounts per individual, provisioned through the identity lifecycle and removed when the person leaves the supplier.
  4. Access on request, not standing. The account exists but is disabled until an operator enables the session, which bounds exposure to the work actually being done.
  5. Least privilege to a specific target. The session reaches one named host or device, not a subnet, and the protocol is brokered rather than routed.
  6. Operator in control. Someone on site can see the session and terminate it. On high-consequence systems, a physical enable switch gives operations an unambiguous veto.
  7. Recorded and reviewed. Full session recording for engineering access, with a sample reviewed rather than merely stored.
  8. Time-boxed. Sessions expire. Access granted for a commissioning campaign does not survive it.

Architecture in Practice

The common pattern is a jump host, or a commercial secure remote access product, sitting in the DMZ. The external user authenticates to the gateway and never obtains an IP route into the control network; the gateway establishes the onward connection and proxies the protocol. That design means a compromised vendor laptop cannot reach a controller even with valid credentials, because there is no path, only a brokered application session.

Where the risk justifies it, add a second hop: a hardened workstation inside the control network that holds the engineering tools, accessed only by screen transfer from the DMZ jump host. Files move through a scanned, logged transfer service rather than by drag and drop. The conduit carrying this traffic is inspected by an OT firewall and watched by passive monitoring, so that a legitimate session doing something illegitimate is still visible.

Managing Vendors Specifically

Standards and UK Expectations

IEC 62443-3-3 addresses this directly: SR 1.13 covers access via untrusted networks, SR 2.6 requires session termination, and SR 6.1 requires auditable records. For UK operators of essential services, the NCSC’s Cyber Assessment Framework asks under Principle B2 how remote and third-party access is controlled, and an assessor will want the register, the multi-factor evidence, and the session logs rather than a policy statement. The NCSC’s guidance on remote access and on supply chain security maps onto the same controls.

Where financial entities operate industrial estates, DORA adds its own third-party access expectations; where personal data is involved in session recordings, the UK GDPR requires the monitoring to be proportionate and disclosed to the people recorded.

At Privia Security, our OT-SCADA Penetration Test routinely starts where attackers do, by examining how remote access into your plant is actually configured rather than how it is documented.

FAQ – Frequently Asked Questions

Is a VPN Enough for OT Remote Access?

No. A VPN grants network-level reachability, so a compromised endpoint gains a route into your control network. Brokered access terminates the session at a gateway and proxies the application, meaning the remote machine never gets an IP path inwards. Use a VPN as transport if you wish, but put a broker behind it.

Should Operators Be Able to Veto a Remote Session?

On high-consequence systems, yes. A physical enable switch or an operator approval step in the access workflow gives the control room an unambiguous say over who is connected to the plant they are responsible for. It also creates a human record of why a session happened, which logs alone rarely capture.

How Long Should Session Recordings Be Kept?

Long enough to support investigation, typically six to twelve months, and defined in a retention schedule rather than left to disk capacity. Where recordings capture identifiable individuals, the UK GDPR requires a lawful basis, proportionality, and transparency with those being recorded, so set the period deliberately and tell vendors it applies to them.

What About Equipment with a Built-In Cellular Router?

Treat it as an unmanaged route into your plant until proven otherwise. Ask the supplier to disable it, or terminate it on a segment you control with no path to the control network. If neither is possible, document it as an accepted risk with compensating monitoring and raise it at the next contract review.

Related Terms

You May Be Interested In These

What Is the Cyber Resilience Act?

Cybersecurity Terms

17 November 2026

What Is the Cyber Resilience Act?

Read More
What Is an Insider Threat?

Cybersecurity Terms

17 November 2026

What Is an Insider Threat?

Read More