When a new zero-day affects services across multiple deployments, how do you quickly find what is exposed and decide what to patch first? I'm also worried about unmanaged servers that might not show up in the usual inventory.
How do you prioritize patching when a zero-day hits an exposed service?
Answers
Start with the vendor advisory and check which versions and configurations are affected. Then look for those services in your asset inventory, cloud accounts, deployment manifests, and package or container records. Prioritize affected instances reachable from the internet, especially where the vulnerable feature is enabled.
If a patch cannot go on immediately, restrict access or take the service offline where practical. Track those temporary measures so they don't get mistaken for a completed fix, and verify the running version after patching.
Reply to this answer
The unknown server problem deserves its own workstream. Inventory is only as good as what people remembered to register. Check cloud account and billing records against your known assets, then follow up on public endpoints or virtual machines that don't have an identified owner.
For anything unowned, work out who depends on it before shutting it down. Once the immediate issue is contained, tighten provisioning permissions and make ownership and update responsibility clear.
Reply to this answer
Don't turn the incident into an automatic decision to abandon a product. Repeated security problems, including a supply chain compromise, can reasonably trigger a review of its security practices and alternatives. That's separate from finding and containing affected deployments right now.
Reply to this answer
Add your answer
Answers are reviewed before publication.
v.294!plaidcaper:
Also check whether the advisory calls for anything beyond updating, such as rotating credentials or investigating signs of compromise. Patching alone won't undo an intrusion.