SCADA at Remote, Unmanned Sites: Lessons from Upstream Oil & Gas
An Industrial Cyber feature published on 20 October 2026 gathers views from Dragos, OMV Petrom and a former CISO on securing satellite, cellular and radio links to unmanned sites. The guidance applies to anyone running distributed operations.
On 20 October 2026, Industrial Cyber (Anna Ribeiro) published a feature on how upstream oil and gas operators protect SCADA systems running over satellite, cellular and radio links to remote sites. The article draws on contributions from executives at Dragos and OMV Petrom and a former energy-sector CISO. This summary is based on the first part of the piece; the final section, with Roya Gordon's commentary on secure remote access, was not reviewed and is not covered here.
The problem: distance, thin staffing, remote access
Wells, gathering systems and offshore platforms depend on a mix of communication links, and many sites have minimal staff or none at all. If a link is compromised, an attacker can intercept, manipulate or disrupt SCADA traffic and field devices, with few people on site able to notice.
The weakest point identified is remote access. Vendors and contractors must reach unattended sites, and shared credentials, always-on VPNs and unmonitored third-party connections are all potential entry points. In addition, centralized remote operations centers and their gateways become high-value targets: a single access point can affect many wells at once. Finally, platform safety systems must remain isolated, especially where production and control data cross bandwidth-limited links.
The figures cited
These figures are reported in the article and attributed to Dragos and Tosi; we have not verified the original reports.
- According to Dragos's 2026 OT/ICS review, poor IT/OT segmentation appears in 29% of oil and gas cases, the highest share of any sector.
- The same review describes VOLTZITE compromising cellular gateways in US oil and gas infrastructure and then moving undetected to engineering workstations.
- In a Tosi survey of 100 upstream and midstream OT leaders in the US, 87% say they are confident they could detect a breach within 24 hours, but only 16% cite continuous OT monitoring as the basis for that confidence.
What the experts recommend
Michael Hoffman (Dragos) recommends a defensible architecture, the second of the SANS five critical controls for ICS cybersecurity. In practice this means firewalls between SCADA servers and outstations that restrict traffic by IP, port, protocol and sometimes application; industrial firewalls at the outstations; encrypted links (VPN, IPsec or SD-WAN); and certificate-based authentication where protocols allow it. The hardest parts are legacy RTUs and radio networks designed for reliability rather than authentication. For Hoffman, visibility is essential, because preventive controls will eventually fail.
Albert Vartic (OMV Petrom) notes that remote SCADA at unmanned sites is mainly for monitoring. Remote commands should be limited to safe, predefined actions, while shutdowns remain local. He suggests alarm limits, plausibility checks and cross-checks between instruments and systems, with links using native encryption plus VPN/IPsec. The real difficulties, in his view, are inconsistent site configurations, weak credential lifecycle management, poor visibility on intermittent links and uncontrolled vendor access.
Minimize remote control, maximize reliable monitoring, and verify against approved baselines.
Dragos adds phishing-resistant authentication, close session monitoring, and routing access through segmented, monitored zones rather than directly into OT networks.
Why this matters beyond oil and gas
Pipelines, distribution networks, remote water facilities and unmanned plants share the same dispersion and thin staffing. Anyone running edge-heavy operations can take a practical checklist from this feature.
Operational takeaways:
- design for limited remote control, with predefined commands and local shutdowns;
- monitor intermittent links too, comparing observed state against approved baselines;
- manage vendor access with individual credentials, monitored sessions and intermediate zones instead of permanent VPNs;
- treat legacy RTUs and radios as a known risk: segment them, filter them with industrial firewalls and compensate with visibility.