CNN is reporting that the classified internal network of the National Security Agency, America’s electronic eavesdropping service, is down. This is the seventh major American system to fail in six days.
Nobody has found an attacker. Three of the failures began as routine upkeep. Edward Gibbon, the 18th-century English historian, filled six volumes of The Decline and Fall of the Roman Empire and blamed barbarians and Christianity. His American successor might point toward a Windows fix and a router in El Dorado, Arkansas. Let’s briefly run through each of the failures:
Markwayne Mullin, the Homeland Security Secretary, says he is 98 percent certain there was no cyberattack
1. Microsoft, November 12
Outlook email, Teams video meetings and the Copilot AI assistant went dark for about 24 hours. Microsoft’s preliminary report blames a defect in a Windows fix, a software repair installed in July. It sat unnoticed for four months. More than 80 percent of the servers that let customers into Microsoft 365, the company’s office software, stopped responding.
2. The Federal Aviation Administration, November 13
L3Harris, a defense contractor working for the FAA, which runs American air traffic control, was replacing old copper lines with fiber-optic cable at a radio site in El Dorado, Arkansas. Sean Duffy, the Transportation Secretary, called the job “pretty straightforward work.” Newly installed routers, which direct data around a network, then flooded the air traffic system with 1,000 connection attempts every four to five seconds. The FAA held every departure in the country for more than four hours, and the tracking service FlightAware counted more than 9,000 cancellations. The routers’ maker, a unit of Hewlett Packard Enterprise, says they “did not fail.” On its account they were working properly when the airspace closed.
3. Workday, November 13
Workday sells payroll and human-resources software to about 11,500 organizations. That evening many of their employees were locked out. Workday’s notice to customers said that during a test of the disaster-recovery site, the backup kept for emergencies, services there had “unexpectedly connected” to the live databases. The test of the disaster plan caused the disaster.
4. JPMorgan Chase, November 16
America’s largest bank blamed “a software bug in an on-premise hardware system,” meaning a machine in its own building. Payments slowed online, in branches and on Zelle, the payment app that big American banks own jointly. Customers of other banks were caught whenever their money passed through Chase.
5. United Airlines, November 16
For about 90 minutes United could not give pilots the final weight of their aircraft, a number they need before takeoff. A pilot in Houston asked the control tower for permission to stay at the gate. United called it a technology issue.
6. The National Security Agency, November 17
CNN, citing six people, said the agency’s staff had lost NSA Net, the network they use to share classified information. No cause has been given. The NSA is the agency Washington pays to break into other countries’ networks. Its staff were told to arrive for work at staggered times.
7. Apple, November 7
Multiple Apple services – the App Store, Apple Pay, Apple Music, AppleCare – were hit with outages this morning. Users also reported being logged out of their iCloud accounts and unable to sign back in again.
Pretty much every company and government agency with outages says an “internal update” explains why their systems went down. That’s a bit like a meteor striking your house six times. Asked about the outages on a visit to Manila, President Trump said “it’s life.” He added that “when you’re big and powerful, and you have all the money,” such things happen. Meanwhile, the FBI has issued an advisory stating that “cybercriminals and state-aligned hackers” are using AI-powered software to attack businesses and software across the globe. However, Markwayne Mullin, the Homeland Security Secretary, says he is 98 percent certain there was no cyberattack on the NSA. If he is right, no adversary spent a dollar on it. Microsoft’s final incident report, a primary source for the next Gibbon, is due on November 20.
Comments