Axi · Сквозной — фон контента (skin) · 16 кат.Axi · Сквозной — фон контента (skin) · 16 кат.

How to Distinguish a Cyberattack from a Technical Failure After a Series of Incidents in the US

• Evgenia Sliv (edited: )
How to Distinguish a Cyberattack from a Technical Failure After a Series of Incidents in the US

In the United States, a series of major technological failures occurred over four working days, affecting cloud services, banking operations, aviation infrastructure, and government systems. The unusual sequence of incidents sparked speculation about a possible coordinated cyberattack, but no confirmation of such a version has emerged. Cybersecurity experts explained what signs can help determine the likely cause of the outage and why several simultaneous failures are not necessarily related.

Major IT failures in the US

On November 12-13, disruptions in Microsoft 365 affected Exchange Online, Outlook, and several other company services. On November 13, a technical malfunction in the telecommunications infrastructure of the Federal Aviation Administration (FAA) led to a temporary halt of flights nationwide. The system stabilized that evening, after which air traffic began to gradually recover.

On November 16, a software error in JPMorgan Chase's infrastructure caused delays in processing banking transactions and affected interactions with other financial organizations. On the same day, United Airlines faced a failure in its own systems, causing flight departures to be delayed. The next day, issues also arose in the internal network of the National Security Agency (NSA), used for handling classified information.

Despite the timing of these events, experts found no evidence that they resulted from a single attack. Moreover, explanations published by Microsoft and the FAA point to technical problems in the infrastructure, and JPMorgan Chase separately reported a software error. This shows why initial assumptions about hacking need to be verified as new data becomes available.

Why a large-scale failure doesn't necessarily mean a cyberattack

According to Doug Madory, head of internet analytics at Infoblox, the vast majority of network failures he tracks are not related to malicious actors. The expert notes that technical malfunctions occur significantly more often than deliberate attacks, so investigations should start by checking common causes. These can include unsuccessful updates, configuration changes, cable damage, power outages, or equipment overload.

Cloudflare CEO Matthew Prince also points to the complexity of modern information systems. In his assessment, even a small malfunction of one component can trigger a chain reaction and affect many dependent services. Therefore, the scale of the consequences alone does not allow determining whether a breach occurred.

A telling example was the November Microsoft 365 failure, which the company linked to a software defect and load distribution characteristics between servers. Similar logic applies to cloud platforms, payment systems, and transportation infrastructure, where individual components serve a large number of users. An error in one such link can appear as several independent failures.

Where to check official information about failures

The first source of information should be the announcements from the organization that owns the problematic service. Major tech companies publish notices about service disruptions on official websites, support pages, and verified social media accounts. These messages help determine which functions are unavailable, when the incident began, and what measures are being taken for recovery.

Additional information is provided by special service status pages – status dashboards. Such tools are available from Microsoft, Amazon Web Services, Google Cloud and other large platforms, and during serious incidents, companies regularly update information on the recovery progress. However, the absence of a message in the first few minutes does not mean the service is operating normally: the infrastructure owner may need time to confirm the scale of the problem.

It is also important to consider the interconnection of systems. For example, a disruption in interbank transaction processing can affect several financial organizations at once, even if their own infrastructure continues to operate. In such cases, reports from different users do not necessarily indicate several independent failures or a large-scale attack.

How network monitoring data helps determine the cause

If official information is insufficient, experts turn to independent internet infrastructure monitoring tools. Services like Cloudflare Radar and Internet Outage Detection and Analysis (IODA) allow the study of changes in network availability, outage duration, and the geography of disruptions. This data helps determine whether the problem is limited to one operator or affects several interconnected networks.

Georgia Tech researcher Amanda Man notes that analysis requires correlating the start and end times of the outage, affected networks, and available incident reports. For example, a local malfunction of a backbone channel can lead to an entire region being disconnected, while a faulty software update can simultaneously disrupt the operation of a large number of servers. However, even a detailed picture of network outages does not always allow determining the cause without information from the infrastructure owner.

Therefore, monitoring data should be considered as additional confirmation of the scale and nature of the problem. They help filter out unconfirmed reports and find a common point of failure, but do not replace a technical investigation. Final conclusions depend on event logs, equipment status, security system check results, and other internal data.

What signs may indicate hacker actions

In some cases, attackers independently claim responsibility for an attack by posting messages on their resources or social media. This is especially common with ransomware, where criminals try to force the affected organization to pay for restoring access to systems or preventing the publication of stolen data. However, such statements may be false or exaggerated and require independent verification.

More reliable indicators may include the detection of malware, unauthorized access, attempts to encrypt data, or confirmed actions of attackers within the network. Such information can be published by affected organizations, specialized researchers, and government agencies, including the Cybersecurity and Infrastructure Security Agency (CISA) in the U.S. However, the absence of a public statement from hackers does not prove that an attack did not occur.

Even the duration of downtime provides only indirect information. Some technical failures are resolved within a few hours, while recovery from a serious attack involving data encryption may take significantly longer. But a complex software error can also lead to prolonged downtime, so this indicator alone does not reliably determine the cause.

Why It's Important to Wait for Investigation Results

Determining the causes of a major IT failure can take from several hours to several weeks, especially if the problem affected complex infrastructure. Initial explanations are sometimes refined after analyzing logs, checking updates, and restoring service operations. Until such data is available, experts recommend distinguishing confirmed facts from assumptions about a possible breach.

A series of November incidents in the U.S. demonstrated how heavily everyday services depend on digital infrastructure and interconnected technological systems. Simultaneous disruptions at several major organizations can have different causes, even if they outwardly appear as a single event. For a reliable assessment, it is necessary to compare official statements, technical data, and investigation results, without considering every large-scale failure as proof of a cyberattack.

This material is prepared solely for informational purposes and does not constitute financial advice or a recommendation.

Comments

Checking authorization...
Loading comments...