NEW: Practise with AI → Try it free

How to Distinguish Between Cyberattacks and Genuine IT Outages

Exercise 1

Vocabulary

Repeat each word, its meaning and the example sentence out loud.

  • cascading failure

    noun phrase

    /kæˈskeɪdɪŋ ˈfeɪljər/a situation where problems in one system trigger a chain reaction of failures across interconnected systems that depend on it

    When AWS experienced outages, the cascading failure disrupted hundreds of dependent services across the platform.

  • to muddy the waters

    phrasal verb

    /tə ˈmʌdi ðə ˈwɔːtərz/to make a situation more confusing or unclear by introducing additional complications or contradictory information

    False reports of additional outages muddied the waters, making it harder for teams to identify the actual point of failure.

  • default position

    noun phrase

    /dɪˈfɔːlt pəˈzɪʃən/the assumption or stance you take initially, before considering alternatives or evidence to the contrary

    Our default position when investigating incidents is that the cause is accidental unless we find proof of deliberate sabotage.

  • foul play

    noun phrase

    /faʊl ˈpleɪ/dishonest, illegal, or malicious behaviour; in security contexts, deliberate sabotage or hacking

    Investigators found no evidence of foul play in the outage, confirming it was simply a configuration error.

  • to trace back

    phrasal verb

    /tə ˈtreɪs ˈbæk/to follow something back to its origin or root cause by working backwards through the evidence

    Network analysts traced back the widespread outages to a single misconfigured update at a major cloud provider.

Exercise 2

Article

Read the article aloud on your own, or listen to it first.

AI generated audio00:00 / 00:00

How to Distinguish Between Cyberattacks and Genuine IT Outages

Tap any word to see what it means.

Recent clusters of high-profile technological failures have fuelled speculation about coordinated cyberattacks destabilising American infrastructure. Within four consecutive business days, organisations confronted a mass Microsoft Exchange outage disrupting IT services across thousands of companies, an FAA systems glitch grounding aircraft nationwide, a JPMorgan Chase software malfunction causing financial sector disruption, a United Airlines technical failure delaying flights, and an NSA classified network experiencing downtime.

The improbable timing prompted widespread anxiety that these incidents might represent a deliberate campaign rather than unfortunate coincidence.

Yet cybersecurity professionals emphasise there remains no evidence linking these failures or attributing them to malicious actors. The challenge for security analysts lies in distinguishing genuine cyberattacks from accidental outages—a distinction that proves increasingly difficult when cascading failures affect multiple services simultaneously and media coverage amplifies speculation.

The fundamental principle guiding incident investigation, according to network security experts, is statistical rather than dramatic. Matthew Prince, CEO of Cloudflare, notes that "most of what we're seeing is the standard background noise," acknowledging that complex systems routinely fail under their own weight.

Cybersecurity researcher Doug Madory, who monitors approximately a dozen network outages daily, emphasises that only around one in a thousand stems from malicious activity. His recommendation is straightforward: "One's default position should be that it isn't a cyberattack unless there is some concrete evidence to the contrary." This baseline assumption redirects investigative focus toward more likely culprits—misconfigured updates, configuration changes, cable cuts, or power failures.

Cascading failures frequently muddy the waters, particularly when foundational services like major cloud providers experience outages. Amazon Web Services disruption, for instance, automatically cascades to dependent customers.

Similarly, multiple services may appear compromised whilst actually functioning normally, merely experiencing problems when interacting with a failed entity. The recent banking sector disruptions exemplified this scenario: whilst multiple institutions appeared to malfunction, the root cause involved interconnected transactions funnelling through JPMorgan Chase.

Identifying the precise point of failure requires consulting official sources. Verified social media accounts, company newsrooms, and status dashboard pages provide authoritative information about service availability.

Major platforms—AWS, Google Cloud Platform, Microsoft Azure, and others—maintain dedicated status pages offering real-time transparency during incidents.

For widespread Internet-wide disruptions, broad-scale monitoring tools prove invaluable. Organisations like Georgia Tech's IODA service, alongside Cloudflare Radar and Watch the Net, analyse network data to determine disruption scope, location, and timing.

This granular analysis helps researchers distinguish between buggy updates affecting isolated networks, infrastructure damage like fibre optic cable cuts, and rarer instances of genuine cyberattacks or government-imposed Internet restrictions.

The convergence of multiple outages need not indicate conspiracy. Rather, it often reflects the fragile interdependencies within modern digital infrastructure and our heightened sensitivity to technological disruption.

Discuss this story out loud with our AI speaking coach.

It asks one question at a time, at your level, and gives you feedback at the end.

Start the discussion Retell it

3,000+ learners

Also works inChatGPTandClaude

Exercise 3

Discussion

Have a discussion based on the following questions.

  1. 1.In your own organisation, how do you distinguish between accidental outages and potential security incidents, and what evidence typically triggers an escalation to your security team?
  2. 2.Given that cascading failures can create the illusion of a coordinated attack, what communication challenges does your team face when explaining outages to non-technical stakeholders who suspect foul play?
  3. 3.How does your organisation utilise status pages and official communications channels during incidents, and do you find that this transparency reduces speculation about cyberattacks?
  4. 4.What processes does your company have in place to verify information about outages without relying on social media speculation or unconfirmed reports?
  5. 5.If you discovered that a cluster of outages affecting your industry was actually accidental rather than malicious, how might that change your incident response procedures or infrastructure investment priorities?

Exercise 4

Further discussion

Have a discussion based on the following questions.

  1. 1.How has the increasing interconnectedness of cloud infrastructure changed the nature of outages, and does this make distinguishing between accidents and cyberattacks easier or more difficult?
  2. 2.What systemic improvements to digital infrastructure transparency might help reduce public anxiety during outage clusters, and who should bear responsibility for implementing these improvements?
  3. 3.As artificial intelligence becomes more prevalent in both infrastructure management and cyberattacks, how will cybersecurity analysts adapt their investigative approaches to identify whether failures stem from autonomous systems or deliberate hacking?
  4. 4.Should governments and critical infrastructure operators prepare differently for the possibility of coordinated outages, even if statistical evidence suggests such events remain rare?
  5. 5.How can technology companies balance the operational benefits of interconnected, interdependent systems against the cascading failure risks that such architecture inherently creates?

Discuss this story out loud with our AI speaking coach.

It asks one question at a time, at your level, and gives you feedback at the end.

Start the discussion Retell it

3,000+ learners

Also works inChatGPTandClaude

Source

This lesson is our own retelling, for English learners, of a story from Ars Technica.

Share this: LinkedInXWhatsApp Email

Related stories

All lessons: learn business English with tech news

For bots & AI agents

When multiple high-profile digital services fail in quick succession, observers often suspect coordinated cyberattacks. However, cybersecurity experts emphasise that the overwhelming majority of outages result from accidents—misconfigured systems, failed updates, or infrastructure errors—rather than malicious interference.

Lesson:
How to Distinguish Between Cyberattacks and Genuine IT Outages
CEFR level:
C1
Topic:
Security & Privacy
Published:
2026-11-20
Based on:
Ars Technica (https://arstechnica.com/security/2026/11/how-to-tell-a-cyberattack-from-a-plain-old-outage/)
Key words:
cascading failure, to muddy the waters, default position, foul play, to trace back
Discussion questions:
5

Related (.md): Signal stops users taking screenshots to protect privacy from AISignal Blocks AI Assistants from Reading Your MessagesMajor US Systems Go Down: Cyber Attack or Bad Luck?Researcher Exposes Massive Data Leaks Across AI Supply Chain Using Digital Tripwires

Machine-readable: This page (.md)Security & Privacy news lessons (.md)MCP serverllms.txt

MCP call: {"method":"tools/call","params":{"name":"get_daily_news_lesson","arguments":{"slug":"cyberattack-vs-outage-how-to-tell-the-difference"}}}

Cite as: “How to Distinguish Between Cyberattacks and Genuine IT Outages, Speak Tech English (https://app.speaktechenglish.com/tech-news-lessons/cyberattack-vs-outage-how-to-tell-the-difference)”