Security News

A Week of Major Outages: Not Cyberattacks, but a Warning About Fragile Systems

The Register · 18 Nov 2026
Key Takeaway Plan for your own systems to fail, not just to be attacked, by knowing your critical dependencies and rehearsing how your business keeps working when they go down.

A string of disruptive outages across the United States has left many people wondering whether a coordinated cyberattack is under way. According to The Register, the evidence points elsewhere. The NSA said its internal classified network, NSANet, suffered a "temporary degradation during scheduled routine maintenance". Apple users reported problems with services including iCloud, the App Store and Apple Pay, and retail stores were reportedly disrupted too.

The week began with outages at major US banks including JPMorgan Chase, Bank of America and US Bank. Chase blamed "a software bug in on-premise hardware systems" and said there was no evidence of a cyber link. Last week, the FAA grounded all planes after copper wiring problems during an L3Harris network upgrade, and Microsoft 365 went down, which Microsoft later blamed on a faulty software update pushed in July.

Security experts quoted in the article say the likely cause is ageing, under-funded infrastructure and complex dependencies. Remedio CEO Tal Kollender said a single misconfiguration, failed update or broken dependency can cause huge disruption without any attacker involved. She noted that for people who could not bank, fly or use email, the impact was real whatever the cause.

AI adds further pressure. The article says AI-assisted bug hunting has surfaced more than 100,000 CVEs this year, and Microsoft's Patch Tuesday has disclosed over 1,000 vulnerabilities in each of the past two months. Halcyon's Cynthia Kaiser warned that the rush to patch creates friction and outages, and that these moments of distraction leave gaps for opportunists, including through social engineering. Stairwell's Mike Wiacek said regular outages are the new normal, and that patching alone will not deliver security.

Why it matters

Most security programs invest in detecting attackers, but these outages show that failed updates, misconfigurations and hidden dependencies can stop a business just as completely. The assumption that patching faster is enough breaks down when patching itself, at higher volume, causes disruption. Leaders must now treat change management and resilience as security controls, and expect attackers to exploit the confusion around outages.

What to do

  • Map the systems and suppliers your critical business processes depend on.
  • Test updates on a small group of systems before rolling them out widely.
  • Warn staff to treat unsolicited contact during an outage with suspicion, since attackers may exploit the disruption.
  • Set governance and access limits before letting AI agents change configurations or reach sensitive systems.
Building or buying AI systems? Governing them under ISO 42001 ->

Summarised by CISO AI from The Register, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.