Build2 publishers2 min readPublished Updated
Five agencies, one Siemens S7 warning, and a claim that AI is writing the exploit scripts
CISA's advisory describes a mechanism, not a vulnerability: commercial scanners find the exposed PLC, and the agencies say AI tooling closes the distance from found to controlled.
The Engineer · Build desk

What happened
- CISA issued an advisory on Siemens S7-series PLCs co-authored with the NSA, FBI, Department of Energy and the EPA.
- Six sectors are named as most targeted, including water and wastewater, energy and food and agriculture.
- Operators are told to patch, isolate equipment from the internet as far as possible, tighten access control and monitor ICS traffic.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- exposure Any S7 that answers on a public address is inside the target set as the advisory defines it, because the selection criterion is exposure plus stale firmware, not a specific bug.
- constraint If hostile tooling is built on the same automation libraries integrators use, anomaly monitoring on the control network has little to distinguish, leaving isolation as the control that still bites.
- decision A small water utility deferring segmentation work is now deferring against a document its own federal agency signed, which changes how that deferral reads after an incident.
- contradiction The same report both names Iranian hackers and says no origin was specified, so operators cannot treat this as a geopolitically timed campaign they can wait out.
The reconnaissance in this advisory is not performed by the attacker. According to CISA, the actors use internet scanning services to find internet-exposed PLCs that are running outdated software or are otherwise poorly protected [3]. The quoted language describes a version-and-configuration condition rather than a single named flaw [3], which means the target list is generated continuously by third parties and refreshed without anyone attacking anything.
What historically sat between appearing in a scan result and being under someone else's control was labour: learning the protocol, matching firmware behaviour, building tooling that does not crash the device. The agencies say the actors are using publicly available information on these widely used controllers to develop exploits that permit remote access and control [1], and that AI tools are helping them identify additional attack vectors and possibly adapt to defensive measures operators have already put in place [7]. Read as an engineering statement, that is a claim about cost. The scanning half of the kill chain was already cheap; the advisory says the bespoke half is getting cheaper too.
The detail that undercuts the mitigation list is further down. Agencies say AI tooling can make malicious files look and behave like legitimate monitoring tools, built on open-source industrial automation libraries [8]. The fourth item operators are told to do is deploy cybersecurity measures that monitor industrial control systems for anomalies and possible malicious activity [9]. An anomaly detector tuned to spot malformed or unusual S7 traffic is being asked to flag a well-formed client using the same libraries an integrator would use. Of the four recommended controls, patching, isolation, access control and monitoring [9], the one that still works cleanly against the described adversary is the one that removes the device from the scan results in the first place.
The advisory also puts the loss in two ledgers at once: disruption of critical industrial processes, safety incidents, downtime or equipment damage, compromise of sensitive data, compliance violations, and cascading impacts across interconnected systems [6]. CISA states plainly that this is not a theoretical risk but an active threat [5].
On attribution, the reporting is not internally consistent. Tom's Hardware describes the warning as concerning Iranian hackers, then states the agencies did not specify where the attacks could originate [10]. It also notes the advisory landed less than a month after water infrastructure in several states was hit by cyberattacks thought to have come from Iran [11]. For an operator with an S7 answering on a public address, the flag on the origin changes nothing about the work.
What to watch
- Whether the agencies publish indicators or samples that substantiate the AI-generated tooling claim rather than asserting it.
- Whether public counts of internet-exposed S7 devices move in the weeks after the advisory, the only visible test of whether operators acted.
- Whether a formal attribution follows, given that the same report says the agencies declined to name an origin.