Patch management program
NIST SP 800-40 Rev. 4 (April 2022) builds a patch program on maintenance groups: sets of assets with similar needs, each with a plan for each of four scenarios. Section 3.4 gives six example groups. Read on 19 Nov 2026, they show how to start and what record proves each step.
Six example groups from NIST section 3.4
NIST defines a maintenance group as "a set of assets with similar characteristics that generally have the same software maintenance needs for each risk response scenario." Section 3.4 lists six simplified examples, reproduced here by the four attributes NIST gives for each (NIST SP 800-40 Rev. 4).
| Group | Software to patch | Outage restriction | Existing mitigations | Impact if compromised |
|---|---|---|---|---|
| Mobile workforce laptops | Firmware, operating systems, client applications | Tolerant to downtime | Endpoint security controls on the laptops | Moderate |
| On-premises datacenter | Firmware, operating systems, applications for server platforms | Scheduled outage windows for all non-emergency situations | Network-based access controls and controls on the assets | High |
| Legacy OT assets | None; software no longer supported and cannot be patched | Scheduled outage windows for all non-emergency situations | Network isolation, physical security controls | High |
| Smartphones for the mobile workforce | Operating systems and mobile apps | Tolerant to downtime | Mobile device security controls | Moderate |
| On-premises servers for automated software testing | Firmware, server OS, virtualization software, guest operating systems, applications | Usually tolerant to downtime | Network-based access controls and controls on the assets | Moderate |
| Containers with customer-facing applications in the public cloud | Container operating systems, application modules | Highly tolerant to downtime | Controls on the container operating system | High |
A count of the table (this site's arithmetic, not NIST's) shows why outage restriction and impact are not enough to define a group. Six groups give only four distinct pairs of outage restriction and impact: laptops and smartphones share (tolerant, moderate), and the datacenter and legacy OT share (scheduled windows, high). NIST keeps each pair apart because the software to patch and the existing mitigations differ, and legacy OT has nothing to patch at all.
Why unpatchable assets get a group
NIST says "Instead of denoting certain assets or types of assets as 'exceptions,' there should be maintenance groups for them," because an asset that cannot be patched "still has software maintenance needs." For that group, section 3.5.4 asks for "an approved set of methods" that security architects reviewed in advance, and a periodic re-evaluation with two parts: a risk assessment of whether the alternatives to patching still work, and a cost-benefit analysis of the asset's value against the cost of mitigating, transferring or accepting the risk. The policy wording for what is recorded when a patch is skipped is in the exceptions clause template.
Start-up sequence and the record each step leaves
- Assign every asset to a group (section 3.4). Record: the inventory export with a group field filled for every asset, and a count of assets with the field blank (the target is zero).
- Give each unpatchable asset a group of its own (3.4, 3.5.4). Record: the approved mitigation set for that group and the date the architects reviewed it.
- Write a plan for each group and each applicable scenario (3.5). Record: the plan with the "timeframes for beginning and ending each action", plus the risk assessment process that decides which plan applies and when to switch.
- Name the canary assets and the grace period (3.5.1). Record: the canary membership list and the date after which installation is forced, directly or by blocking network access.
- Choose metrics per audience (3.6). Record: one metric definition for each audience, because NIST notes that a bare percentage patched is not actionable; see patch compliance rate.
- Reassess the groups periodically (3.4). Record: the date of each reassessment and the groups added, merged or removed.
The NIST SP 800-40 page covers the four scenarios in full, and the policy sections and procedure template carry the written side. Who owns each record is a choice the policy makes by role name; NIST names seven audiences for metrics in section 3.6 but assigns no owners.
4.3 Patch windows
| Severity | Window3143090180 days |
|---|---|
| 1. Known exploited, internet-facing | 3 calendar daysApplies to: Systems reachable from the internet |
| 1. Known exploited, other | 14 calendar daysApplies to: All other systems |
| 2. Critical | 14 calendar days |
| 3. High | 30 calendar daysApplies to: All systems [set 14 if you hold Cyber Essentials] |
| 4. Medium | 90 calendar days |
| 5. Low | 180 calendar days |
| Routine baseline | Every month, or more oftenApplies to: Operating system and application updates |
No framework selected: every window above is the site template's suggested default, and the clock starts as this section states.
Questions
patch management program
A patch management program is the standing set of groups, plans, records and reports that carry out the policy. In NIST SP 800-40 Rev. 4 it starts from maintenance groups, each with a plan for routine patching, emergency patching, emergency mitigation and unpatchable assets.
what is patch management program
It is the recurring work of keeping each group of assets patched or mitigated, with a record for each step. The start-up sequence above lists six steps and the record each one leaves.
what is patch management process
It is the repeated sequence of identifying, prioritizing, acquiring, installing and verifying patches. The steps are laid out in the process.
Sources
Last reviewed 19 Nov 2026