The Risk & Reward Of Distributed Industrial Control
This talk analyzes the security implications of increasingly distributed industrial control systems (ICS) and the expansion of the attack surface due to remote connectivity. It highlights how the shift from air-gapped environments to networked, cloud-integrated operations introduces new vectors for adversary interaction with critical infrastructure. The speaker emphasizes the necessity of validating communications and implementing robust security controls to mitigate risks like those seen in the KA-SAT and Colonial Pipeline incidents. The presentation serves as a strategic overview for security professionals assessing the resilience of distributed OT environments.
The Silent Collapse of Distributed Industrial Control Systems
TLDR: Industrial control systems are shifting from air-gapped, localized setups to highly distributed, cloud-connected architectures, creating massive new attack surfaces. Adversaries can now target these systems via remote communication links, potentially inducing catastrophic physical failures without ever touching the primary business network. Security researchers and pentesters must prioritize validating these remote communication channels and testing for protocol manipulation, as traditional perimeter defenses are no longer sufficient.
The myth of the air-gapped industrial control system is dead. For years, security professionals operated under the assumption that critical infrastructure was physically isolated from the internet, protected by the sheer inconvenience of geography and proprietary hardware. That era ended when economic pressure and the need for remote telemetry forced operators to bridge the gap between field devices and centralized management platforms. Today, wind farms, pipelines, and power grids rely on a complex web of satellite links, cellular modems, and cloud-based management services. This transition has turned what were once isolated, hard-to-reach targets into nodes on a global, interconnected network.
The New Reality of Distributed Operations
Modern industrial operations require constant data flow. Whether it is a wind turbine in a remote field or a compressor station along a pipeline, the need for real-time monitoring and remote maintenance has necessitated the adoption of technologies like VSATs and 5G mesh networks. These systems are not just sending telemetry; they are receiving control commands. When you move from a hard-wired, local control room to a distributed model, you introduce multiple touchpoints where an adversary can intercept, replay, or inject traffic.
The KA-SAT incident serves as a stark reminder of this vulnerability. By targeting the satellite communication network, attackers were able to disrupt not only military operations but also the remote management of thousands of wind turbines. The turbines did not necessarily fail because their internal logic was compromised, but because the communication link that allowed for remote control and health monitoring was severed. When a system is designed to rely on constant connectivity for operational stability, losing that link is functionally equivalent to a denial-of-service attack on the physical process itself.
Protocol Manipulation and the Risk of "Frosty Goop"
For a pentester, the shift to distributed control means the focus must move away from traditional IT-centric exploitation and toward the manipulation of industrial protocols. We are seeing tools like FrostyGoop emerge, which specifically target Modbus communications to manipulate heating systems. These attacks do not require a sophisticated exploit chain against a hardened OS; they rely on the fact that many industrial protocols lack basic authentication or integrity checks.
If you are assessing a distributed OT environment, your engagement should focus on the communication path between the field device and the control center. Can you intercept the traffic? Can you replay a command? If the protocol is unencrypted and lacks a robust check-sum mechanism, you are essentially looking at a clear-text command-and-control channel.
Consider a scenario where you have access to a remote terminal unit (RTU) communicating over a cellular link. If the traffic is not encapsulated in a secure tunnel, you can use standard packet manipulation tools to inject commands. A simple payload might look like this:
# Example of a Modbus function code injection to force a register change
# This assumes access to the serial or network interface of the field device
modbus_client --write-register 40001:1 --address 10.0.0.5
This is not about finding a zero-day in a PLC firmware; it is about exploiting the lack of transport security in a system that was never designed to be exposed to a wide-area network.
The Pentester’s Role in OT Resilience
Asset owners often struggle to balance the need for operational efficiency with the reality of an expanded attack surface. As a researcher, your value lies in demonstrating that these remote links are not just "pipes" for data, but critical components of the control loop. During an engagement, you should stress-test the assumptions of the blue team. What happens when the satellite link drops? Does the system fail into a safe state, or does it hang in an indeterminate condition?
The OWASP Industrial Control Systems Security guidance provides a solid foundation for understanding these risks, but the practical application requires a deep understanding of the specific field protocols in use. You need to look for opportunities to induce a loss of view or a loss of control. If you can prevent the operator from seeing the current state of the process, or if you can prevent them from sending a stop command, you have achieved a significant impact.
Moving Beyond Perimeter Defense
Defenders must stop treating the network perimeter as the primary line of defense. In a distributed environment, the perimeter is everywhere. Implementing robust, end-to-end encryption for all remote telemetry is a baseline requirement, but it is rarely enough. You must also implement integrity verification for all control commands. If a command arrives at a field device, the device should be able to verify that the command originated from a trusted source and has not been tampered with in transit.
We are currently in a transition period where the convenience of distributed control has outpaced our ability to secure it. The next few years will likely see more incidents where the failure of a communication link leads to physical consequences. For those of us in the security community, the task is clear: we need to stop treating these systems as black boxes and start rigorously testing the protocols and communication paths that keep them running. If you are not looking at the traffic between the field and the cloud, you are missing the most critical part of the modern industrial attack surface.
Vulnerability Classes
Tools Used
Target Technologies
Attack Techniques
Up Next From This Conference

Breaking Secure Web Gateways for Fun and Profit

Listen to the Whispers: Web Timing Attacks That Actually Work

Abusing Windows Hello Without a Severed Hand
Similar Talks

Inside the FBI's Secret Encrypted Phone Company 'Anom'

Kill List: Hacking an Assassination Site on the Dark Web

