Urgent.News

What's breaking now, across thousands of outlets.

Tech

How to Tell If It’s a Cyberattack or Just an Outage

Email, flights, banks; network failures are piling up. Here’s how WIRED investigates if they’re the result of hacker mayhem. (Hint: usually not.)

How to Tell If It’s a Cyberattack or Just an Outage

Over the past week, a series of major technology failures left many Americans questioning whether a cyberwar had struck the United States. Across four consecutive business days, Microsoft Exchange services went down, causing IT disruptions for thousands of companies; the Federal Aviation Administration experienced technical issues that grounded airplanes nationwide; JPMorgan Chase faced software-related problems that caused further disruption; United Airlines encountered flight delays due to a system glitch; and the NSA's classified network went offline, leaving agency staff waiting to return to their office in Fort Meade.

Amidst a backdrop of US tensions with Iran and growing concerns about AI-enabled hacking, these events seemed increasingly likely to be related. However, there is currently no evidence suggesting a connection between these isolated technological failures or that they were caused by hackers. It is the responsibility of cybersecurity analysts and journalists to investigate and determine, beyond mere speculation, if the latest tech outage was an accident or a cyberattack.

The likelihood is that most digital breakdowns are due to negligence or mistakes by IT administrators, as complex systems are prone to breaking down. To discern the cause of an IT service outage, it is essential to begin by assuming the issue is a result of negligence rather than a cyberattack. Only around one in a thousand network outages turn out to be caused by hackers, according to cybersecurity researcher Doug Madory.

This presumption of innocence should hold unless there is concrete evidence to the contrary. Moreover, many significant outages that resemble cyberattacks are actually self-inflicted due to factors such as bad updates, configuration changes, cable cuts, or power failures. Common culprits include problems within foundational services like cloud providers; multiple services experiencing issues that are actually functional individually but interact poorly when combining; and false reports created by false (typically accidental or anecdotal) claims of additional outages.

To determine the cause of a tech outage, start by checking the official status updates from the organization involved. For large tech companies, look for statements on their verified social media accounts or press release sections on their websites. In addition, trusted sources of network data, such as status dashboard pages, can provide transparency into the functioning of various components of a service.

Companies like AWS, Google Cloud Platform, and Microsoft Azure offer these pages to keep users informed about system restoration efforts. By following these guidelines, one can better distinguish between a cyberattack and an accidental outage, helping to calm the nerves of a country gripped by fear of increasingly frequent tech catastrophes.

Written by urgent.news from Wired's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at wired.com →

More in Tech

Reading car fault codes from a web page: Web Serial and Web Bluetooth vs. cheap ELM327 clones

A cheap ELM327 adapter, Chrome, and two browser APIs are enough to read engine fault codes without installing anything. The protocol part is small; most of the code deals with how real adapters and…

  • Web Serial and Web Bluetooth APIs enable reading car fault codes via web page.
  • Chrome and Edge support these APIs for USB or BLE adapter access.
  • OBD-II layer reads various codes like stored, pending, freeze frame data, sensors, VIN.

More from Tuesday 17 November →