Continuing from the previous article published on Friday, July 19th, 2024.
Microsoft estimates that the CrowdStrike outage that occurred on Friday has caused 8.3 million computers globally to be disabled.
Crowdstrike, a leading global cybersecurity company, issued a software update to its clientele. Regrettably, this action resulted in significant disruption, leading to flight cancellations, grounded aircraft, broadcast interruptions, and the denial of essential services such as healthcare and banking to customers.
Microsoft has estimated that approximately 1% of Windows users have encountered the phenomenon known as the ‘Blue Screen of Death’. In an official statement, the company projected that this error has impacted 1 percent of Windows-based computers globally.
It is the first time that a specific number has been attributed to the incident, which continues to cause global disruptions.
The turmoil ensued after CrowdStrike distributed a flawed software update to its customers, resulting in widespread computer system failures.
There are now warnings that malicious actors may seek to exploit the confusion by presenting deceptive offers for purported “fixes” to companies and consumers. You can read more about it here.
This incident is consider to be the largest-cyber event eclisping all previous hacks and outages, according to Microsoft.
The National Co-ordination Mechanism, comprised of government agencies and representatives from affected sectors, is convening to deliberate on the subsequent measures in Australia’s “recovery stage” following the outage.
Jenny McAllister, Assistant Energy Minister, expressed that collaborative efforts persist between the government and the impacted sectors to ensure their resumption of operations.
“We are presently in a phase of recovery. More work remains to address any residual issues stemming from this outage,” she conveyed to Sky News on Sunday.
“In due course, there will be an opportunity to contemplate the events of the past few days and ascertain whether they have exposed vulnerabilities that we can mitigate.”
The majority of companies affected by the outage had restored their operations by Saturday.
For many businesses and organisations around the world, it is anticipated that there will be no conpensation but rather it is a learning experience for everyone involved.
Warning from CrowdStrike’s CEO about ‘malicious actors’
Government cybersecurity agencies worldwide, along with CrowdStrike CEO George Kurtz, are cautioning businesses and individuals about new phishing scams. These schemes involve malicious actors posing as CrowdStrike employees or other tech specialists, offering assistance to those affected by the outage.
Mr. Kurtz stated, “We know that adversaries and bad actors will try to exploit events like this. I encourage everyone to remain vigilant and ensure that you’re engaging with official CrowdStrike representatives.”
The UK Cyber Security Centre reported an increase in phishing attempts related to this event. CrowdStrike collaborated with Microsoft’s Azure infrastructure to expedite a solution, with Microsoft working alongside Amazon Web Services and Google Cloud Platform to share information about the industry-wide impact.
The air travel industry is currently recovering from the outage, which led to numerous flight cancellations and left passengers stranded or dealing with extensive delays. Security experts highlighted that an update of CrowdStrike’s widely used cybersecurity software apparently did not undergo sufficient quality checks before deployment.
The latest version of the Falcon sensor software aimed to enhance clients’ system security against hacking by updating threats it defends against. Steve Cobb, Chief Security Officer at Security Scorecard, suggested, “What it looks like is, potentially, the vetting or the sandboxing they do when they look at code, maybe somehow this file was not included in that or slipped through.”
CrowdStrike provided information to rectify affected systems, although experts indicated that restoring them would be time-consuming, as it necessitated manual removal of the flawed code.


