…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.

  • Hazzia@infosec.pub
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    2
    ·
    4 months ago

    I’m gonna take from this that we should have AI doing disaster recovery on all deployments. Tech CEO’s have been hyping AI up so much, what could possibly go wrong?

    • Couldbealeotard@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      4 months ago

      What are the chances that Crowdstrike started using ai to do their update deployments, and they just won’t admit it?