If their incompetence can stop pacemaker monitoring and what the f else, then god help us when an unfriendly regime decides to eff with us or them !! (fi)
If the windoze OS wasn’t such a steaming pile of excrement, maybe crowdstrike would not have caused this problem.
Or maybe if Crowdstrike didn’t have such a major QA problem the bad patch would have been caught. This isn’t a Microsoft issue this is a Crowdstrike issue.
1 Like
It also shows a major vulnerability to national security. Industry, banking institutions, airlines all shut down. Its a pretty bad situation with far-reaching implications. Imagine if someone causes that and then knocks out telecommunications and power with known vulnerabilities that exist. It would be almost as bad as an EMP.
This is exactly why converting to electronic currency is a foolhardy idea.
What happened with Crowdstrike was bad, really bad but at the same time this also highlights the bad practices of companies across the board.
Roughly 8.5 million systems were impacted worldwide, around 1% of all Windows systems globally. So why weren’t all the Microsoft systems affected? The answer can range from systems too old, systems where offline, systems didn’t have updates automatically running or there were processes in place that just didn’t throw a new untested (internally) update into production. So while Crowdstrike deserves the beating they are getting for such a stupid error. The banks, airlines, health care providers, etc that just let this update freely be done on all their systems with no testing or validation should also take a beating for such poor procedures and practices.
At the end of the day, Crowdstrike releases a very badly broken patch and failed to catch it but at the same time, all these enterprise companies seem to have Automatically Download and Install Updates enabled on their production systems.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.