Patch Management Policy

HIPAA patch management policy

The HIPAA Security Rule in force sets no patch deadline. The proposal published 6 January 2025 (90 FR 898) would require 15 calendar days for critical risk and 30 for high risk, with documented exceptions. No final rule was found on 19 Nov 2026, so this variant writes both, side by side.

HIPAA variant: paste over the same-numbered sections of the general policy

1 Purpose and scope

1.1 This policy applies to every electronic information system of [Company name] that creates, receives, maintains or transmits electronic protected health information, and to every system that connects to one. [Company name] is a [covered entity / business associate].

1.2 The policy is part of the security measures required by 45 CFR 164.308(a)(1)(ii)(B), chosen on the basis of the risk analysis required by 164.308(a)(1)(ii)(A) dated [date].

4 Severity and patch windows

4.1 Risk level (critical, high, other) is assigned by the policy owner from the current risk analysis and recorded for each vulnerability.

4.2 Patch windows

Windows, from the date [Company name] identifies the need to patch, where a patch is available

SeverityWindow3143090180 days
Critical14 calendar days (company standard)Window if the proposed federal rule is finalized as written: 15 calendar days
High30 calendar days (company standard)Window if the proposed federal rule is finalized as written: 30 calendar days
All otherAs set in the general policyWindow if the proposed federal rule is finalized as written: As set in this policy

Windows as this template sets them, on the same 0 to 180 day scale as the builder.

4.3 Where no patch is available, the 15 and 30 days run from the date a patch becomes available, and Annex A applies meanwhile.

4.4 The company standard is stricter than or equal to every figure in the proposal, so adopting it now means no change when the rule is final.

9 Review and approval

9.1 This policy is reviewed and tested at least once every 12 months, and after any significant change to systems that hold ePHI.

9.2 Test means: [tabletop walk-through of one critical and one high case; evidence kept for each].

Annex A Exceptions (HIPAA)

A.1 An exception is valid only if (a) no patch is available, or (b) the only available patch would adversely affect the confidentiality, integrity or availability of ePHI.

A.2 Each exception records the compensating controls applied, the risk analysis entry, the approver and the date for the next check.

What the rule in force says

The eCFR text of 45 CFR 164.308 (latest amendment 30 December 2016; eCFR current as of 17 November 2026) requires, at (a)(1)(ii)(B), security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level. Its risk analysis duty at (a)(1)(ii)(A) is an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of ePHI. Protection from malicious software, (a)(5)(ii)(B), is addressable and reads procedures for guarding against, detecting and reporting malicious software. The text read does not use the word patch and sets no number of days. Source.

A policy written today therefore answers to the risk analysis: the policy's windows are justified there. The template ties the windows to the analysis in clause 1.2.

What the proposal would add

Proposed text from 90 FR 898, published 6 January 2025, read 19 Nov 2026 on federalregister.gov. Proposal only.
Proposed clauseText readMeaning for the policy
164.308(a)(4)(ii)(C)(1)Within 15 calendar days of identifying the need to patch, update, or upgrade ... to address a critical risk ... where a patch, update, or upgrade is availableWindow for critical risk; clock starts at identification
164.308(a)(4)(ii)(C)(2)Within 30 calendar days ... to address a high risk ... where a patch, update, or upgrade is availableWindow for high risk
164.308(a)(4)(ii)(C)(3)As determined by and documented in the ... policies and procedures ... for all other patchesNo number; your own policy sets it
164.308(a)(4)(ii)(D)(1) no patch is available to address a risk identified in the risk analysis; (2) the only available patch would adversely affect the confidentiality, integrity, or availability of ePHIThe two grounds for an exception
164.308(a)(4)(ii)(B)Review and test written policies and procedures at least once every 12 monthsAnnual review and test

The comment period closed on 7 March 2025 (Federal Register API). A search of the Federal Register API for documents published from 7 January 2025 to 19 November 2026 returned 23 hits, none of them a Security Rule final rule, so the proposal reads as not in force on this check. HHS pages returned HTTP 403 and the Unified Agenda was not read; confirm status before relying on this.

Notes on the drafting

Clause 4.2 puts company-standard windows (14 and 30) inside the proposal's 15 and 30 days, an arrangement that costs nothing to adopt early. The proposal also expects compensating controls for exceptions under its (E) and (F) paragraphs, which the exceptions clause carries as a required field. Everything else in the general policy applies. Dates to watch are on the dates to know page and the HIPAA row of the window table.

Sources

Last reviewed 19 Nov 2026