Patch management guides
Thirteen guides, each answering one question about patching from sources read on 19 Nov 2026. They run from the definition of a patch management policy to the compliance rate and the difference between patch and vulnerability management. Each guide names its sources and the texts that could not be read.
The guides
- What a patch management policy is: the parts a policy must have and the clause behind each.
- How to write a patch management policy: nine sections in order, a fill-in skeleton and the NIST scenarios.
- Patch management lifecycle: the five NIST phases and the process page for each.
- Patch management vs vulnerability management: a question-by-question comparison with CIS Control 7 and SSDF.
- Hotfix vs patch: NIST's glossary entries for patch and hotfix, and the one-line definition a policy needs.
- How often to patch: cadence by source and Patch Tuesday dates to February 2027.
- Proving patch compliance to an auditor: the evidence record, one row per asset per patch.
- Patch compliance rate: formula, three variants and why clocks differ.
- Third-party and open source patching: SSDF clauses and policy wording for components.
- Automated patch management: the default approval delays and severity filters in AWS, Azure and Autopatch, and the policy lines they touch.
- What is patch management: the definition and scale figures for 19 Nov 2026.
- Patch management program: NIST's six example maintenance groups and a start-up sequence with a record for each step.
- Patch management practices, each with its source: ten practices, the clause behind each and the record that proves it.
Reading order
For a new policy: start with what it is, then how to write it, then fill the template. For an audit: evidence and rate. For definitions: what is patch management and hotfix vs patch.
One guide is narrow on purpose: the vulnerability management comparison covers where the two functions meet, not how to build a vulnerability program. Short answers to 17 common questions are in the FAQ.
Related sections
The patch window table has one page per framework. The process has nine steps, patching by asset class has eleven classes, and the glossary has the terms.
Sources
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022), read 19 Nov 2026
- NCSC, Cyber Essentials Requirements for IT Infrastructure v3.3, Security Update Management, read 19 Nov 2026
- CISA, BOD 26-04, Prioritizing Security Updates Based on Risk, read 19 Nov 2026
Last reviewed 19 Nov 2026