this post was submitted on 19 Jul 2024
1 points (100.0% liked)

Technology

59566 readers
4828 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] Angry_Autist@lemmy.world 0 points 4 months ago (1 children)

From my experience it was more likely to be an accidental overwrite from human error with recent policy changes that removed vetting steps.

[–] rozodru@lemmy.ca 0 points 4 months ago (1 children)

this is what I suspect also. I mean it's easy to point fingers at George Kurtz as he was CTO at Mcafee when they had their "little" snafu but...well...yeah. I strongly suspect many of his "policies" he had while CTO at Mcafee carried over to Crowdstrike. dude isn't exactly known for being a fan of testing or vetting processes. in fact he's all about quick development/crunch.

[–] Angry_Autist@lemmy.world 0 points 4 months ago

Quick development will probably spell the end of the internet once AI code creation hits its stride. It'll be like the most topheavy SCRUM you've ever seen with the devs literally incapable of disagreeing.

I was thinking about his stint at McAfee, and I think you're right. My real question is: will the next company he golden parachutes off to learn the lesson?

I'm going to bet not.