77% of UK Utilities Suffered Cyber Attacks on Legacy OT Systems in Past Year

Attacks on Legacy Systems Hit 77% of UK Utility Companies, Report Finds

HIGH
June 18, 2026
4m read
Industrial Control SystemsCyberattackPolicy and Compliance

Related Entities

Other

Bridewell United Kingdom

Full Report

Executive Summary

A new report from Bridewell, a cybersecurity services firm, paints a concerning picture of the state of security in the UK's utilities sector. The "Cyber Security in Critical National Infrastructure Report 2026" found that 77% of UK utility organizations were targeted by cyber attacks exploiting outdated software or legacy operational technology (OT) in the past year. This makes attacks on aging infrastructure the most common type of incident faced by the sector. The report underscores the significant operational risk posed by these attacks, with 47% of organizations suffering IT disruption and 32% experiencing disruption to production or services as a direct result.


Threat Overview

The report highlights that the utilities sector is caught between the long lifecycle of industrial control systems and the rapid evolution of cyber threats. Many critical OT assets, designed for decades of service, were not built with modern security in mind and are now connected to IT networks, exposing them to new risks. These legacy systems are often difficult to patch or take offline, making them persistent and attractive targets for attackers.

While attacks on legacy systems are the most common incident type (77%), utilities also face a barrage of other threats:

  • Phishing and Business Email Compromise (BEC): 76%
  • Malware: 74%
  • Supply Chain Attacks: These were noted as requiring the longest average response time (9.9 hours).

Technical Analysis

The attacks described are less about sophisticated zero-day exploits and more about adversaries taking advantage of fundamental security gaps. The primary technique is the exploitation of known, unpatched vulnerabilities in legacy software and hardware (T1210 - Exploitation of Remote Services). Because these OT systems often cannot be easily patched, vulnerabilities can persist for years.

Attackers often gain initial access through the IT network, typically via phishing (T1566 - Phishing), and then pivot to the less-secure OT environment. The lack of segmentation between IT and OT networks is a key enabling factor, allowing threats to move from a compromised email account to a critical control system (T1021.001 - Remote Desktop Protocol).

Impact Assessment

The consequences of these attacks are tangible and disruptive. The report quantifies the primary impacts on UK utilities:

  • IT Disruption/Outages: 47% of organizations
  • Increased Cybersecurity Spending: 42%
  • Data Loss: 35%
  • Revenue Loss: 34%
  • Disruption to Production/Services: 32%

The fact that nearly a third of organizations experienced disruption to their core operational services (e.g., power generation, water distribution) is a critical finding. It demonstrates that cyber attacks are no longer just an IT problem but a direct threat to the physical services on which the public depends.

IOCs — Directly from Articles

No specific Indicators of Compromise (IOCs) were provided in the source articles.

Cyber Observables — Hunting Hints

Security teams in the utilities sector should hunt for signs of IT-to-OT crossover:

Type
Network Traffic Pattern
Value
IT-to-OT RDP/SMB Traffic
Description
Monitor for any RDP or SMB connections originating from the corporate IT network and destined for the OT network, especially if not from a designated jump server.
Type
Log Source
Value
PLC/RTU Logs
Description
Look for unexpected configuration changes, firmware updates, or 'program stop' commands on Programmable Logic Controllers (PLCs) and Remote Terminal Units (RTUs).
Type
Process Name
Value
powershell.exe on HMI
Description
The presence or execution of PowerShell on a Human-Machine Interface (HMI) workstation is highly suspicious and could indicate an attacker attempting to script interactions with the control system.
Type
User Account Pattern
Value
IT Admin accounts logging into OT systems
Description
Any login to an OT system using credentials from the corporate IT domain should be investigated immediately.

Detection & Response

  1. OT Network Visibility: Deploy passive network monitoring tools specifically designed for OT environments (like Dragos or Nozomi Networks). These tools can identify legacy assets, baseline normal communication patterns, and alert on anomalous activity or the use of insecure industrial protocols.
  2. IT/OT Log Correlation: Ingest logs from both IT (e.g., Active Directory, firewalls) and OT (e.g., data historians, HMI event logs) into a central SIEM. Correlating events across the boundary is key to detecting pivot attempts.
  3. Honeypots: Deploy OT-specific honeypots to safely detect and analyze attacker TTPs targeting industrial protocols like Modbus or DNP3.

Mitigation

  1. Network Segmentation: This is the most critical mitigation. Implement a robust, defensible architecture that strictly separates IT and OT networks. All communication between the two should pass through a secured DMZ with deep packet inspection. This aligns with M1030 - Network Segmentation.
  2. Virtual Patching: For legacy systems that cannot be patched, use an Intrusion Prevention System (IPS) with rules specific to industrial vulnerabilities to create a 'virtual patch', blocking exploit traffic before it reaches the vulnerable asset.
  3. Asset Inventory: Maintain a comprehensive and up-to-date inventory of all OT assets, including their software/firmware versions and known vulnerabilities. This is a foundational step for risk management.
  4. Compensating Controls: Where patching is not feasible, implement compensating controls such as application allowlisting on HMIs, disabling unnecessary ports and services on OT devices, and enforcing strict access control.

Timeline of Events

1
June 18, 2026
This article was published

MITRE ATT&CK Mitigations

Implement a Purdue Model-aligned architecture with a DMZ between IT and OT to prevent attackers from pivoting between environments.

Mapped D3FEND Techniques:

Establish a risk-based patching program for OT, and use compensating controls like virtual patching for systems that cannot be updated.

Mapped D3FEND Techniques:

Maintain a comprehensive inventory of all OT assets to understand the attack surface and prioritize security efforts.

Utilize OT-specific threat intelligence to understand adversary TTPs and proactively hunt for them in the industrial environment.

D3FEND Defensive Countermeasures

The most effective defense for UK utilities against attacks on legacy systems is strict network isolation based on the Purdue Model. This involves creating a hardened security perimeter between the corporate IT network (Level 4/5) and the industrial OT network (Levels 0-3). All traffic must flow through a DMZ (Level 3.5) where it can be inspected by firewalls with deep packet inspection for industrial protocols. Within the OT network, further micro-segmentation should be implemented to isolate critical control processes from the broader supervisory network. This ensures that a compromise in the IT environment (e.g., via phishing) cannot easily pivot to the OT environment, and a compromise within one part of the OT network is contained and cannot spread to other production lines or sites.

To protect unpatchable legacy systems, utilities must deploy OT-aware Network Traffic Analysis. This involves using passive sensors to monitor all traffic on the industrial network without impacting operations. The NTA platform should be configured to learn the baseline of normal operations—which PLCs talk to which HMIs, using what protocols, and at what frequency. The system should then alert on any deviation from this baseline. For example, an alert should trigger if an engineering workstation suddenly attempts to communicate with a PLC using a function code it has never used before, or if any device attempts to connect to the internet. This behavioral approach can detect attacks even when no known vulnerability signature exists.

For legacy Windows-based HMIs and engineering workstations that cannot be easily replaced, application hardening is a critical compensating control. This involves using application allowlisting (e.g., AppLocker) to ensure that only pre-approved, essential software can execute. All other executables, scripts, and DLLs should be blocked by default. This prevents attackers who gain access to an HMI from running malicious tools, PowerShell scripts, or other malware. Additionally, system hardening should include disabling unused services, closing unnecessary ports, and enforcing strict user permissions to reduce the attack surface of these vulnerable but critical endpoints.

Sources & References

Staggering 77% of utility companies hit by cyber attacks
Energy Live News (energylivenews.com)

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

UtilitiesUKLegacy SystemsOT SecurityICSCritical InfrastructureBridewell

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.