There is no point. They drag the social media CEOs in front of congress regularly, give them a stern talking-to, and then it's back to business as usual.

Two things come to mind:

1. Do we need compliance regulations on minimum testing infrastructure etc for kernel-level development so that dangerous bugs can’t be mistakenly released?

2. Kurtz has a history of this calibre of issue under their leadership (both at CrowdStrike and at McAfee); why does this keep happening under their leadership and what can we learn to instruct other orgs not to make the same mistakes (e.g. via CISA directives)?

I'd like to see a televised paddling. Pants down bend over closeup shot of face, let go of ankkes and another whack.

Be far more effective than fines.

It wasn’t the whole world. Our business went on just fine without any issues and we were running Windows too. And the thing about that is you have a lot of people pushing for a homogeneous culture on Linux, not realizing that 1) crowdstrike was crashing Linux systems a couple months ago and 2) if it were to become the dominant system we could see things happen that way too.

So I’m kinda curious, what would you suggest?

Trick is that any respectable OS should crash in this scenario. Including when cloudstrike did this to Linux.

There was an uncaught exception in a program that was using a workaround to run unsigned code at a kernel level.

The only part of this on MS is not investigating how Cloudstrike was doing updates. Otherwise its 100% Cloudstrike that set all of this in motion.

People are definitely talking about that. Maybe not in the media but in the affected industries.

It was different when we weren't living in a software as a service world. You could be mono platform but since you had complete control you didn't have to worry you could roll out how you wanted.

Crowd strike by it's very nature is supposed to be live updated throughout the day as threats emerge.

If we want services like these maybe we need to come up with better ways to isolate them from the kernel while still allowing crowdstrike type software to detect threats

Solving the crowdstrike problem could solve kernel level anti cheat software too

Windows blames the EU for forcing them to allow other vendors with access to do this type of thing rather than just letting Microsoft themselves manage it.

I'm not sure I buy that argument but it's going to get a bit tricky.

I dislike windows and I pretty much agree with your point, but this was crowdstrike through and through, wasn’t it? They’re there ones selling a product that requires privileged access, they’re the ones who need to be responsible with that privilege. Microsoft made the OS, but they didn’t do the breaking here.

I simultaneously hear from people that the Internet runs on Linux and also everything in the world runs on windows