Take a minute to turn this off (or at least be aware it exists).

One of the most important things you can do for your security program this week is to proactively discuss security controls with your stakeholders. Admit that automatic content (signature) update is a risk, but delaying those updates is a bigger risk. Talk candidly about vulnerability management and how this plays into the equation. Most importantly, don't wait for stakeholders to come to you. When they come to you, they'll have already taken a position (usually uneducated position) on things. When you're proactive, you get to control the narrative. Or (as my vet says) remember that it's FAR easier to prevent heartworms than it is to treat them. s/heart/brain/

.@CrowdStrike has confirmed they're no longer pushing the faulty update, so you only have to fix the machines that were already stuck in a BSOD loop. Anything that isn't impacted now shouldn't be impacted.