…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.
I’ve got a feeling crowdstrike won’t be as grand of target anymore. They’re sure to lose a lot of clients…ateast until they spin up a new name and erease all traces of “cdowdstrike”.
That trick doesn’t work for B2B as organizations tend to do their research before buying. Consumers tend not to.
I don’t think they will lose any big clients. I am sure they will have insurance to take care of compensations.