Patching by asset type
Eleven asset classes need different patch windows because their vendors ship on different rhythms: Microsoft on the second Tuesday, Oracle on four fixed dates a year, Kubernetes monthly, Android on the first Monday. NIST SP 800-40 Rev. 4 calls the grouping a maintenance group. Read 19 Nov 2026.
Why a policy groups assets by class
NIST defines the unit: “A maintenance group is a set of assets with similar characteristics that generally have the same software maintenance needs for each risk response scenario.” It then asks for a maintenance plan for each group, with “the timeframes for beginning and ending each action” (NIST SP 800-40 Rev. 4, sections 3.4 and 3.5). Its examples of groups include containers running customer-facing applications in a public cloud, with outage restrictions described as “highly tolerant to downtime,” and OT and IoT assets “with life-safety impact.” A class page below is the starting point for one such group: it names the vendor rhythm, the usual constraint on the window, and the evidence to keep.
The eleven classes
| Class | Release rhythm in one line (read 19 Nov 2026) | Constraint that sets the window |
|---|---|---|
| Windows endpoints and servers | Second Tuesday, plus out-of-band | Restarts; 35-day cap on an Intune pause |
| macOS | No fixed day; three macOS lines patched on 9 Nov 2026 | Several supported major versions at once |
| Linux servers | Per-distribution errata; daily unattended runs on Ubuntu | Kernel and library restarts |
| Network devices and firmware | Cisco bundles twice a year per product line; Fortinet second Tuesday | Software train and image upgrade |
| Browsers and third-party apps | Chrome stable update on 17 Nov 2026; Extended Stable every 8 weeks | Inventory of what is installed |
| Containers and images | Kubernetes monthly patch releases | Rebuild and redeploy, not patch in place |
| Cloud virtual machines | Follows the operating system vendor | Shared responsibility and orchestration |
| Databases | Oracle four dates a year; PostgreSQL at least every three months | Application compatibility |
| Mobile devices | Android first Monday; Apple unscheduled | Manufacturer and carrier delivery |
| OT and medical devices | Vendor-specific; CISA publishes advisories | Planned outages; certification |
| Systems that cannot reboot | Hotpatch baselines every three months; live kernel patches | Live patch coverage limits |
How to use these pages with the rest of the site
The class pages give the supply side: what the vendor ships and when. The demand side, the number of days a framework allows, is on the patch window table, and the clause that connects them is severity and patch windows. The steps that apply to every class are on the process page.
Sources
Last reviewed 19 Nov 2026