• ditty@lemm.ee
    link
    fedilink
    English
    arrow-up
    73
    ·
    4 months ago

    $5.4 Bn so far, not including lost worker productivity or damage to brand reputations, so that’s a very conservative estimate. And Cybersecurity insurance will supposedly only cover up to 20% of that (but good luck getting even that much). What a clusterf***

      • 11111one11111@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 months ago

        No it’s all of them because all the companies combined out side of the 500 wouldn’t even have enough net worth large enough to move the needle. So technically they may not be included but would be covered by whatever amount they rounded up to make the even 5.4b

  • Imgonnatrythis@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    70
    ·
    4 months ago

    “CrowdStrike said it also plans to move to a staggered approach to releasing content updates so that not everyone receives the same update at once, and to give customers more fine-grained control over when the updates are installed.”

    Hol up. So they like still get to exist? Microsoft and affected industries just gonna kinda move past this?

    • BakerBagel@midwest.social
      link
      fedilink
      English
      arrow-up
      31
      ·
      4 months ago

      Haven’t seen anything from the affected major players. Obviously Crowdstrike isn’t going to say they are fucked long term, they have to act like this is just a little hiccup and move on. Lawsuits are absolutely incoming

    • Ledivin@lemmy.world
      link
      fedilink
      English
      arrow-up
      22
      ·
      edit-2
      4 months ago

      We’ll see how fucked they are from SLA breaches/etc., and then we’ll see how many companies jump ship to an alternative. We won’t have the real fallout from this event for months or years.

    • Kairos@lemmy.today
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      1
      ·
      4 months ago

      Companies using CrowdStrike and Windows aren’t really the type to be active about this sort of thing.

      • Imgonnatrythis@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 months ago

        Yeah, what was I thinking. United airlines was bankrupt and literally beating people up on their planes and still got taxpayer payouts and is around paying investors divends still today.

  • 0x0@programming.dev
    link
    fedilink
    English
    arrow-up
    38
    arrow-down
    1
    ·
    edit-2
    4 months ago

    On Wednesday, CrowdStrike released a report outlining the initial results of its investigation into the incident, which involved a file that helps CrowdStrike’s security platform look for signs of malicious hacking on customer devices.

    The company routinely tests its software updates before pushing them out to customers, CrowdStrike said in the report. But on July 19, a bug in CrowdStrike’s cloud-based testing system — specifically, the part that runs validation checks on new updates prior to release — ended up allowing the software to be pushed out “despite containing problematic content data.”

    When Windows devices using CrowdStrike’s cybersecurity tools tried to access the flawed file, it caused an “out-of-bounds memory read” that “could not be gracefully handled, resulting in a Windows operating system crash,” CrowdStrike said.

    Couldn’t it, though? 🤔

    And CrowdStrike said it also plans to move to a staggered approach to releasing content updates so that not everyone receives the same update at once, and to give customers more fine-grained control over when the updates are installed.

    I thought they were already supposed to be doing this?

    • Plopp@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 months ago

      Couldn’t it, though? 🤔

      IANAD and AFAIU, not in kernel mode. Things like trying to read non existing memory in kernel mode are supposed to crash the system because continuing could be worse.

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

          They could and clearly they should have done that but hindsight is 20/20. Software is complex and there’s a lot of places that invalid data could come in.

    • whatwhatwhatwhat@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 months ago

      The fact that they weren’t already doing staggered releases is mind-boggling. I work for a company with a minuscule fraction of CrowdStrike’s user base / value, and even we do staggered releases.

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

        They do have staggered releases, but it’s a bit more complicated. The client that you run does have versioning and you can choose to lag behind the current build, but this was a bad definition update. Most people want the latest definition to protect themselves from zero days. The whole thing is complicated and a but wonky, but the real issue here is cloudflare’s kernel driver not validating the content of the definition before loading it.

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

    For the rest of history this sort of thing will mention Crowdstrike, or it might even be called a “crowdstrike.”

    You can’t buy that kind of marketing