• Carighan Maconar@lemmy.world
    link
    fedilink
    arrow-up
    109
    ·
    1 year ago

    This is, in a lot of ways, impressive. This is CrowdStrike going full “Hold my beer!” about people talking about what bad production deploy fuckups they made.

    • KomfortablesKissen@discuss.tchncs.de
      link
      fedilink
      arrow-up
      23
      arrow-down
      2
      ·
      1 year ago

      I’m volunteering to hold their beer.

      Everyone remember to sue the services not able to provide their respective service. Teach them to take better care of their IT landscape.

      • ricecake@sh.itjust.works
        link
        fedilink
        arrow-up
        23
        ·
        1 year ago

        Typically auto-applying updates to your security software is considered a good IT practice.

        Ideally you’d like, stagger the updates and cancel the rollout when things stopped coming back online, but who actually does it completely correctly?

        • KomfortablesKissen@discuss.tchncs.de
          link
          fedilink
          arrow-up
          15
          ·
          1 year ago

          Applying updates is considered good practice. Auto-applying is the best you can do with the money provided. My critique here is the amount of money provided.

          Also, you cannot pull a Boeing and let people die just because you cannot 100% avoid accidents. There are steps in between these two states.

              • ricecake@sh.itjust.works
                link
                fedilink
                arrow-up
                5
                ·
                1 year ago

                That’s totally fair. :)

                I work at a different company in the same security space as cloudstrike, and we spend a lot of time considering stuff like “if this goes sideways, we need to make sure the hospitals can still get patient information”.

                I’m a little more generous giving the downstream entities slack for trusting that their expensive upstream security vendor isn’t shipping them something entirely fucking broken.
                Like, I can’t even imagine the procedureal fuck up that results in a bsod getting shipped like that. Even if you have auto updates enabled for our stuff, we’re still slow rolling it and making sure we see things being normal before we make it available to more customers. That’s after our testing and internal deployments.

                I can’t put too much blame on our customers for trusting us when we spend a huge amount of energy convincing them we can be trusted to literally protect all their infrastructure and data.

                • KomfortablesKissen@discuss.tchncs.de
                  link
                  fedilink
                  arrow-up
                  3
                  ·
                  1 year ago

                  I can put the blame to your customers. If I make a contract with a bank they are responsible for my money. I don’t care about their choice of infrastructure. They are responsible for this. They have to be sued for this. Same for hospitals. Same for everyone else. Why should they be exempt from punishment for not providing the one service they were trusted to provide? Am I expected to feel for them because they made the “sensible choice” of employing the cheapest tools?

                  This was a business decision to trust someone external. It should not be tolerated that they point their fingers elsewhere.

  • Logh@lemmy.ml
    link
    fedilink
    arrow-up
    104
    ·
    1 year ago

    Funny how CrowdStrike already sounds like some malware’s name.

  • psycho_driver@lemmy.world
    link
    fedilink
    arrow-up
    35
    ·
    1 year ago

    The answer is obviously to require all users to change their passwords and make them stronger. 26 minimum characters; two capitals, two numbers, two special characters, cannot include ‘_’, ‘b’ or the number ‘8’, and most include Pi to the 6th place.

    • arendjr@programming.dev
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      Sorry, I don’t understand. Do you mean there have to be 6 digits of Pi in there, or the sixth character must be π? I’m down either way.

  • Solemarc@lemmy.world
    link
    fedilink
    arrow-up
    15
    ·
    1 year ago

    Maybe this is a case of hindsight being 20/20 but wouldn’t they have caught this if they tried pushing the file to a test machine first?

      • JackbyDev@programming.dev
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        1 year ago

        Well, it is hindsight 20/20… But also, it’s a lesson many people have already learned. There’s a reason people use canary deployments lol. Learning from other people’s failures is important. So I agree, they should’ve seen the possibility.

    • Gsus4@programming.dev
      link
      fedilink
      arrow-up
      11
      arrow-down
      1
      ·
      1 year ago

      I saw one rumor where they uploaded a gibberish file for some reason. In another, there was a Windows update that shipped just before they uploaded their well-tested update. The first is easy to avoid with a checksum. The second…I’m not sure…maybe only allow the installation if the windows update versions match (checksum again) :D

    • undu@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      It’s a sequence of problems that lead to this:

      • The kernel driver should have parsed the update, or at a minimum it should have validated a signature, before trying to load it.
      • There should not have been a mechanism to bypass Microsoft’s certification.
      • Microsoft should never have certified and signed a kernel driver that loads code without any kind signature verification, probably not at all.

      Many people say Microsoft are not at fault here, but I believe they share the blame, they are responsible when they actually certify the kernel drivers that get shipped to customers.

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    11
    ·
    1 year ago

    Now threat actors know what EDR they are running and can craft malware to sneak past it. yay(!)

    • marcos@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      1 year ago

      Smart threat actors use the EDR for distribution. Seems to be working very well for whoever owned Solar Winds.

  • LeFantome@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Who says it was accidental?

    Netflix knew they were going to move from DVD rentals to streaming over the Internet. It is right in their name.

    CrowdStrike knew they were eventually going to _________. It is right in their name.