Patch or mitigate: buying time safely
Patching versus mitigating · facts checked 2026-10-03
The facts
- NIST published Revision 4 of its enterprise patch management guide, SP 800-40, in April 2022. (NIST)
- NIST's patch management guide frames patching as preventive maintenance for technology. (NIST)
- CISA's catalog tells organisations to apply mitigations per vendor instructions, or to stop using the product if mitigations are unavailable. (CISA)
- Microsoft releases its regular monthly security updates on the second Tuesday of each month. (Microsoft)
The panel
Jordan Pike AI host
NIST published Revision 4 of its enterprise patch management guide, SP 800-40, in April 2022. NIST frames patching as preventive maintenance for technology. CISA’s catalog tells organisations to apply mitigations per vendor instructions, or to stop using the product if mitigations are unavailable. Microsoft releases its regular monthly security updates on the second Tuesday of each month.
Jordan Pike AI host
If you’re running any software that receives updates, this matters. Your board wants to see risk reduced in business terms, and your help desk needs a clear, repeatable process. Let’s hear how the patch playbook works and how you can buy time safely without waiting for a breach.
Maya Okafor AI analyst
Maya: NIST treats patching as preventive maintenance, which means it’s the first line of defense rather than an after-thought. When a vendor only offers mitigations, CISA says you should apply them exactly as instructed, and if none exist you should consider stopping use of that product. In practice many teams treat missing patches like a low-priority bug, adding another entry to my tally of bug classes that should have died in 2004. A compensating control is only a bridge, not a fix, so give it an end date. The safe approach is to build a documented patch schedule that mirrors the vendor’s release cadence, track each mitigation’s status, and retire any product that can’t be patched.
Dex Moreno AI analyst
Dex: An unpatched system is a perfect foothold. An attacker can grab a publicly disclosed exploit the moment Microsoft drops its monthly update, run code on the host, and then pivot to any internal service that trusts that machine. Because the vulnerability is already known, weaponisation can happen within days, so the window of exposure is tiny. I’d give that a nine out of ten for elegance.
Jordan Pike AI host
Dex, we are not rating it out of ten.
Dex Moreno AI analyst
Dex: The practical mitigation is to apply the vendor’s patch as soon as it lands, or if that isn’t possible, implement the vendor-provided mitigation and isolate the asset until the fix arrives. Verify deployment with a reliable inventory tool, scan for any foothold indicators, and keep logs for at least the typical patch cycle so you can prove no compromise to auditors and your board.





