Patch Management Policy

Patch management policy review

Review a patch policy at least every 12 months, the cadence in the HIPAA Security Rule proposal and in CIS safeguard 7.1, and sooner when a framework changes: CISA BOD 26-04 took effect 10 June 2026, FedRAMP's rules become mandatory on 7 December 2026. Approval names a role, a date and a version.

What the section must say

  • The review interval, and the events that trigger an earlier review.
  • Who approves changes: a role, not a person.
  • Where the approved version, its date and its approver are recorded.
  • Who tests the policy, and how, if a framework requires testing.

The HIPAA Security Rule proposal (90 FR 898, proposed 164.308(a)(4)(ii)(B)) would require reviewing and testing written patch policies and procedures at least once every 12 months. CIS Controls v8 safeguard 7.1 asks to review and update the vulnerability management documentation annually, or when significant enterprise changes occur. Safeguard 7.2 adds monthly or more frequent reviews of the remediation strategy.

Events that force an earlier revision, with dates

Dates as read on 19 Nov 2026; the 7 Dec computation is arithmetic from the BOD page's phase wording, not a statement on the page.
DateEventEffect on a policy
27 Apr 2026Cyber Essentials Requirements v3.3 effectiveKeeps the 14 day rule for critical or high updates; check the scope list
10 Jun 2026CISA BOD 26-04 issued; revokes BOD 19-02 and BOD 22-01Remove any citation of 15, 30 day or 2 week and 6 month rules as current
24 Jun 2026FedRAMP Consolidated Rules for 2026 launchedReplace legacy references in FedRAMP-bound policies
7 Dec 2026 (upcoming)FedRAMP VDR rules mandatory; grace period to 7 Mar 2027Revise before this date if you hold or seek certification
7 Dec 2026 (computed)180 days after BOD 26-04 issue, the end of its stated Phase IIIFederal agencies only; Phase I was immediate, Phase II within 60 days
Each fiscal yearCISA reassesses BOD 26-04 Table 1Re-read the Table if your windows copy it

The fiscal-year reassessment is why a policy that copies a BOD table should cite the issue date and carry a re-read reminder; the dates to know page tracks the others.

Sample wording

9.1 This policy is reviewed and tested at least every 12 months, and within [30] days of any of these events: a change to the timing of a framework named in section 4; a significant change to the estate; a missed class 1 window.

9.2 [Role] approves changes. Each approved version records its number, date, approver and a list of changes.

9.3 The policy's test is [a tabletop of one class 1 and one class 2 case]. The record of the test is kept with the policy.

Common mistakes

  • Review date left blank. The cover line needs a date no later than 12 months ahead.
  • Review without test. The HIPAA proposal says review and test.
  • No trigger for external change. The table shows five dated changes in 2026 alone.

Return to the policy sections, or see the table of what each framework sets in severity and patch windows.

Sources

Last reviewed 19 Nov 2026