Why AI Means Less Time To Respond To Cyberattacks

🔍 Read the full analysis: Why AI Means Less Time To Respond To Cyberattacks on ThorstenMeyerAI.com

Buying for a business?Offer from Amazon

Get business pricing on office and shipping supplies

• Business-only prices and quantity discounts
• Tax-exempt purchasing
• Multiple users, one account, clear invoices

Create a free Business account →Free to register

As an affiliate, we earn on qualifying purchases.Hide

U.S. agencies and Microsoft have documented attackers using AI-generated scripts and an agentic framework in activity targeting industrial control systems and cloud tenants, underscoring how automation can compress the time defenders have to respond. The reports also include important limits: most activity in Microsoft’s account did not succeed, and a successful sign-in does not by itself prove data was accessed.

A joint advisory issued Aug. 18 by the NSA, CISA, FBI, Department of Energy and Environmental Protection Agency says actors used AI-generated exploitation scripts against internet-reachable Siemens S7 programmable logic controllers, or PLCs. These industrial computers can operate equipment such as pumps, valves and production lines. The advisory describes reconnaissance and capability development involving models from the S7-200 to the S7-1500, including safety controllers, and says the activity may be preparation for operational effects against critical infrastructure.

The agencies say attackers used scripts disguised as legitimate monitoring tools and built with the open-source snap7 library. They warn the approach can reduce the expertise and time required for attacks. Their recommended defenses include cataloguing PLCs, updating firmware, preventing direct internet access, blocking TCP port 102 at network perimeters, separating operational technology from corporate IT, requiring multifactor authentication for remote OT access and monitoring for unauthorized S7 writes.

In an Oct. 21 report, Microsoft Threat Intelligence said the China-state-aligned group Storm-0940 used ARTEX, an open-source multi-agent penetration-testing framework, in activity associated with the ConnectWise Cloud Backup compromise. Microsoft said the actor used credentials for the backup application to attempt sign-ins across more than 2,250 tenants. From Oct. 10 to 14, Microsoft recorded more than 151,000 failed logons in a password-spraying campaign, with a peak rate of 2,900 per minute; none succeeded. In several attacks, Microsoft said, the period from initial targeting to privileged cloud access was under three hours.

Microsoft cautioned that most targeting was unsuccessful and that an affected application or successful sign-in does not necessarily mean data was accessed. ConnectWise, which disclosed the compromise on Oct. 16, said existing backup archives showed no indication of compromise. It suspended Cloud Backup, SaaS Security and Cloud Management while investigating.

Faster Attacks, Tighter Response Windows

The reported cases matter because they show how automation can make familiar attack steps—scanning, password spraying and adapting scripts—run at greater speed and scale. That does not establish that AI has produced a wholly new kind of attacker. It does mean a security team may have less time between an initial attempt and a consequential account or system compromise, as Microsoft’s reported sub-three-hour incidents illustrate.

For industrial operators, a remotely reachable controller can connect a cyber intrusion to physical processes. For organizations that rely on cloud applications, credentials and trusted third-party integrations can provide routes into multiple tenants. Those risks make basic controls particularly relevant: limiting exposure, reviewing application permissions, using phishing-resistant authentication where available, and rehearsing how to isolate systems and revoke access.

AI may also assist defenders. OpenAI said AI helped identify critical vulnerabilities in PHP that were patched on Oct. 21, before attackers exploited them, and forecast that AI-found critical vulnerabilities would increase sharply in coming months. That forecast is not a count of future flaws, but it points to a practical consequence: organizations may face more pressure to triage and apply patches quickly.

Three Reports, Different Evidence

The source material describes several developments, rather than a single newly announced attack. The Aug. 18 government advisory concerns industrial controllers; Microsoft’s Oct. 21 report concerns Storm-0940, ARTEX and a third-party backup service; and a July 30 report from Palo Alto Networks’ Unit 42 describes a separate agent experiment. Keeping the cases separate matters: their actors, targets and evidence are not interchangeable.

Unit 42 described a Chinese-speaking actor that connected the DeepSeek model to the Hermes Agent framework and directed it through Telegram. According to the report, when an initial exploit failed, the agent searched GitHub for another approach. Unit 42 said an agent carried out hundreds of hours’ worth of manual targeting analysis in minutes. That is a report about a specific observed operation, not proof that all AI agents can perform the same work or that the activity succeeded in every case.

The reports describe AI as part of an attacker’s toolchain, not as an independent super-hacker. The central change is the potential to automate routine work and keep it running continuously. That can benefit defenders too, while increasing the pace at which both sides scan, identify weaknesses and act on them.

“This is not a theoretical risk—it is an active threat.”

— Joint Cybersecurity Advisory by the NSA, CISA, FBI, DOE and EPA, Aug. 18

What the Reports Do Not Establish

The reports do not establish that AI was responsible for every step in the incidents, or that every attempted intrusion led to access. Microsoft’s data records large numbers of failed logons, and the company explicitly says most targeting did not succeed. ConnectWise said its existing backup archives showed no indication of compromise; the full scope and consequences of the incident were not settled in the source material.

The agencies describe activity against PLCs and assess it as likely preparation for operational effects, but the material does not confirm that attackers caused physical disruption. It also does not provide a measured, sector-wide estimate of how much AI has shortened incident response times.

A security leader cited in the source material predicted that conditions could worsen before improving, describing a possible “vulnerability tsunami” within months and roughly 18 months to hold on. That is an expert opinion, not a measured forecast or a finding from the cited agency and company reports. OpenAI’s expectation that AI-found critical vulnerabilities will rise sharply is also a forecast; its scale and timing remain uncertain.

Controls and Investigations Ahead

Organizations with industrial systems can follow the agencies’ specific recommendations: identify every PLC, remove direct internet exposure, patch firmware, segment operational networks, secure remote access and monitor controller traffic for changes outside approved windows. Companies using third-party cloud applications can review what permissions those apps hold, check sign-in logs, and have a process to disable integrations and revoke credentials during an incident.

Security teams should also set patch priorities and response procedures before a high-volume alert or vulnerability disclosure arrives. Practised incident response can clarify who can isolate a system, contact a provider, preserve logs and notify affected users. For individuals, securing the primary email account with multifactor authentication and a unique password can reduce the risk that a compromised inbox becomes a route into other services.

The next useful signals will be findings from ConnectWise’s investigation, any further technical details from Microsoft or the agencies, and evidence about whether AI-assisted vulnerability discovery materially changes patch volumes. Until then, the confirmed reports point to faster automated activity—and a need for tested, established defenses—rather than a quantified prediction of what comes next.

Key Questions

What did U.S. agencies report about AI and industrial control systems?

A joint advisory said actors used AI-generated scripts against internet-reachable Siemens S7 PLCs. The agencies described reconnaissance and preparation, and warned that the activity could reduce the time and technical expertise needed for attacks.

Did Microsoft confirm that all targeted cloud tenants were breached?

No. Microsoft reported attempts across more than 2,250 tenants and said most targeting was unsuccessful. It also cautioned that an affected app or successful sign-in does not necessarily mean data was accessed.

Does the reporting show AI attacks are impossible to stop?

No. The reports document AI-assisted activity, including many failed attempts. They support concern about speed and scale, but do not show that defenses cannot block attacks.

What should companies do in response?

The agencies recommend securing and inventorying PLCs, keeping firmware updated, blocking direct internet access, segmenting IT and operational networks, requiring multifactor authentication for remote OT access, and monitoring for unauthorized controller activity. Cloud customers should review third-party app permissions and practise incident response.

Is a wave of AI-found vulnerabilities confirmed?

No. OpenAI said AI helped find critical PHP vulnerabilities patched on Oct. 21 and forecast that AI-found critical vulnerabilities would increase sharply. The expected increase is a forecast, and its size and timing are not yet known.

Source: ThorstenMeyerAI.com