Microsoft is Still Hurting Badly From CrowdStrike-gate (Now It Plays Dirty to Bypass Technical People)
YESTERDAY we added an article entitled "CrowdStrike estimates the tech meltdown caused by its bungling left a $60 million dent in its sales" and then said: "What about the billions in damages caused by Windows and clownstrike [sic] malfunctioning and the massive loss of lives?"
Well, clownstrike (CrowdStrike) isn't the sole culprit. We explained this last month, many times in fact.
We saw several reports like the above (maybe chatbots making permutations of the same) and a reader sent along a similar report, "CrowdStrike Sales Outlook Weakens After Microsoft Outage".
The most interesting report was not one of the many puff pieces about a so-called 'security summit' of CrowdStrike and Microsoft (basically marketing, propaganda, cover-up, and lobbying), which we shelved for reference in IRC but left out, i.e. excluded, from Daily Links. It was this article which says: "US Senator Ron Wyden (D-OR), who has been very critical of Microsoft's shoddy security performance while raking in billions of dollars in government contracts, didn't get an invite, we're told. So…some friendly government officials and security vendors but no press or members of the public ensure "the highest level of transparency" in Microsoft's book?"
Typically Microsoft. As an associate put it: "Non-disclosure, non-disparagement, etc hidden in contracts?"
"A list of the government participants who shamefully participated is needed. Remember the clownstrike has not been the only major outage in the last year even..."
Right, it keeps happening and Microsoft always tries to spin that as a "rotten apple" and "won't happen again".
Had Microsoft not been bribing politicians (it still does), Microsoft would already be altogether blacklisted from procurement, even based on its technical track record, not just the corruption.
The so-called 'security summit' is just an indication that Microsoft is still hurting badly from last month's global incident. It was a Windows incident. █