SANS Report: OT/ICS Cyber Incidents Rising, 40% Cause Downtime

SANS 2025 Report Reveals Alarming Rise in OT/ICS Incidents, with Ransomware Driving Disruptions

INFORMATIONAL
November 21, 2025
5m read
Industrial Control SystemsThreat IntelligenceRansomware

Related Entities

Organizations

Products & Tech

Operational Technology (OT)Industrial Control Systems (ICS)

Other

Ransomware Jason D. Christopher

Full Report

Executive Summary

The SANS Institute has released its "2025 State of ICS/OT Security Report," painting a concerning picture of the escalating cyber threats facing critical infrastructure and industrial sectors. The survey of over 330 OT security professionals reveals that cyber incidents are becoming more frequent and more disruptive. Key findings show that 21.5% of organizations experienced a cybersecurity incident impacting their Operational Technology (OT) or Industrial Control Systems (ICS) in the past year. A staggering 40.3% of these incidents led to operational disruption and downtime. Ransomware has emerged as a dominant threat, being the root cause of nearly 38% of incidents. The report underscores a critical weakness in remote access security and a troubling "resilience gap," where recovery times lag far behind detection, posing a direct threat to safety and operational continuity.


Threat Intelligence Overview

The SANS report provides critical data points on the current state of OT/ICS security:

  • Incident Frequency: More than one in five (21.5%) organizations experienced an OT/ICS incident in the last 12 months. This indicates that such events are no longer rare occurrences but a common operational risk.
  • Primary Threat: Ransomware is the leading cause of disruptive incidents, accounting for 37.9% of attacks. This shows a continued trend of financially motivated actors successfully crossing the IT/OT divide.
  • Initial Access Vector: Unauthorized external connections were the primary initial access vector, responsible for 50% of all incidents. This points to weaknesses in perimeter security, particularly around remote access solutions for vendors and employees.
  • Impact: The impact is tangible and severe. 40.3% of incidents resulted in operational downtime, directly affecting production, delivery, and safety.

Key Findings and Analysis

The Resilience Gap

The report identifies a dangerous disparity between detection and recovery capabilities. While detection is improving (nearly half of incidents are detected within 24 hours), recovery is lagging. A significant portion of organizations (19-20%) reported that it took over a month to fully remediate an incident, with some taking more than a year. This prolonged recovery period means extended downtime, increased financial loss, and sustained risk to safety and the environment.

Remote Access Risk

The prevalence of unauthorized external connections as the main entry point is a major red flag. The survey found that only 13% of organizations have implemented advanced controls for remote access, suchas session recording or just-in-time access. This lack of maturity in securing remote connections provides a wide-open door for threat actors to enter OT networks.

Investment Priorities

Looking ahead to 2026-2027, the report notes that organizations are planning to prioritize investments in key defensive areas:

  • Asset Visibility: You can't protect what you can't see. Gaining a comprehensive inventory of all OT assets is the top priority.
  • Threat Detection: Enhancing capabilities to detect malicious activity within the OT network.
  • Securing Remote Access: Recognizing it as a major weakness, organizations are planning to invest in stronger controls for remote connections.

Impact Assessment

The findings of the SANS report have broad implications for all industries that rely on OT and ICS, including Manufacturing, Energy, Chemicals, and Transportation.

  • Increased Safety Risk: Downtime in an OT environment is not just a financial issue; it can have serious safety and environmental consequences. The inability to control industrial processes poses a direct threat to human life.
  • Economic Disruption: Attacks on critical infrastructure can have cascading effects, disrupting supply chains and essential services, leading to widespread economic damage.
  • Erosion of the IT/OT Air Gap: The report confirms that the concept of a completely "air-gapped" OT network is largely a myth. The convergence of IT and OT, driven by the need for remote monitoring and data analytics, has created new pathways for threats to enter industrial environments.

Detection & Response Recommendations

Based on the report's findings, organizations should focus their detection and response efforts on:

  • OT Network Visibility: Deploy OT-aware network monitoring solutions that can passively identify assets, map communication patterns, and detect anomalous behavior without disrupting sensitive processes. This is the foundation of any OT security program. This aligns with D3-NTA: Network Traffic Analysis.
  • Baseline Normal Behavior: Establish a baseline of normal network traffic and device behavior within the OT environment. Alerts should be triggered by deviations, such as new devices, unusual communication protocols (e.g., IT protocols like SMB or RDP in a control network), or connections to the internet from OT assets.
  • IT/OT Boundary Monitoring: Pay close attention to all traffic crossing the boundary between the IT and OT networks. This is a critical chokepoint and the most likely path for a threat to pivot into the industrial environment.

Mitigation and Strategic Guidance

To address the risks highlighted in the report, organizations must adopt a strategic approach to OT security:

  1. Implement Robust Network Segmentation: Enforce strict segmentation between IT and OT networks using a DMZ architecture. Further micro-segmentation within the OT network can limit the lateral movement of an attacker. This is a crucial implementation of M0930 - Network Segmentation (ICS version of M1030).
  2. Harden Remote Access: All remote access into the OT network must be brokered through a secure gateway in the DMZ. Enforce MFA, use jump hosts, and implement session monitoring and recording. Eliminate all direct, unauthorized external connections.
  3. Develop an OT-Specific Incident Response Plan: Generic IT incident response plans are not sufficient for OT. The OT IR plan must prioritize safety and operational continuity, and the team must be trained on the unique constraints of industrial environments.
  4. Create a Defensible Architecture: Design the OT network with security in mind. This includes creating a comprehensive asset inventory, identifying communication pathways, and establishing security zones based on the Purdue Model or similar frameworks.

Timeline of Events

1
November 21, 2025
This article was published

MITRE ATT&CK Mitigations

Implement a defensible architecture with strong segmentation between IT and OT networks, as well as micro-segmentation within OT zones, to limit the spread of an attack.

Strictly control and filter all traffic entering the OT network, allowing only expected protocols and sources.

Maintain regular, tested, and isolated backups of critical OT systems (e.g., HMI configurations, project files) to enable recovery from a ransomware attack.

Apply the principle of least privilege to all accounts, especially those used for remote access into the OT environment.

D3FEND Defensive Countermeasures

Given that 50% of OT incidents originate from unauthorized external connections, implementing robust Network Isolation is the most critical countermeasure. This goes beyond the legacy concept of an 'air gap' and focuses on creating a strictly controlled, defensible architecture. The primary tactical implementation is the establishment of a proper Industrial Demilitarized Zone (IDMZ) between the IT and OT networks. All traffic must terminate in the IDMZ; no direct connections between IT and OT should be permitted. Remote access for vendors or employees must be brokered through a secure jump host or remote access solution within the IDMZ, with MFA enforced. All traffic flowing from the IDMZ into the OT network must be restricted by firewall rules to only the necessary protocols, sources, and destinations (e.g., allowing only DNP3 traffic from a specific historian server to a specific control network segment). This strict enforcement of network boundaries and traffic flows directly mitigates the top initial access vector identified in the SANS report and is the foundational step in preventing IT-based threats like ransomware from impacting industrial operations.

To address the rise of ransomware in OT environments, organizations need visibility into the traffic within their control networks. Protocol-based Network Analysis, using an OT-aware Network Detection and Response (NDR) platform, is essential. These tools passively monitor network traffic and use deep packet inspection (DPI) to understand OT-specific protocols (e.g., Modbus, DNP3, S7). The key tactical recommendation is to deploy sensors at key network segments (e.g., spanning ports on switches in Levels 1, 2, and 3 of the Purdue model). The NDR system should be configured to baseline normal communication patterns and alert on any anomalies. For instance, an alert should trigger if an HMI running on a Windows machine suddenly starts an SMB file transfer to multiple PLCs, or if a device in the control zone attempts to communicate out to the internet. This provides early detection of the lateral movement and reconnaissance stages of a ransomware attack, allowing responders to act before the 'impact' stage (encryption) begins. This is far more effective than relying on traditional IT security tools that lack the context to understand normal vs. malicious OT traffic.

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

SANSOT SecurityICS SecurityCritical InfrastructureRansomwareThreat Report

📢 Share This Article

Help others stay informed about cybersecurity threats

Continue Reading