05.02.21

Microsoft-Centric “Ransomware Task Force”

Posted in Deception, Microsoft, Security at 3:37 am by Guest Editorial Team

Original by Mitchel Lewis, republished with permission

Microsoft ransom
Source: https://www.statista.com/statistics/701020/major-operating-systems-targeted-by-ransomware/

Summary: Mitchel Lewis, a former Microsoft employee, takes a look at Microsoft-connected or Microsoft-controlled ‘think tanks’ in ‘task force’ clothing

Although most platforms have had their flare-ups with ransomware, it’s well-known that Microsoft’s legacy architecture has a hyper-monopoly with respect to ransomware infections that consequently renders all other platforms into negligible outliers in comparison. In fact, there’s nothing in this world that Microsoft monopolizes better than ransomware attacks at the moment.

Depending on who you ask, anywhere from 85–99% of ransomware attacks occur on Microsoft architecture, often via well-known vulnerabilities. Because of this common denominator, most working within the ransomware space daily would find it supremely difficult gloss to over the vulnerability of Microsoft’s architecture as being a key component in the rising prominence of ransomware and this is especially true if they were asked to write an 80-page report on the matter.

Taskforce ransom
A “venerable” who’s who of the ransomware field.

Recently though, a team of more than 60 lawyers and supposed experts that no one has ever heard of before from software companies, cybersecurity vendors, government agencies, non-profits, and academic institutions came together with the Institute for Security and Technology, an institute that no one has ever heard of before, and achieved the irrational by developing a “comprehensive framework” attempting to tackle the modern threat of ransomware. To no surprise and in true Dunning-Kruger fashion whenever expertise is proclaimed, these experts managed to accomplish the unconscionable by overlooking Microsoft’s blatant complicity in the ransomware space and the fundamental importance of modern infrastructure in the face of IT security and prevention of ransomware in an 81-page report.

ZDNet ransom
This wasn’t even a revelation in December for anyone with half of an ass in the field of assessing root cause.

To be fair, the task farce rightfully highlighted the rise of cryptocurrency as a motivational force behind ransomware attacks and further dubbed ransomware to be a threat against our national security, this is nothing new; even my stupid ass has been talking about this for 6 months now. Many of their suggestions are relevant too and might help to some degree, but they’re reactionary and ancillary at best in comparison to an architectural shift away from Microsoft solutions; the single best preventative measure that a company can take to defend itself against various attacks plaguing industry throughout the world, ransomware or otherwise. Hell, their whole article only mentioned prevention 3 times.

Safety Detectives
Source: https://www.safetydetectives.com/blog/ransomware-statistics/

With the exception of Hafnium, most attacks are rudimentary at best and exploit well-known vulnerabilities throughout the Microsoft ecosystem and the ignorant companies refusing to mitigate these vulnerabilities in favor of convenience. More often than not, ransomware infections are a direct consequence of phishing campaigns, poor password complexity, poor lockout policies that embolden brute force attacks, poorly trained users, no MFA, no VPN, and admins ignorantly exposing RDP to the WAN, etc. All of which are fundamental no-no’s in the world of IT security that are amazingly easy to prevent and almost all of which are targeted exclusively at Microsoft cloud and server solutions hosted on-premise by their clientele. And a task force of supposed experts would have acknowledged this if they were actually experts in ransomware or IT security.

Given all of this, it seems as if Microsoft is just as much of a threat to our national security as ransomware itself; you can’t have one without the other. Although many of these attacks are preventable and much can be done to supplement Microsoft architecture to harden against said attacks, it’s becoming increasingly evident that it’s impossible for most teams to account Microsoft’s entire threat surface, ransomware or otherwise, and that it’s simply too complex, costly, and cumbersome for most IT staff to manage. As such migrating away from the Microsoft ecosystem entirely is the single most viable way to reduce your threat surface against ransomware and pretty much every other form of attack; the drastic reductions in IT ownership costs and improved employee morale are nice too I hear.

This is not easy though. On top of being notorious for ransomware, Microsoft is notorious for optimizing their solutions for lock-in, addiction if you will, which makes them incredibly difficult and costly to migrate away from. The benefits are immediate to those with the grit to migrate though.

But instead of highlighting any of this, the task farce appears to be operating under a false pretense that ransomware is somehow a platform-agnostic affair and that architecture is irrelevant while further ignoring the important role that architecture plays in preventing ransomware and neglecting to showcase Microsoft for being a common denominator that it is; bungling it massively if you will. This is so much the case that they only mentioned the word architecture once in their entire report. If anything, they appear to be adopting Microsoft’s “assume breach” approach which is just their way of shifting blame to the people who support and manage their unsupportable and unmanageable solutions. All of which forces me to question the degree of their expertise and their intentions.

As harsh as this may seem at first, questioning their expertise is fair when there seems to be no focus on preventative measures and devoid of even the most obvious architectural recommendations; no acknowledgment that most ransomware attacks are preventable, no acknowledgment that not all architectures are equal, and no acknowledgment that they often occur when fundamentals are abandoned or forbidden. More often than not, there’s an IT nerd saying, “I told you so.”, to their change-averse management post-mortem with emails to back it up and this just isn’t something that experts can simply ignore when trying to prevent ransomware.

 Katie Nickels with context
Recommendations given, no response as expected.

Katie Nickels

To say the least, the IST report would look markedly different if boots on the ground were at least consulted with beforehand, hence why I began to question it so flagrantly as someone that has dealt with ransomware and its prevention for half a decade now. In an effort to clarify their expertise, I reached out to Katie Nickels, one of the task farce members, and she didn’t argue or lambast me with credentials proving otherwise and merely asked for my recommendations; a low-key admission of my expertise concern having merit if you’re into that whole social engineering thing.

Unsurprisingly and rather than supplying ransomware experts that could provide action items for people that actually work against ransomware on a daily basis which Microsoft has an abundance of, Microsoft instead supplied their digital diplomacy team comprised of Kemba Walden, Ginny Badanes, Kaja Ciglic, and Ping Look, which is curious because none of these people get wake-up calls when ransomware is dominating the infrastructure of their clientele. So far as I can tell, none of them seem to have even gone on the record about ransomware prior to this task farce being formed and it’s hard to see their role in the task farce and the absence of Microsoft’s complicity in their report as a coincidence.

Katie Nickels' reply

When combining these oversights, the dominant presence of Microsoft spin artists within their task farce, and the high likelihood of a sizable donation from Microsoft to the Institute for Security and Technology though, none of this should come as a shock to you. As shown with fraud of dolphin-safe labeling/oversight, we live in a world where industry has a penchant for hijacking its own watchdogs with massive donations and further installing people throughout their ranks that are sympathetic to the plight of starving investors; all of which Microsoft has been accused of before which appears to be the case with the #ransomwaretaskforce. Roy Schestowitz refers to this approach as entryism and it may be time to pay more attention to these nefarious approaches in the tech space.

In summary, trying to cull ransomware via decree alone is only viable in comparison to throwing virgins into a volcano. Given Microsoft’s monopoly on ransomware attacks, the single best thing that any organization can do to prevent ransomware from ravaging your IT infrastructure is to migrate far, far away from Microsoft architecture entirely. Once that is accomplished, companies can implement multi-factor authentication, complex password requirements with password managers, and spare no expense on user training to further reduce their exposure to ransomware and other attacks that leverage these very same threat vectors. And companies can do this while reducing their ownership costs by a factor of 3 conservatively as showcased by IBM when they standardized on the Apple ecosystem; those less efficient at managing PCs at scale than IBM stand to see greater reductions.

You’re welcome to disagree and stay on Microsoft architecture or believe that approaching ransomware via bureaucracy- laden decrees is viable. It’s your funeral. But if you find yourself in this precarious position of deferring to lawyers and people that have never been on the hook to remove ransomware before, it may be a sign that you should do more reading and less talking about the matter instead.

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

This post is also available in Gemini over at:

gemini://gemini.techrights.org/2021/05/02/ransomware-task-force/

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

What Else is New


  1. Links 21/6/2021: NVIDIA’s DLSS and Most Beautiful GNU/Linux Distributions

    Links for the day



  2. Neil's Misgovernment

    The GNOME Foundation has one member of staff fewer; the attack on the founder/father of Free/libre software activism and GNU (the "G" in GNOME) failed and backfired spectacularly



  3. IRC Proceedings: Monday, June 21, 2021

    IRC logs for Monday, June 21, 2021



  4. Virtual Injustice -- Part 14: How Mandatory ViCo Became the “New Normal”

    How mandatory ViCo hearings gradually became the "New Normal" at the EPO



  5. Links 21/6/2021: Rocky Linux 8.4, IPFire 2.25 - Core Update 157, and SUSE Linux Enterprise 15 SP3

    Links for the day



  6. There Are Bigger Scandals Than Revisionism and Brand Dilution at the Linux Foundation

    There are some misconceptions that need tackling; back in February (more than 4 months ago) the so-called 'Linux' Foundation decided to associate with yet another controversial drive that has nothing to do with Linux; some people think it's a new thing and leap to conclusions



  7. Techrights Video Gallery Without JavaScript

    Some of the improvements made this morning to the gallery of recent videos



  8. IRC Proceedings: Sunday, June 20, 2021

    IRC logs for Sunday, June 20, 2021



  9. Links 21/6/2021: Linux 5.13 RC7, IRC.com by Freenode

    Links for the day



  10. Virtual Injustice -- Part 13: Let the Games Continue…

    "It would be nice to think that the events of 28 May have given the Enlarged Board pause for thought."



  11. Links 20/6/2021: Akademy 2021 Underway and Linux Foundation Blasted

    Links for the day



  12. EPO: Fake Patents, Fake (Paid-for) Patent Coverage, and Fake Awards for Public Relations Purposes

    The media has been thoroughly corrupted, patent legitimacy has been severely damaged (far too many European Patents aren't in compliance with the EPC anymore), and Team UPC is trying to undermine the EPC and turn Europe into another Texas



  13. Changes in IRC and New Features Over Gemini Protocol or the World Wide Web

    We examine more closely some of the latest changes in the site and the capsule (Web and Gemini, respectively); we show that it’s possible to keep abreast of IRC using nothing but a text editor, a Gemini client… or even the command line alone



  14. IRC Proceedings: Saturday, June 19, 2021

    IRC logs for Saturday, June 19, 2021



  15. We Need and Deserve a Saner Patent System in Europe

    The laughing stock that the patent system, the patent law firms, and patent media became (over the past few years) must be replaced; at the moment we have a cabal connected to a bunch of criminals running the entire show and the public understandably grows impatient (at least people who are sufficiently informed; the criminals have already intimidated and bribed a lot of the media and they're still bribing more of it, as we shall demonstrate later today)



  16. [Meme] IRC Wars in a Nutshell

    In terms of large IRC networks, we’re in trouble (unless we self-host) because they seem to be dividing themselves along political lines rather than anything technical or something of an on-topic/relevant substance. Using networks for Free software projects/organisations to push one’s political agenda is not acceptable because it’s starting to seem like in IRC space, FN has become the Front Nationale (French) and LC is Liberal Coalition. Both FreeNode and Libera Chat have managed to turn from technical platforms into political parties, in effect using technical networks (intended for technical projects) to push someone's political agenda and thus misusing them for personal gain. There’s no free lunch. As it turns out, FreeNode’s new owner (Andrew Lee) has just outed himself as a huge Donald Trump supporter who speaks of “these fuckers who stole that shit” (he meant the election, which he insists Trump actually won in 2020).



  17. IBM Handles More Removals of Signatures From Its Hate Letter Against Richard Stallman

    Less than a day ago IBM processed a request for removal (from its hate letter); as someone put it in a letter to us, also less than a day ago: “When all of this started in 2019, the Red Hat GNU developers showed off their colours. The best way to attack an organisation is from the inside. Using GNU developers was a dead giveaway. Google and Microsoft are very much on the team with IBM. I believe they’ve made headway into the Free/Libre software community and have persuaded senior Debianties to go along with them.” That same message, from an anonymous GNU maintainer, said: “The strategy to target major distributions is clear and present danger. I’m not sure what arguments of persuasion are being used, but I’m pretty sure their main tool is currency. RMS needs a lot of strategic support from experts who will rally to the Free Software cause. He needs great lawyers, some corporate minds, and intelligence specialists.” Sometimes it seems or feels like by simply buying Red Hat (the staff) IBM infiltrated the GNU Project and now it is vainly making claims like 'GNU is IBM' and thus IBM et al can command/tell the FSF who should run FSF, not only GNU. Such entryism isn’t hard to see; “An open letter in support of Richard Matthew Stallman being reinstated by the Free Software Foundation” has meanwhile garnered 6,758 signatures. The opposite letter is only decreasing in support (signatures lost).



  18. Links 20/6/2021: Debian GNU/Linux 10.10 “Buster” Released and LF Revisionism Resumes

    Links for the day



  19. The EPO's Enlarged Board of Appeal Has Already Lost the Case in the Court of Public Opinion

    Personal views on the sordid state of the Enlarged Board of Appeal (EBoA), which by extension bodes poorly for the perception of independence in every Board of Appeal (BoA); the patent tribunals have been captured by patent maximalists who either stack the panels or intimidate judges into ruling in a particular way



  20. Virtual Injustice -- Part 12: Carl Josefsson – Down But Not Out!

    António Campinos still controls Josefsson, who controls all the judges, so in effect all the legal cases (including some about European software patents) are manipulated by the Office the judges are supposed to judge



  21. Links 19/6/2021: Wine 6.11 and Proton 6.3-5 RC

    Links for the day



  22. IRC Proceedings: Friday, June 18, 2021

    IRC logs for Friday, June 18, 2021



  23. Virtual Injustice -- Part 11: Perceptive Comments and Caustic Criticism

    The EPO‘s management managed to silence a lot of the critical media (handouts and threats from Benoît Battistelli and António Campinos), but silencing comments is a lot harder; though we don’t know which ones were moderated out of existence…



  24. Links 18/6/2021: Mir 2.4, ActivityWatch 0.11, Microsoft Breaks Its Own Repos

    Links for the day



  25. [Meme] When the 'Court' Drops

    As the EPO sneakily outsourced courts to American companies and parties in dispute depend on their ISP for “access to justice” there’s a catastrophic impact on the very concept of justice or the right to be heard (sometimes you don’t hear anything and/or cannot be heard)



  26. The EPO's Virtual Injustice and Virtual ('News') Media

    A discussion of this morning's post (part 10 in a series) about the shallow media/blog coverage that followed or accompanied last month's notorious EPO hearing



  27. Links 18/6/2021: LibreOffice 7.2 Beta, Elementary OS 6.0 Beta 2, and Linux Mint 20.2 “Uma” Beta

    Links for the day



  28. The Self-Hosting Song

    Cautionary tales about outsourcing one's systems to companies that could not care less about anyone but themselves



  29. IRC Proceedings: Thursday, June 17, 2021

    IRC logs for Thursday, June 17, 2021



  30. [Meme] Swedish Justice

    The EPO‘s patent tribunals have been mostly symbolic under the Benoît Battistelli and António Campinos regimes; giving them back their autonomy (and removing those who help Battistelli and Campinos attack their autonomy) is the only way to go now


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts