In an enterprise environment, you rely on a service that tracks CVEs, analyzes which ones apply to your environment, and prioritizes security critical updates.
The issue here is that one of these services installed a release upgrade because Microsoft mislabelled it as security update.
For security updates in critical infrastructure, no. You want that right away, in best case instant. You can’t risk a zero day being used to kill people.
Yet another reason to not do auto-updates in an enterprise environment for mission-critical services.
In an enterprise environment, you rely on a service that tracks CVEs, analyzes which ones apply to your environment, and prioritizes security critical updates.
The issue here is that one of these services installed a release upgrade because Microsoft mislabelled it as security update.
Should still be doing phased rollouts of any patches, and where possible, implementing them on pre-prod first.
For security updates in critical infrastructure, no. You want that right away, in best case instant. You can’t risk a zero day being used to kill people.
Even security updates can be uncritical or supercritical. Conault the patch notes or get burned lol
Pre-prod is ideal, but a pipe dream for many. Lots of folks barely get prod.
We still stagger patching so things like this only wipe some of the critical infrastructure, but that still causes needless issues.