🔍
Showing 503 articles
← Return to All Dispatches / Tech & AI Systems
#463 Tech & AI Systems • Updated Oct 27, 2026

Two Decades of Cyber Conflict: The Journey from Web Disruption to ICS Exploitation

Ethics • Computing • Urban Environment

1. Introduction: The Shifting Paradigm of Infrastructural Conflict

The virtualization of critical civilian infrastructure has fundamentally altered the calculus of international conflict, allowing adversarial states and proxy groups to disrupt the foundational operations of a society without firing a kinetic shot[1]. Over the past two decades, the evolution of state-sponsored cyber operations has progressed from volumetric Distributed Denial of Service (DDoS) floods targeting public web portals—pioneered during the 2007 cyberattacks against Estonia—to architecturally aware intrusions targeting the Programmable Logic Controllers (PLCs) that govern physical water, hydrological distribution, and energy infrastructure[3, 5].

This report examines that two-decade trajectory, analyzing the network mechanics of the 2007 Estonian campaign, the legal thresholds of armed force established in the Tallinn Manual, the forensic anatomy of recent Iranian-linked intrusions into Unitronics PCOM industrial controllers, and the structural remediation frameworks required to restore defense-in-depth across the Purdue Enterprise Reference Architecture.

2. The 2007 Estonian Precedent and the Tallinn Manual

In April and May 2007, following a diplomatic dispute over the relocation of the Soviet-era Bronze Soldier of Tallinn memorial, Estonia endured a 22-day digital siege widely recognized as the first major state-aligned cyber campaign[3, 8]. Initial waves beginning April 27 relied on ICMP ping floods, malformed HTTP queries, and UDP packet floods, rapidly escalating into coordinated global botnet assaults mobilizing 1 to 2 million compromised machines across 175 jurisdictions[4, 9, 11]. Traffic analysis by Arbor Networks’ Security Engineering and Response Team (ASERT) recorded sustained attack streams reaching 90 Mbps for up to ten hours per wave—sufficient in 2007 to saturate parliamentary email servers, overload Domain Name System (DNS) resolvers, and force Estonia’s largest commercial bank, Hansabank, offline on May 10[3, 11, 13].

To preserve domestic banking and government communications, the Estonian Computer Emergency Response Team (CERT-EE) implemented Border Gateway Protocol (BGP) blackholing to sever external international IP routes[4, 8]. Although the attacks synchronized with Russian political dates (such as May 9 Victory Day) and adapted dynamically to countermeasures, decentralized botnet routing preserved plausible deniability and prevented definitive legal attribution[3, 4].

In response, NATO established the Cooperative Cyber Defence Centre of Excellence (CCDCOE) in Tallinn in 2008, convening legal scholars to draft the Tallinn Manual on how international law governs cyber warfare[3]. Under Rules 80 and 82 of Tallinn Manual 2.0, cyber operations during armed conflict are bound by International Humanitarian Law prohibitions against targeting civilian survival infrastructure, and an independent cyber operation constitutes a "use of force" or "armed attack" under UN Charter Article 51 when its scale and effects match kinetic force[15, 18, 19]. Under the "loss of functionality" doctrine endorsed by states such as Germany, disabling an Industrial Control System (ICS) such that physical component replacement or manual system reinstallation is required crosses the threshold of physical destruction, alongside territorial "due diligence" obligations[15, 21]. Consequently, modern threat actors deliberately calibrate gray-zone OT disruptions to inflict economic and psychological costs just below the threshold of kinetic military retaliation[4, 7].

3. Asymmetric OT Doctrine and the PCOM Protocol Vulnerability

Following heightened Middle Eastern geopolitical tensions in late 2023 and early 2026, Iranian-affiliated threat actors shifted from long-term espionage—such as a six-year infiltration of Israel’s Institute for National Security Studies[27]—toward direct disruption of Western operational technology[7, 24].

Threat Group DesignationAffiliationPrimary TargetsTypical Operational Tactics
CyberAv3ngersIslamic Revolutionary Guard Corps Cyber-Electronic Command (IRGC-CEC)Water/Wastewater, Energy, Manufacturing, specifically targeting Israeli-manufactured equipmentExploitation of default credentials on exposed PLCs, HMIs defacement, process disruption
MuddyWaterMinistry of Intelligence and Security (MOIS)Government, Defense, Telecommunications, EnergyLiving-off-the-land techniques (PowerShell, WMI), lateral movement, long-term persistence

Operating under the IRGC-CEC, CyberAv3ngers systematically compromised municipal water and wastewater utilities—including the Aliquippa Municipal Water Authority in Pennsylvania and regional pumping stations in County Mayo, Ireland—causing simultaneous loss of view and loss of control that forced operators onto manual bypass[7, 24, 31]. Rather than deploying zero-day malware against public health or wastewater monitoring systems, the attackers exploited Unitronics Vision series PLCs exposed directly to the public internet on TCP port 20256[6, 24, 32].

Unitronics silicon controllers communicate with engineering workstations via the proprietary PCOM (Programmable Controller Communication) protocol encapsulated over TCP/IP[24, 35, 36]. PCOM operates in two request-response modes: PCOM ASCII (delimited by / request and /a response magic bytes for homogeneous data) and PCOM Binary (prefixed by /_OPLC for heterogeneous memory operations)[35]. Once connected, hexadecimal opcodes grant complete read/write authority over PLC memory and ladder logic[35].

Function Code (Hexadecimal)Protocol Action Description
0x01 / 0x81Read Memory
0x02 / 0x82Check Password
0x0C / 0x8CGet PLC Name
0x10 / 0x90Find Resource
0x41 / 0xC1Write Memory
0x42 / 0xC2Reset Upload Password
0x4D / 0xCDRead Operand

Because legacy industrial protocols lack high-entropy cryptographic session authentication, Unitronics PLCs relied on an optional application-level password initialized by default to "1111" (CWE-1188)[24, 32, 42]. Using Shodan and Censys queries accelerated by large language models, actors scanned industrial ports, authenticated with "1111", overwrote pump logic, and defaced Human-Machine Interfaces (HMIs)[7, 24].

Associated TCP/UDP PortIndustrial ProtocolTarget Device/Function
TCP 20256Unitronics PCOMUnitronics Vision/Samba PLCs
TCP 502ModbusGeneric ICS process control
TCP 44818EtherNet/IPRockwell Automation / Allen-Bradley PLCs
TCP 4840OPC UACross-vendor ICS communication
UDP 47808BACnetBuilding and facility automation
TCP 20000DNP3Electric utility SCADA protocol

4. Architectural Atrophy in the Purdue Model and CISA Remediations

The exposure of Level 1 PLCs directly to the internet reflects the widespread erosion of the Purdue Enterprise Reference Architecture (PERA), which segments industrial networks into hierarchical trust zones separated by a Level 3.5 Industrial Demilitarized Zone (DMZ)[37, 38, 43].

Purdue Model LevelZone DesignationDescription of Components and Functions
Level 5Enterprise NetworkCorporate IT functions, internet connectivity, email servers, and broad enterprise resource planning (ERP) systems.
Level 4Business LogisticsSite-specific business systems, production scheduling, and local IT operations.
Level 3.5Industrial DMZThe Demilitarized Zone. A secure buffer housing firewalls, jump servers, and proxies to prevent direct communication between IT and OT.
Level 3Site OperationsManufacturing execution systems (MES), data historians, and site-wide OT management. The highest level of the OT network.
Level 2Supervisory ControlHuman-Machine Interfaces (HMIs) and distributed control systems monitoring specific local processes.
Level 1Basic ControlProgrammable Logic Controllers (PLCs) and Remote Terminal Units (RTUs) executing automated process logic.
Level 0Physical ProcessThe physical equipment: sensors, actuators, pumps, and valves interacting with the real world.

Rapid IT/OT convergence, cloud-connected IIoT telemetry bypassing Level 3.5, and unmonitored vendor remote-maintenance links have collapsed this segmentation across municipal utilities[24, 32, 38, 46]. To restore resilience in alignment with CISA’s Cross-Sector Cybersecurity Performance Goals (CPGs) and Advisory AA23-335A, critical infrastructure operators must implement five core engineering controls[24, 48, 49]:

  1. Eliminate Internet-Facing OT Assets: Remove all PLCs and HMIs from public IP space and require multi-factor VPN authentication terminating inside a Level 3.5 jump host[24, 28].
  2. Eradicate Default Credentials: Mandate unique, high-entropy passwords prior to commissioning any controller[24].
  3. Enforce Bidirectional Boundary Filtering: Apply default-deny firewall rules blocking inbound and outbound traffic on industrial ports (TCP 20256, 502, 44818, 4840, 20000; UDP 47808) to prevent C2 beaconing[24, 45].
  4. Deploy Behavioral Anomaly Detection: Use statistical network baselining to detect living-off-the-land lateral movement (PowerShell, WMI) by groups such as MuddyWater[6, 24].
  5. Install Unidirectional Data Diodes: Enforce hardware-level one-way optical replication from Level 3 historians to Level 4 enterprise analytics, physically preventing remote command injection[26].

5. Conclusion: Defending the Cyber-Physical Frontier

From the 90 Mbps botnet floods against Estonia in 2007 to the manipulation of municipal water PLCs via exposed PCOM opcodes, cyber conflict has matured into a persistent instrument of gray-zone coercion. Because legacy industrial controllers operate for decades without native cryptographic authentication, securing civilian lifelines requires combining strict Purdue Model network segmentation, hardware data diodes, and CISA CPG baseline hygiene with enforceable international legal norms under the Tallinn framework.

Works Cited

  1. The Bulwark - Substack, https://substack.com/@thebulwark/note/c-307931108
  2. NewsNow: The Independent News Discovery Platform, https://www.newsnow.com/us/
  3. 2007 cyberattacks on Estonia - Wikipedia, https://en.wikipedia.org/wiki/2007_cyberattacks_on_Estonia
  4. 2007 cyber attacks on Estonia - NATO StratCom, https://stratcomcoe.org/cuploads/pfiles/cyber_attacks_estonia.pdf
  5. CISA, FBI warn that Iran-linked hackers are expanding target set for, https://www.cybersecuritydive.com/news/cisa-fbi-iran-hackers-target-water-energy/826025/
  6. Rigorous Evaluation of Machine Learning Intrusion Detection for, https://www.mdpi.com/2076-3417/16/14/7206
  7. Multistate cyber campaign targeting US water and wastewater sector, https://shieldworkz.com/blogs/threat-intelligence-update-multistate-cyber-campaign-targeting-us-water-and-wastewater-sector-operational-technology
  8. Analysis of the 2007 Cyber Attacks against Estonia from the Inf, https://ccdcoe.org/uploads/2018/10/Ottis2008_AnalysisOf2007FromTheInformationWarfarePerspective.pdf
  9. (PDF) The Estonian Cyberattacks - ResearchGate, https://www.researchgate.net/publication/264418820_The_Estonian_Cyberattacks
  10. CCDCOE analysis of the 2007 cyber attacks against Estonia, https://ccdcoe.org/library/publications/analysis-of-the-2007-cyber-attacks-against-estonia-from-the-information-warfare-perspective/
  11. Estonia Cyber Attack, April-May 2007 | Computer Science - EBSCO, https://www.ebsco.com/research-starters/computer-science/estonia-cyber-attack-april-may-2007
  12. Cyber Attacks Explained - CSIS, https://www.csis.org/analysis/cyber-attacks-explained
  13. Estonia: Cyber Window into the Future of NATO - NDU Press, https://ndupress.ndu.edu/Portals/68/Documents/jfq/jfq-63/jfq-63_58-63_Laasme.pdf?ver=Gmp2P_MaR_5WUw4ETKCnXA%3D%3D
  14. Cyber attacks against Estonia (2007), https://cyberlaw.ccdcoe.org/wiki/Cyber_attacks_against_Estonia_(2007)
  15. International Legal Perspectives on Cyber Operations: A Common, https://ccdcoe.org/uploads/2026/06/International_Legal_Perspectives_on_Cyber_Operations.pdf
  16. TALLINN MANUAL 2.0 - International Law Moot Court, https://ilmc.univie.ac.at/fileadmin/user_upload/p_ilmc/Bilder/Bewerbung/Case_2/Michael_N._Schmitt_-_Tallinn_Manual_2.0_on_the_International_Law_Applicable_to_Cyber_Operations-Cambridge_University_Press__2017_.pdf
  17. Terminological Precision and International Cyber Law - Lieber Institute, https://lieber.westpoint.edu/terminological-precision-international-cyber-law/
  18. Communication Blackouts: Israeli Cyberattacks Against Civilians in, http://opiniojuris.org/2024/03/20/communication-blackouts-israeli-cyberattacks-against-civilians-in-gaza/
  19. The law of armed conflict generally (Chapter 16) - Tallinn Manual, https://www.cambridge.org/core/books/tallinn-manual-20-on-the-international-law-applicable-to-cyber-operations/law-of-armed-conflict-generally/E51C33369B1E84763B3CFD4C0CB8E943
  20. Tallinn Manual on the International Law applicable to Cyber Warfare, https://scispace.com/pdf/tallinn-manual-on-the-international-law-applicable-to-cyber-1ypzb2oq5n.pdf
  21. Germany's Positions on International Law in Cyberspace Part II, https://www.justsecurity.org/75278/germanys-positions-on-international-law-in-cyberspace-part-ii/
  22. LIMITE EN - Data, https://data.consilium.europa.eu/doc/document/WK-3320-2021-INIT/en/pdf
  23. The Sony and OPM Double Whammy: International Law and Cyber, https://scholar.smu.edu/cgi/viewcontent.cgi?article=1025&context=scitech
  24. A Threat Actor Landscape Assessment of ICS/OT Targeting in the, https://www.cloudsek.com/blog/a-threat-actor-landscape-assessment-of-ics-ot-targeting-in-the-2026-iran-us-conflict-and-the-scale-of-the-risk
  25. Welcome to the New Cyber Battleground | CISO Collective - Fortinet, https://www.fortinet.com/blog/ciso-collective/welcome-to-the-new-cyber-battleground
  26. The Evolving Threat: Iranian and Nation-State APT Cyber Operations, https://www.uscybersecurity.net/csmag/the-evolving-threat-iranian-and-nation-state-apt-cyber-operations-present-and-future/
  27. Haaretz Discloses Six-Year Iranian Penetration of Israel's INSS, https://zerodawn.tech/
  28. AI, the Iran-US Conflict, and the Threat to US Critical Infrastructure, https://www.cloudsek.com/blog/ai-the-iran-us-conflict-and-the-threat-to-us-critical-infrastructure
  29. Improving Resilience in Chemical Plant under Cyberattack by, https://bura.brunel.ac.uk/bitstream/2438/31895/1/FulltextThesis.pdf
  30. 18th International Conference on Cyber Conflict: Securing, https://ccdcoe.org/uploads/2026/05/CyCon_2026_Securing_Tomorrow_Proceedings.pdf
  31. Physical Security Engineering | Risk Management | Security, https://soybean-deer-akrk.squarespace.com/operational-analysis/blog-post-title-four-kb8br-z8sk7-sw4za-8nyce
  32. The County Mayo Water Hack: How a Default Password Took 180, https://netsecgroup.io/guides/county-mayo-water-hack-unitronics
  33. 2024 State of The Threat – A Year in Review, https://newsletter.radensa.ru/wp-content/uploads/2024/10/secureworks-state-of-the-threat-report-2024.pdf
  34. Volume 12 | Issue 1 July 2024, https://hcss.nl/wp-content/uploads/2024/07/Georgetown-Security-Studies-Review-Vol-12-1-Davis-Ellison-2024.pdf
  35. From Exploits to Forensics: Unraveling the Unitronics Attack | Claroty, https://claroty.com/team82/research/from-exploits-to-forensics-unraveling-the-unitronics-attack
  36. SASE for Water Utilities: NIS2 SCADA Security 2026 | Jimber, https://jimber.io/blog/sase-for-water-utilities-nis2-scada-security/
  37. What Is the Purdue Model for ICS Security? | A Guide to PERA, https://www.paloaltonetworks.com/cyberpedia/what-is-the-purdue-model-for-ics-security
  38. What Is the Purdue Model for ICS Security? - Zscaler, Inc., https://www.zscaler.com/resources/security-terms-glossary/what-is-purdue-model-ics-security
  39. Following Unitronics research, Claroty's Team82 debut tools to, https://industrialcyber.co/industrial-cyber-attacks/following-unitronics-research-clarotys-team82-debut-tools-to-combat-cyber-threats-in-critical-infrastructure/
  40. A Comprehensive Security Analysis of a SCADA Protocol, https://www.researchgate.net/publication/331974234_A_Comprehensive_Security_Analysis_of_a_SCADA_Protocol_from_OSINT_to_Mitigation
  41. Communication with the Vision™ PLC - Unitronics, https://www.unitronicsplc.com/Download/SoftwareUtilities/Unitronics%20PCOM%20Protocol.pdf
  42. CVE-2023-6448 — Unitronics Vision PLC and HMI Insecure Default, https://kev.5sn.com/2023/CVE-2023-6448.html
  43. What Is the Purdue Model? Definition, Level & Best Practices, https://www.sentinelone.com/cybersecurity-101/cybersecurity/what-is-the-purdue-model/
  44. The Purdue Model - Introduction to ICS Security Part 2 - SANS Institute, https://www.sans.org/blog/introduction-to-ics-security-part-2
  45. What Is the Purdue Model for ICS Security? | Fortinet, https://www.fortinet.com/resources/cyberglossary/purdue-model
  46. IT/OT/ICS Cybersecurity — Guide for Industry 2026 - EITT, https://eitt.academy/knowledge-base/it-ot-ics-cybersecurity-comprehensive-guide-for-industry/
  47. OT ICS Cybersecurity Threats: Tactics, Paths, Defenses - Group-IB, https://www.group-ib.com/resources/knowledge-hub/ot-ics-cybersecurity/
  48. Cross-Sector Cybersecurity Performance Goals - CISA, https://www.cisa.gov/cross-sector-cybersecurity-performance-goals/cross-sector-cybersecurity-performance-goals
  49. CISA rolls out cross-sector cybersecurity performance goals for, https://industrialcyber.co/critical-infrastructure/cisa-rolls-out-cross-sector-cybersecurity-performance-goals-for-critical-infrastructure-sets-benchmark-standards/
  50. CPG - CISA, https://www.cisa.gov/sites/default/files/2023-03/CISA_CPG_REPORT_v1.0.1_FINAL.pdf
  51. (TLP:CLEAR) CISA Releases Cybersecurity Performance Goals 2.0, https://www.waterisac.org/tlpclear-cisa-releases-cybersecurity-performance-goals-2-0-for-critical-infrastructure
  52. Cross-Sector Cybersecurity Performance Goals, Version 2.0 - CISA, https://www.cisa.gov/sites/default/files/2025-12/CPG_Report_2.0_508c.pdf