• wolfylow@lemmy.world
      link
      fedilink
      English
      arrow-up
      22
      ·
      3 months ago

      Found this post that explains what happened in detail: https://lemmy.ohaa.xyz/post/3522666

      As an application developer (rather than someone who can/does code operating systems) I was just left open-mouthed …

      Looks like they’re delivering “code as content” to get around the rigour of getting an updated driver authorised by MS. I realise they can’t wait too long for driver approval for antivirus releases but surely - surely - you have an ironclad QA process if you’re playing with fire like this.

    • b161@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 months ago

      Do you know if the sensor update policy had been set to N-2 would this have avoided the issue?

      • starneld@infosec.pub
        link
        fedilink
        English
        arrow-up
        7
        ·
        3 months ago

        Setting the update policy to N-2 (or any other configuration) would not have avoided the issue. The Falcon sensor itself wasn’t updated, which is what the update policy controls. As it turns out, you cannot control the content channel updates - you simply always get the updates.