Refreshing the latest version...

Welcome to Kernel Panic, a weekly newsletter by Lily Hay Newman and Matt Burgess from inside the new world of privacy and digital security. To receive this newsletter in your inbox each week, sign up here.
Over the last week, you have surely noticed the disruptive streak of technical outages that hit everything from Outlook to Apple, a half dozen US banks, United Airlines, and even the NSA’s classified network. While there’s no evidence that these were cyberattacks, speculation has run wild about the cause—including a pervasive feeling that AI is to blame.
So let’s just be clear: The incidents were definitely not caused by some sort of coordinated AI hacking spree and, taken individually, they all seem to have routine explanations. But as AI impacts the dynamics of digital defense more and more, security researchers and analysts have increasingly concluded that AI pressures are starting to play a role in real-world tech failures.
AI-assisted vulnerability discovery has unleashed a torrent of software bugs. Attackers are then using AI tools to exploit those vulnerabilities faster, which puts more pressure than ever on organizations to quickly patch their systems. This leaves often under-resourced IT teams scrambling to evaluate a massive number of patches and push the updates to systems on which countless people and organizations rely. Researchers and practitioners have told us again and again that AI’s biggest impact is that it speeds everything up.
Microsoft’s massive 365 outage last week was caused by a flawed update in its infrastructure exacerbated by other network failures. Officials said this week that the NSA outage to its internal communication system was due to botched patching following October’s critical PHP updates. Apple also said its snafus this week related to an internal update. AI vulnerability discovery and the resulting patching are “putting tremendous strain on systems that weren’t built to handle that pace of change,” US senator Mark Warner said in a statement on Tuesday. And more “instability” could be coming, Microsoft CEO Satya Nadella said this week, because a “patch needs to go instantly from being available to being patched in production because it’s being exploited in the wild.”
External pressures and bugs in patches are not new, and they’ve always caused tech failures. Researchers also point out that many organizations around the world have a significant amount of what’s often called “tech debt,” because they have cut corners and failed to invest in upgrading and maintaining their digital systems for years. This practice was always risky, but organizations that didn’t have the resources or didn’t want to devote them to digital security could gamble with out-of-date systems and missing safeguards and typically avoid the worst consequences.
“Historically, even a couple of years ago, a vendor releases a patch for a nasty bug. You might have some time to do some validation and apply it,” says Joe Slowik, the director of threat research and cyber engineering at Dataminr. “Now, that may not even be an option, because we’re talking about turnaround times that completely defeat the ability to do patch verification.”