Patch Management Policy

Patch management process improvement

Review the patch cycle on a stated schedule: exceptions regularly, alternatives to patching periodically, deadlines yearly. CISA reassesses BOD 26-04 Table 1 once per fiscal year, and the HIPAA Security Rule proposal of 6 Jan 2025 would require testing the patch policy at least every 12 months. Read 19 Nov 2026.

What NIST asks to be reviewed

NIST SP 800-40 Rev. 4 names three reviews. Exceptions: “all exceptions to maintenance plans should be reviewed regularly to determine if the maintenance plan can be implemented now,” and assets with similar long-term exceptions might need a separate maintenance group. Alternatives to patching for unpatchable assets: reevaluate periodically through a risk assessment and a cost-benefit analysis of mitigating, transferring or accepting the risk. Metrics: improve the low-level data so enterprise measures can be trusted (sections 3.5.4, 3.5.5 and 3.6). The inputs are the reports from step 8.

Cycle lengths taken from published texts

Sources: CISA, Federal Register, CIS Controls v8 PDF, read 19 Nov 2026. See the HIPAA and CIS pages.
SourceWhat is reviewedStated intervalStatus on 19 Nov 2026
CISA BOD 26-04Table 1 remediation timelines, in a data-driven reassessmentOnce per fiscal yearIn force for federal civilian agencies
HIPAA Security Rule NPRM, 90 FR 898, proposed 164.308(a)(4)(ii)(B)Review and test written patch policies and proceduresAt least once every 12 monthsProposed 6 Jan 2025; no final rule found in the text read
CIS Controls v8, safeguard 7.2The remediation strategyMonthly or more frequentControl text from the August 2023 guide; v8.1 wording not read
CIS Controls v8, safeguard 7.1Documentation of the vulnerability management processAnnuallySame source and limit

Triggers outside the calendar

Some events should force a review before the date. A vendor that publishes outside its schedule, as Cisco and Fortinet say they may for actively exploited flaws, can make a calendar-based window stale. An end-of-support date can leave a group with no patches at all: Microsoft states that SQL Server extended support “includes only security updates,” and that after it ends Microsoft no longer provides servicing. When either happens, move the affected assets to the unpatchable maintenance group and set the mitigations NIST describes in section 3.5.4.

The record to keep

  • The review date, attendees by role, and the decisions, each with an owner and a due date.
  • The set of exceptions reviewed and their outcomes: closed, renewed with a new expiry, or moved to another group.
  • Policy changes that followed, with version numbers, so the review and approval section can point at them.

Sources

Last reviewed 19 Nov 2026