July 20th, 2024

Microsoft says 8.5M Windows devices were affected by CrowdStrike outage

Microsoft reported that a CrowdStrike outage impacted 8.5 million Windows devices globally, causing disruptions in banking, retail, and transportation. Collaboration with tech giants is ongoing to address cybersecurity risks efficiently.

Read original articleLink Icon
Microsoft says 8.5M Windows devices were affected by CrowdStrike outage

Microsoft reported that around 8.5 million Windows devices, less than 1% of global Windows machines, were impacted by a recent CrowdStrike outage caused by a faulty update. The incident led to widespread disruptions affecting various sectors like banking, retail, and transportation, with airlines worldwide halting flight operations. While the percentage of affected devices was small, the economic and societal impacts were significant due to the critical services relying on CrowdStrike. Microsoft's vice president of enterprise and OS security, David Weston, mentioned that collaboration with CrowdStrike, Amazon Web Services, and Google Cloud Platform is ongoing to address the issue efficiently. Despite the relatively low number of affected devices, the outage highlighted the potential risks associated with cybersecurity incidents and the importance of swift and coordinated responses to mitigate disruptions.

Related

Microsoft/Crowdstrike outage ground planes, banks and the London Stock Exchange

Microsoft/Crowdstrike outage ground planes, banks and the London Stock Exchange

A cybersecurity program update failure caused global disruptions affecting businesses and services like United Airlines, McDonald’s, and the London Stock Exchange. Microsoft and CrowdStrike faced issues, but the problem was resolved without a cyberattack. CrowdStrike's shares dropped 20%, and Microsoft's fell 2.9%. The incident, involving Windows and security software, is one of the largest IT outages, surpassing past disruptions.

Global IT Collapse Puts Cyber Firm CrowdStrike in Spotlight

Global IT Collapse Puts Cyber Firm CrowdStrike in Spotlight

A faulty patch from CrowdStrike Holdings Inc. caused a global IT collapse, impacting various sectors. CrowdStrike's shares dropped by 15%, losing $8 billion. The incident emphasized the importance of endpoint protection software.

Microsoft has serious questions to answer after the biggest IT outage in history

Microsoft has serious questions to answer after the biggest IT outage in history

The largest IT outage in history stemmed from a faulty software update by CrowdStrike, impacting 70% of Windows computers globally. Mac and Linux systems remained unaffected. Concerns arise over responsibility and prevention measures.

2024 CrowdStrike incident: The largest IT outage in history

2024 CrowdStrike incident: The largest IT outage in history

A faulty update by CrowdStrike led to a global computer outage affecting airlines, banks, hospitals, and government services. Over 3,200 flights were canceled, emphasizing the need for strong cybersecurity.

Global CrowdStrike Outage Proves How Fragile IT Systems Have Become

Global CrowdStrike Outage Proves How Fragile IT Systems Have Become

A global software outage stemming from a faulty update by cybersecurity firm CrowdStrike led to widespread disruptions. The incident underscored the vulnerability of modern IT systems and the need for thorough testing.

Link Icon 14 comments
By @dgrin91 - 3 months
That sounds low... Really low. E.g. NYC has ~350k employees and I know they got hit hard. Not all of them have windows machines, but let's say 100k do. I know they basically all have falcon installed. That's 100k in just one org, not even counting their windows servers. How many Fortune 500s are mainly Windows?

Edit: I did some back of napkin math. ~30 million work for a fortune 500. Let's say 2/3rds of those have a Windows desktop provided by employer, so ~20M. I think I read crowdstrike has about ~25% market share, so that's 5 mil just in fortune 500. No way it's just 8.5M

By @belter - 3 months
Microsoft is just jealous, it took the focus from their large Azure outage, also on Friday: "Major Microsoft 365 outage caused by Azure configuration change" - https://www.bleepingcomputer.com/news/microsoft/major-micros...

To compensate and keep the focus on them, as masters of all outages...They will take at least until Tuesday, (according to their own info...) to fix the current ongoing issue with Teams scheduling: https://portal.office.com/servicestatus

By @averageRoyalty - 3 months
Another article blaming the upstream vendor and not bothering to put any onus on the horrible security practices of companies allowing auto updating of executable code in production on critical systems.

This is unacceptable practice. I understand non tech media not getting it, but this lack of awareness from tech news is sad.

By @someonehere - 3 months
What saved my company from this is the recommended policy I’ve had the last three companies I’ve implemented this in. N -1.

The first time I ever rolled out Falcon, the sales engineer said, “if you want to be on the latest when it releases, choose this policy. Generally customers like to be one release (N -1) behind. This is the safest option in my experience. We rarely have issues but this is the way to prevent issues if we do ship something bad.”

I’ve been telling other admins this is the safest option moving forward. I don’t see a need for my org to run bleeding edge releases of newer products. This also applies to OS updates unless it’s a zero day. Major OS releases I wait for the first .1 update to release. Currently doing this with Ubuntu Desktop 24 LTS as it shipped with missing features from 22 and a broken autosetup functionality. August is the first update to 24 LTS and we’ll test and determine if the bugs have been squashed.

I can’t think of any way to always be on the latest upgrade of anything critical. All of these companies were on the bleeding edge release of CrowdStrike and it brought a lot down globally.

By @Gys - 3 months
I wonder how they came to this number? And how reliable is it? It is very quick and relatively a very small number. Very convenient for damage management.
By @xyst - 3 months
This outage (fuck up) impacted critical workflows. Lawyers should be foaming at the mouth to get a class action lawsuit going if criminal penalties are not applicable.

Hospitals - physicians/doctors/nurses lost access to critical equipment. Patients may have suffered degraded care as well. Reports of this outage impacting active surgeries. Patients forced to reschedule appointments around ClownStrike

Airlines - many flights grounded. Delays, delays, delays. Wasted fuel, time. Loss of revenue due to rescheduled flights, refunding customers. Local airports flooded with grounded flights, increased personnel to deal with it. FAA stressed.

Banks - many people lost access to money. Frustration for people trying to get access to pay bills, or get paid themselves.

By @surfingdino - 3 months
Monocultures die fast and without survivors.
By @LadyCailin - 3 months
I vote we stop putting George Kurtz in charge of things.
By @dmd - 3 months
So my org (a random medium-sized healthcare system), with ~100k seats, was more than 1% of the devices? I don't buy it.
By @steveBK123 - 3 months
Off by an order of magnitude for sure.

I've heard of 250k employee companies where people got a snow day off this.

By @m3kw9 - 3 months
Maybe I would think most non businesses will not need falcon sensor, and more critical systems will be the ones actually using it. So their “low” numbers are actually high if you only look at businesses or critical systems
By @Quaranqi - 3 months
That is 0001.5-M out of 1400.0-M windows devices in all.

That is about -.1% of all the MS machines.

As a linux user, I dont understand the big deal, the effects of this.