Recovering from the global tech outage could be a long, arduous process
The company that caused a massive worldwide computer outage said a flawed update had been rolled back, but that doesnât necessarily help the thousands of businesses affected by the glitch.
Video above: How to protect yourself after global outage
The CrowdStrike software issue at the heart of the outage runs at such a deep level in affected computers and systems that getting them up and running just to be fixed will be, in many cases, an enormous challenge.
Thatâs compounded by the fact that many of the servers that may contain information needed to get these systems working again are themselves caught in a cycle of crashing and rebooting.
"I donât think it's too early to call it: this will be the largest IT outage in history," said security expert Troy Hunt .
The CrowdStrike software at fault operates at a computerâs kernel level, a much deeper level than what more ordinary applications such as browsers or video games do. This portion of a device has much greater visibility and control over a computer and its components, making it critical for the operation of all other systems and far more sensitive.
Running at the kernel level means CrowdStrike's software can do more to detect cyberattacks, but it also means the current bug is causing Windows computers to crash to a before users can take any actions to correct it.
The issue appears to be recoverable, , but in many cases it requires painstaking work: Each affected device must be accessed by an administrator and manually rebooted into safe mode. Then, the offending CrowdStrike file must be deleted by hand.
For businesses with hundreds or thousands of laptops, desktops and servers running CrowdStrikeâs security software, an individual human may have to perform that process over and over and over again.
"You canât automate that," said Kevin Beaumont, a security researcher and former Microsoft threat analyst, in . "So this is going to be incredibly painful for CrowdStrike customers."
Video above: CrowdStrike CEO says company has 'deployed a fix' to tech issue
It gets worse.
Organizations that take security seriously will have likely encrypted their computersâ hard drives, making it even more challenging to access the file that needs to be deleted.
For those organizations, "you need to manually decrypt the disk with a BitLocker Recovery Key, which is probably â for most companies â stored digitally on one of the servers that is currently booting over and over," said Ira Bailey, a security researcher, .
Every affected computer that is BitLocker-encrypted will need to be unlocked with a recovery key before organizations can begin the process of deleting the bad CrowdStrike file and restoring normal operation, said the cybersecurity expert who goes by the pseudonymous handle SwiftOnSecurity in .
Recovery will be enormously expensive for Fortune 500 companies with large teams of IT staff and likely even more challenging for smaller firms, Kenn White, an independent security researcher who specializes in network security, told CNN.
"If you donât have physical staff that can actually touch it, this is going to take many, many days for much of corporate America to recover from," White said. "It's just a ton of labor-intensive manual work."
"Itâs a fairly complicated procedure for non-technical people," White added, "and even a lot of skilled IT professionals will find it difficult to do this at the scale thatâs going to be required given the number of machines that are affected."
How did the CrowdStrike bug lead to such widespread effects?
Because CrowdStrikeâs security software is running on countless individual computers all around the globe, the update that got pushed to those devices caused them all to shut down, virtually simultaneously.
And in todayâs networked economy, an outage in one part of a supply chain can cause domino effects up and down the line. When multiple parts of a supply chain go down, it touches off a cascade of problems.
Imagine a person trying to buy a coffee, said Andrew Peck, a cybersecurity expert at Loughborough University in the UK. What may seem like a simple transaction relies on multiple computers working in tandem, from the coffee shopâs point of sale to the payment processorâs own back-end systems.
Video above: Starbucks, hotels, businesses affected by CrowdStrike outage
"There are a lot of computers in this chain, and usually the larger the business, the larger the chain," Peck said. "If any one of the computers are down in the chain, the transaction will not complete."
Now scale that up to something like the massive aviation industry, the critical financial services sector or the life-or-death operations of a health care provider, and the scope of the disaster becomes starkly clear.
What is Microsoftâs role in all this?
A separate issue earlier, on Thursday, did lead to significant impacts on many of Microsoftâs own cloud customers, but it was resolved overnight and was unrelated to the CrowdStrike issue, multiple cybersecurity experts said.
The CrowdStrike bug may have initially been conflated with the Microsoft issue because CrowdStrikeâs error affected only Windows machines.
âBoth are Microsoft-related, but Microsoft had nothing to do with the second incident,â White told CNN.
That appears to be supported by Microsoftâs own status account on X, which on Thursday announced affecting "Microsoft 365 apps and services" and Friday addressing the CrowdStrike outage. The two issues are being tracked using different reference numbers.
As of Friday morning, Microsoft said the issue with Microsoft 365 had been resolved and that . Microsoft didnât immediately respond to a request for comment.
Since the update to CrowdStrikeâs software was delivered by the companyâs own systems, it appears unlikely that Microsoft bears direct responsibility for Fridayâs outages, said Beaumont, who said he reviewed a copy of CrowdStrikeâs flawed update.
The problem with CrowdStrikeâs update was that it wasnât formatted correctly âand causes Windows to crash every time,â Beaumont .
CNNâs Olesya Dmitracova contributed reporting.