CrowdStrike's Disaster Is Bigger Than Windows

preview_player
Показать описание
A few days back the whole CrowdStrike ordeal went down and whilst it was terrible for Windows it turns out that CrowdStrike has a long history of being an absolute disaster of a company

==========Support The Channel==========

==========Resources==========

=========Video Platforms==========

==========Social Media==========

==========Credits==========
🎨 Channel Art:
Profile Picture:

#CrowdStrike #Linux #Windows #Antivirus

🎵 Ending music
Track: Debris & Jonth - Game Time [NCS Release]
Music provided by NoCopyrightSounds.

DISCLOSURE: Wherever possible I use referral links, which means if you click one of the links in this video or description and make a purchase I may receive a small commission or other compensation.
Рекомендации по теме
Комментарии
Автор

To be fair crowdstrike are just doing a more efficient version of the Windows Insider program. Instead of pushing tests out for 6 months and ignoring the results they are just going straight to production.

wilfridtaylor
Автор

In my opinion, seeing as this is not the first time, CrowdStrike should be officially declared to be malware.

tmfx
Автор

Wow, I thought it was just a one-off mistake, but they are truly terrible. How can a company sell a product to 298 of fortune 500 and not test updates after they repeatedly cause large scale system outages?!

szaszm_
Автор

If there's a lawsuit, I'll be following it with some popcorn in hand.

jean-michelgilbert
Автор

Look up recent Crowdstrike layoffs and it will become clearer how "testing in production" is the level of QA one would expect

MrJustwatchandlisten
Автор

Everybody has a test environment, some also have a separate production environment.

Dennis-vhtz
Автор

It cannot be understated enough. If they tested it or reviewed it just ONCE. They would of known right away. Massive L

Lanewreck
Автор

Of all the things Windows does that I hate Patch Tuesday being a Tuesday is not one of them.

rockdemn
Автор

"Does CrowdStrike connect to the home WiFi?" -Congress

aqua-bery
Автор

If our product owner asks us to build a hotfix on a Friday (I'm a release manager), my default response is ALWAYS: "Sure, I can do that. But I'll only deploy it on staging for testing purposes. Nothing goes to production before Monday morning at the earliest." I flat out refuse to deploy anything to production on a Friday. And if someone insists, I'll tell them to wait for me to log off for the weekend. Deployments on a Friday are just a no go!

laertes
Автор

Outsourcing your own security and not investing in proper testing practices is two of big tech's greatest mistakes, and now we are seeing the consequences.

Автор

Deploys on Friday, just asks for disaster

romanstingler
Автор

Kaspersky gets booted for speculation.

CrowdStrike takes out half the planet and no one bats an eye.

StephenMcGregor
Автор

ah yes, the US congress hearing. Asking truly mind opening questions such as "does tiktok use the home wifi" during the tiktok ban hearing 🤣

yumekarisu
Автор

Crowdstrike published a postmortem on this error. TLDR - this spring they created a template for channel update files, and put it through complete testing (including staging deployment of said file), which it passed successfully. Then in July they made 2 new instances of channel update file, based on his template. Due to a bug in their testing software, it missed the fact that one of said had problematic code in it. And then because all the previous channel update files, based on this template, passed all their tests successfully, they decided that their automatic test (the one with a bug in it) was enough and deployed this file straight into production. Truly some 5 head move right there.

IdleCommentator
Автор

Crowdstrike should not only be sued, but potentially arrested. This is inexcusable amounts of oversight.

authurstretchygreenthing
Автор

if they only tested it on one machine... just one machine

davidconner-shover
Автор

MS were asked why they didn't do anything to prevent this, they replied that the only thing they could have done to prevent this was blocking kernel level access, and that they had tried to do so years ago but that this was prohibited by the EU (in order to protect MS competitors like Crowd Strike). Considering the circumstances I think MS had the right to be a bit salty in response to (unwarranted) media and government criticism (especially from the EU!), so the only thing arguably wrong with the Tom's Hardware article (and many others like it) is the click-bait headline.

Dennis-vhtz
Автор

Crowdstrike: the Pioneers of Lemonware (software that is so poorly written it bricks your entire rig)

timothyt.
Автор

From what I understand, CrowdStrike made a kernel-level interpreter/JIT compiler for Windows in the form of a "device driver". The updates that they push are apparently some kind of p-code files that the driver then runs. This allows them to push updates without going through the whole WHQL process for each update but errr.. it also means you have a kernel-level p-code interpreter that can run untested and *UNSIGNED* code! If this is true, then what the actual are these guys doing?!

CrippleX
visit shbcf.ru