- Offshore oil and gas platforms, FPSOs, and subsea control systems are high-value targets for state-sponsored and criminal cyber threat actors, with the convergence of industrial control systems (ICS) and IT networks creating attack surfaces that did not exist when legacy offshore equipment was designed and installed.
- The Triton/TRISIS malware attack on a Middle Eastern petrochemical facility’s Safety Instrumented Systems in 2017 — the first known cyberattack specifically targeting industrial safety systems — established a new threat model for the offshore industry: adversaries willing and technically capable of causing physical process failures and bypassing the safety layers designed to prevent catastrophic accidents.
- Regulatory frameworks including IMO Resolution MSC-FAL.1/Circ.3 (Guidelines on Maritime Cyber Risk Management), the IEC 62443 standard for industrial automation and control system security, and NIST Cybersecurity Framework are converging toward mandatory requirements for offshore asset operators, with BSEE and NSTA both actively developing cyber risk management guidance for their respective jurisdictions.
The Offshore Cyber Threat: More Real Than Most Operations Teams Believe
Ask an offshore installation manager in 2010 whether their platform was at risk from a cyberattack, and the honest answer — reflecting the state of knowledge at that time — would have been “unlikely; we’re not connected to the internet.” Ask the same question in 2026, and the honest answer is “yes, significantly — and here’s how.” The transformation of offshore oil and gas infrastructure from isolated, analogue systems to internet-connected, digitally integrated operational environments has happened over approximately 15 years, driven entirely by commercial logic: remote monitoring, predictive maintenance, digital twins, real-time production optimisation, and the administrative efficiency of cloud-based data management all require connectivity. But connectivity that serves legitimate business purposes also creates pathways for illegitimate access.
The offshore industry’s cyber threat landscape involves three broad categories of adversary. State-sponsored actors — primarily those with strategic interests in disrupting energy infrastructure, obtaining commercially sensitive exploration data, or demonstrating capability for coercive purposes — represent the highest-capability threat. Criminal ransomware operators seeking financial gain represent the most frequent source of actual incidents. Insider threats — whether disgruntled employees, contractors with system access and malicious intent, or individuals who are wittingly or unwittingly used as entry vectors by external actors — represent a persistent and difficult-to-defend-against risk category.
IT/OT Convergence: The Attack Surface That Changed Everything
The fundamental cybersecurity challenge for offshore infrastructure is the convergence of Information Technology (IT) systems — the enterprise networks, business applications, and internet-connected systems familiar from corporate environments — with Operational Technology (OT) systems — the SCADA systems, distributed control systems (DCS), programmable logic controllers (PLCs), and safety instrumented systems (SIS) that actually control physical processes on the platform or vessel. Historically these were completely separate: OT systems were air-gapped (physically isolated from any network connection), used proprietary industrial protocols (Modbus, DNP3, PROFIBUS) that bore no resemblance to TCP/IP networking, and ran on hardware with 20-year lifecycles that made software patching a theoretical rather than practical concern.
The commercial drive for connectivity has progressively eroded these separations. Remotely accessible production data, digital twins that require real-time OT data feeds, cloud-based condition monitoring that aggregates sensor data from multiple platforms, and remote support access for vendor engineers who need to troubleshoot DCS issues without travelling offshore — all of these legitimate capabilities require connectivity between OT and IT systems. And every connection between OT and IT is a potential attack path from the internet-connected IT environment into the process-controlling OT environment.
Modern offshore platforms typically have a demilitarised zone (DMZ) architecture that sits between the OT and IT networks, providing a controlled interface point with firewalls, data diodes, and jump server architectures that theoretically prevent direct IT-to-OT access while allowing data to flow from OT systems for monitoring and analytics purposes. In practice, the effectiveness of these DMZ architectures varies enormously — from properly designed and maintained solutions with regular penetration testing to legacy configurations that have accumulated unplanned connectivity paths over years of operational additions and vendor access provisions.
The Triton/TRISIS Warning: When Hackers Target Safety Systems
The 2017 Triton (also called TRISIS) malware attack on the Safety Instrumented System (SIS) of a Middle Eastern petrochemical facility — later attributed to a Russian state-sponsored group known as Sandworm — was a watershed event for industrial cybersecurity globally and should be required reading for every offshore operations and HSE professional. The attackers had already compromised the facility’s DCS — giving them control over the process — when they also compromised the Triconex SIS manufactured by Schneider Electric. The SIS is the last line of defence: the independent safety system that monitors process conditions and initiates emergency shutdown (ESD) if the DCS fails to control a dangerous process excursion.
By compromising the SIS, the attackers were attempting to disable the safety barrier that would have prevented a catastrophic process accident (explosion, toxic release, or fire) if they had then deliberately caused a process upset via the compromised DCS. In the event, an unintentional programming error in the Triton malware caused the SIS to initiate a safe shutdown rather than disabling itself — the facility’s process was halted, the attack was discovered, and a potential catastrophic accident was averted. But the incident demonstrated with terrifying clarity that state-sponsored adversaries are willing and technically capable of targeting offshore industrial safety systems with the intent of bypassing them — not just for data theft or ransomware, but potentially to cause physical accidents.
The Colonial Pipeline Lesson for Offshore: Ransomware Causes Physical Consequences
The 2021 Colonial Pipeline ransomware attack — in which the DarkSide criminal ransomware group encrypted the IT systems of the US East Coast’s primary petroleum pipeline operator, causing the operator to proactively shut down pipeline operations as a precautionary measure — illustrated a different but equally important cyber risk scenario: that an attack on the IT side of an energy infrastructure company, without directly touching any OT systems, can cause physical supply disruption significant enough to trigger gasoline shortages across multiple US states. The operators’ decision to shut down the pipeline was precautionary — they could not confirm that the ransomware had not spread to OT systems — but it was commercially and operationally devastating regardless.
For offshore oil and gas operators, the Colonial Pipeline lesson is that an IT ransomware attack that does not touch a single DCS or SCADA system can still force production shutdown through precautionary operational response. Production accounting systems, hydrocarbon metering data, helicopter scheduling, logistics management, procurement systems — all of these IT-side functions support offshore operations, and their unavailability creates operational confusion and potential safety implications even without any direct OT compromise. Ransomware response planning for offshore operators therefore needs to address the IT-side operational continuity scenario as seriously as the OT-intrusion scenario.
Regulatory Requirements: Where Is the Industry Going?
The regulatory framework for offshore cyber risk management is converging toward mandatory requirements from multiple directions. IMO Resolution MSC-FAL.1/Circ.3 — the Guidelines on Maritime Cyber Risk Management — became effectively mandatory for ship management systems under ISM Code requirements from January 2021. Vessels operating under the International Safety Management (ISM) Code must demonstrate that cyber risk management is integrated into their Safety Management System (SMS), covering hardware and software systems, operational technology, and crew training.
IEC 62443 — the international standard for industrial automation and control system security — provides the technical framework for OT cybersecurity that is increasingly referenced in offshore industry contract requirements and regulatory guidance. Its zone-and-conduit model, security levels (SL 1 through SL 4), and requirements for system integrators and product suppliers are being adopted as the baseline specification for new offshore control system installations and upgrades. The IEC 62443 framework is not simple to implement on legacy offshore installations built before cybersecurity was a design consideration, but its adoption as an industry reference standard has created a common language and technical baseline for OT cybersecurity across the sector.
Practical Defences: What Offshore Operators Are Doing
Leading offshore operators — bp, Shell, Equinor, TotalEnergies, and ExxonMobil among the majors — have invested significantly in offshore cybersecurity over the past five to seven years. The practical measures being implemented include network segmentation and OT/IT separation review and remediation (identifying and closing unintended connectivity paths between OT and IT networks), privileged access management (ensuring that vendor remote access is controlled, monitored, and time-limited rather than providing standing access), and OT-specific security monitoring solutions that can detect anomalous behaviour within industrial control system protocols without requiring the OT environment to be fully network-connected.
Cyber incident response planning — developing and exercising the procedures for responding to a confirmed OT compromise on an offshore installation, including the decision criteria for production shutdown, communications protocols, and recovery procedures — is a growing focus area. The offshore industry equivalent of a blowout response drill is a cybersecurity incident response exercise, and the most sophisticated operators are now conducting these regularly, testing both the technical response procedures and the operational decision-making under simulated conditions of system compromise and partial information.
The human dimension — offshore workforce cyber awareness, secure behaviour training, and the management of USB drives, personal devices, and remote access on offshore installations — is where most actual security incidents originate. Social engineering, phishing emails that compromise credentials, and the casual introduction of malware through maintenance laptops or USB devices are the realistic attack vectors for most threat scenarios rather than the sophisticated supply-chain compromises of state actors. Building cyber hygiene into offshore workforce culture — treated with the same seriousness as permit-to-work systems and personal protective equipment compliance — is the most practical near-term security improvement available to most offshore operators.

