This is an unpopular opinion, and I get why – people crave a scapegoat. CrowdStrike undeniably pushed a faulty update demanding a low-level fix (booting into recovery). However, this incident lays bare the fragility of corporate IT, particularly for companies entrusted with vast amounts of sensitive personal information.

Robust disaster recovery plans, including automated processes to remotely reboot and remediate thousands of machines, aren’t revolutionary. They’re basic hygiene, especially when considering the potential consequences of a breach. Yet, this incident highlights a systemic failure across many organizations. While CrowdStrike erred, the real culprit is a culture of shortcuts and misplaced priorities within corporate IT.

Too often, companies throw millions at vendor contracts, lured by flashy promises and neglecting the due diligence necessary to ensure those solutions truly fit their needs. This is exacerbated by a corporate culture where CEOs, vice presidents, and managers are often more easily swayed by vendor kickbacks, gifts, and lavish trips than by investing in innovative ideas with measurable outcomes.

This misguided approach not only results in bloated IT budgets but also leaves companies vulnerable to precisely the kind of disruptions caused by the CrowdStrike incident. When decision-makers prioritize personal gain over the long-term health and security of their IT infrastructure, it’s ultimately the customers and their data that suffer.

  • magikmw@lemm.ee
    link
    fedilink
    English
    arrow-up
    26
    ·
    edit-2
    3 months ago

    This works great for stationary pcs and local servers, does nothing for public internet connected laptops in hands of users.

    The only fix here is staggered and tested updates, and apparently this update bypassed even deffered update settings that crowdstrike themselves put into their software.

    The only winning move here was to not use crowdstrike.

    • wizardbeard@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      2
      ·
      3 months ago

      It also assumes that reimaging is always an option.

      Yes, every company should have networked storage enforced specifically for issues like this, so no user data would be lost, but there’s often a gap between should and “has been able to find the time and get the required business side buy in to make it happen”.

      Also, users constantly find new ways to do non-standard, non-supported things with business critical data.

      • Bluetreefrog@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        3 months ago

        Isn’t this just more of what caused the problem in the first place? Namely, centralisation. If you store data locally and you lose a machine, that’s bad but not the end of the world. If you store it centrally and you lose the data, that’s catastrophic. Nassim Taleb nailed this stuff. Keep the downside limited, and the upside unlimited or as he says, “Don’t pick up pennies in front of a steamroller.”

    • LrdThndr@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      2
      ·
      3 months ago

      Absolutely. 100%

      But don’t let perfect be the enemy of good. A fix that gets you 40% of the way there is still 40% less work you have to do by hand. Not everything has to be a fix for all situations. There’s no such thing as a panacea.

      • magikmw@lemm.ee
        link
        fedilink
        English
        arrow-up
        6
        ·
        3 months ago

        Sure. At the same time one needs to manage resources.

        I was all in on laptop deployment automation. It cut down on a lot of human error issues and having inconsistent configuration popping up all the time.

        But it needs constant supervision, even if not constant updates. More systems and solutions lead to neglect if not supplied well. So some “would be good to have” systems just never make the cut, because as overachieving I am, I’m also don’t want to think everything is taken care of when it clearly isn’t.

        • catloaf@lemm.ee
          link
          fedilink
          English
          arrow-up
          2
          ·
          3 months ago

          Yeah. I find a base image and post-install config with group policy or Ansible to be far more reliable.

          • magikmw@lemm.ee
            link
            fedilink
            English
            arrow-up
            1
            ·
            3 months ago

            Yea we’re doing something similiar. Only update base images for bigger OS updates or if something breaks or can break.

            The general idea is to have config that works for both new PCs and the ones that are already in use. Saves on maintaining two configuration methods.

        • John Richard@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          4
          arrow-down
          3
          ·
          3 months ago

          You were all in, but was the company all in? How many employees? It sounds like you innovated. Let’s say that the company you worked for was spending millions on vendors that promised solutions but rarely delivered. If instead they gave you $400k a year, a $1 million/year budget & 10 employees… I’m guessing you could have managed the laptop deployment automation, along with some other significant projects as well.

          Instead though, people with good ideas, even loyal to the company, are competing against sales and marketing reps from billion dollar companies, and upper management are easily swooned.

          • magikmw@lemm.ee
            link
            fedilink
            English
            arrow-up
            3
            ·
            3 months ago

            I’m the only one to swoon here, and I’m as sceptical as one can be.

            I’m also a cost and my budget is on paper only. Non-IT management is complicit in crappy IT.

    • John Richard@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      7
      ·
      3 months ago

      Almost all computers can be set to PXE boot, but work laptops usually even have more advanced remote management capabilities. You ask the employee to reboot the laptop and presto!

      • magikmw@lemm.ee
        link
        fedilink
        English
        arrow-up
        7
        ·
        3 months ago

        I wonder how you’re supposed to get PXE boot to work securely over the internet. And how that helps when affected disk is still encrypted and needs unusual intervention to fix, including admin access to system files.

        I’ve been doing this for a while, and I like creative solutions, so I wonder about those issues a lot. Not much comes to my mind besides let’s recall all the laptops and do it one by one.

        • LrdThndr@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          From a home user? Probably ain’t shit-all you can do with PXE booting. But if you have a field office or somewhere a user can go with a hardware vpn appliance? Well now you’re in business.

        • wizardbeard@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          edit-2
          3 months ago

          Hypothectically you could ship a company provided router to handle the vpn connection to your remote users, so you aren’t relying on the OS to be able to boot up to get connected to the vpn for the company network and PXE environment. Lots of extra cost and mess though.

        • John Richard@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          4
          ·
          3 months ago

          I wonder how you’re supposed to get PXE boot to work securely over the internet.

          PXE boot is more of last resort IMO, but can be uses as a chainloader to a more secure option. The biggest challenge I could see security-wise is having PXE boot being ran on unsecured networks. Even then though, normally a computer will have been provisioned on a secure network and will have encryption and secure boot-based encryption, and some additional signature-based image verification.