• Brkdncr@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      ·
      4 months ago

      Yes. Why would anyone trust Crowdstike after this? They’ve ignored foundational deployment steps.

  • boydster
    link
    fedilink
    English
    arrow-up
    13
    ·
    4 months ago

    But will you try actually installing the update on a machine or 50 to see if you bork things horrifically?

    Crowdstrike: “We are really focused on unit testing right now”

    I probably misread it, don’t mind my grumbling, rabble rabble rabble

    • sugar_in_your_tea
      link
      fedilink
      English
      arrow-up
      6
      ·
      4 months ago

      Local developer testing

      Hmm, didn’t think of that one…

      staggered deployment strategy

      Also a novel idea…

      It’s like they’re catching up to best practices from 10 years ago, good job team!

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

        Listening to literally any sysadmin would have had these practices already in play.

        I wonder if any are in the building, of if it’s all devs and “platform engineers.”

    • PlutoniumAcid@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 months ago

      Systems in scope include Windows hosts running sensor version 7.11 and above that were online between Friday, July 19, 2024 04:09 UTC and Friday, July 19, 2024 05:27 UTC and received the update.

      Definitely incorrect. My machine was powered off by physical switch at that time. It was powered off at 17:00 the day before and powered up at 08:00 CEST / 06:00 UTC and promptly bluescreened.