…according to a Twitter post by the Chief Informational Security Officer of Grand Canyon Education.

So, does anyone else find it odd that the file that caused everything CrowdStrike to freak out, C-00000291-
00000000-00000032.sys was 42KB of blank/null values, while the replacement file C-00000291-00000000-
00000.033.sys was 35KB and looked like a normal, if not obfuscated sys/.conf file?

Also, apparently CrowdStrike had at least 5 hours to work on the problem between the time it was discovered and the time it was fixed.

  • phx@lemmy.ca
    link
    fedilink
    English
    arrow-up
    24
    ·
    3 months ago

    Security products of this nature need to be tight with the kernel in order to actually be effective (and prevent actual rootkits).

    That said, the old mantra of “with great power” comes to mind…

    • arin@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      1
      ·
      edit-2
      3 months ago

      with great power, don’t lay off the testing team (force return to office or get fired ultimatums)

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

        It’s fine, they’ve just switched to a crowd-sourced testing strategy.