A practical guide to enabling remote OT access without compromising safety, availability or operational continuity.
Published: 20 August 2026 | Last reviewed: 10 September 2026 | 8 min read
Remote access allows authorised people to connect to operational technology systems from another location. It can support fault finding, engineering work, vendor support and emergency response when on-site access is not practical.
In OT, remote connectivity can also create a pathway into systems that control physical processes. A secure approach makes access necessary, authorised, limited in scope and visible to the teams responsible for the operation.
The goal is not to prevent all remote access. It is to ensure each connection has a defined purpose, uses a controlled access path and can be monitored, reviewed and removed when no longer needed.
Remote access can deliver real operational benefits. It can help teams respond to faults sooner, reduce travel to remote or regional sites, bring specialist vendor expertise into an incident and improve the coordination of maintenance work.
However, a remote connection can also provide an entry point into systems that operate physical equipment and processes. In an OT environment, the consequences of compromise may extend beyond information loss. They can include disrupted production, equipment damage, loss of visibility or control, safety impacts, and interruptions to essential services.
Common remote-access risks include:
An OT cyber security risk assessment can help identify remote-access pathways, the systems they can reach and the operational consequences that could arise from a compromise.
Remote access should exist for a defined operational purpose, not simply because it is convenient.
Typical OT use cases include:
Each use case should have an accountable owner, an approved access path and clear technical boundaries. For example, a vendor supporting one PLC or one application should not automatically receive broad visibility of the wider OT environment.
A practical OT remote-access design should apply the following principles.
Specify why access is needed, who needs it, which systems it supports and when it may be used. If the operational benefit is unclear, permanent connectivity is rarely justified.
Remote users should connect through a documented and approved path, rather than directly from the internet to an OT network, engineering workstation, PLC, HMI or SCADA server.
Use individual accounts and multi-factor authentication for employees, administrators, contractors and vendors. Avoid shared accounts wherever practical.
Provide each user access only to the systems, applications and actions required for the approved task. Avoid broad network access and unnecessary administrative rights.
Enable access only when it is needed, using approved maintenance windows, scheduled sessions or an access-approval process. Remove access when the task is complete.
Use segmentation to control traffic flows between corporate IT, remote users, intermediary systems and OT networks. Limit the systems a remote session can reach.
Log remote sessions and review activity. Maintain the ability to suspend access quickly during a suspected compromise, incident or unstable operating condition.
Vendor support is often necessary in OT, particularly where an organisation relies on specialist equipment, proprietary software or legacy systems. It should be managed as a controlled operational activity, not as a permanent exception.
The same principles used for employee and administrator access apply to vendors and contractors: use named accounts, multi-factor authentication, approved access paths and access that is limited to the systems and time window required for the task.
For higher-risk support work, record the session and the changes made. Your OT asset inventory should identify systems with external support arrangements, their responsible system owner and the remote-access pathways associated with each asset.
There is no single remote-access architecture that suits every OT environment, as a small remote site, manufacturing facility and multi-site critical-infrastructure operator will each have different constraints, operational requirements and legacy technology. However, a secure design will generally separate remote users from OT systems through a series of controlled layers:
A managed employee or vendor device connects through an approved encrypted remote-access service.
The user authenticates with an individual account, multi-factor authentication and an approved access request or entitlement.
The connection terminates at a controlled gateway, VPN concentrator, zero-trust access service or equivalent approved entry point.
The user reaches a segregated environment containing services such as jump hosts, remote desktop gateways, patch repositories or data-transfer services.
The user connects to an approved intermediary system rather than directly to OT assets.
Firewall rules and segmentation permit only the required protocol, destination and service for the approved task.
The user accesses only the specific engineering workstation, application server, HMI, SCADA system or other approved system needed to perform the work.
This design reduces direct exposure, limits lateral movement and makes access easier to approve, monitor, review and isolate.
Many organisations have accumulated remote-access methods over time through vendor support arrangements, urgent maintenance needs, site upgrades and temporary workarounds.
Start by developing a clear view of every remote-access pathway into the OT environment. Include permanent and temporary connections, vendor tools, VPNs, cloud services, remote desktop services, cellular links and unmanaged access methods.
Ask these questions:
Use the answers to prioritise improvements. Begin with pathways that provide broad access, reach safety or production-critical systems, rely on shared credentials, lack multi-factor authentication, cannot be adequately monitored or cannot be quickly isolated.
Australian industrial and critical-infrastructure organisations should design remote connectivity around safety, reliability and continuity of operations.
The Australian Cyber Security Centre’s secure connectivity principles for operational technology provide useful guidance for balancing remote connectivity with operational resilience. The principles emphasise risk-based design, limited exposure, controlled data flows and planning for isolation.
AS IEC 62443 provides a recognised framework for applying security requirements across OT systems, security architecture, suppliers and lifecycle activities. It is particularly relevant where remote access affects zones and conduits, identity and access control, change management and supplier support.
NIST Special Publication 800-82 also recognises that OT security controls need to address the performance, reliability and safety requirements of operational environments.
Implicit OT helps industrial and critical-infrastructure organisations review remote-access pathways, improve vendor and privileged access, and reduce cyber exposure while protecting safety and operational continuity.
