Crowdstrike computers as of now be like:
Uploaded by ryansean071 Jul 19, 2024 at 10:20PM EDT
crowdstrike spongebob squilliam returns bsod
Origin Entry: CrowdStrike Microsoft Global Outage
File type: png
Resolution: (1420px x 1139px)
File size: 2.52 MB
![Dion Almaer @dalmaer Comcast just emailed saying that they are safe from CrowdStrike because they run DOS. And SouthWest said they got lucky by running Windows 3.11 for Workgroups, Phew. Traducir post 1:09 p. m. - 19 jul. 2024 - 15,7 mil Reproducciones 21 Reposts 6 Citas 171 Me gusta 8 Elementos guardados 27 Σ 8 <]](https://i.kym-cdn.com/photos/images/list/002/865/993/842.png "The superiority of MS-DOS and Windows 3.11 for Workgroups")
![zmmmmm 2 hours ago | next [-] So CrowdStrike is deployed as third party software into the critical path of mission critical systems and then left to update itself. It's easy to blame CrowdStrike but that seems too easy on both the orgs that do this but also the upstream forces that compel them to do it. My org which does mission critical healthcare just deployed ZScaler on every computer which is now in the critical path of every computer starting up and then in the critical path of every network connection the computer makes. The risk of ZScaler being a central point of failure is not considered. But - the risk of failing the compliance checkbox it satisfies is paramount. All over the place I'm seeing checkbox compliance being prioritised above actual real risks from how the compliance is implemented. Orgs are doing this because they are more scared of failing an audit than they are of the consequences failure of the underlying systems the audits are supposed to be protecting. So we need to hold regulatory bodies accountable as well - when they frame regulation such that organisations are cornered into this they get to be part of the culpability here too. reply.](https://i.kym-cdn.com/photos/images/newsfeed/002/865/267/17c.png "clown technology")
