HIPAA patch management requirements
The HIPAA Security Rule now in force sets no patch deadline. The proposed rule published 6 Jan 2025 (90 FR 898) would require patching within 15 calendar days for critical risk and 30 for high risk. A Federal Register search on 19 Nov 2026 found no final rule, so the proposal is not in force.
4.3 Patch windows
HIPAA Security Rule (in force); HIPAA Security Rule NPRM (proposed, not in force)
| Severity | Window3143090180 days | Clock starts | Set by |
|---|---|---|---|
| All severities (HIPAA (current rule)) | no number set | Default | |
| Critical (HIPAA (proposed rule)) | 15 calendar days (proposed) | Identifying the need to patch | HIPAA Security Rule NPRM (proposed, not in force), proposed 164.308(a)(4)(ii)(C)(1) |
| High (HIPAA (proposed rule)) | 30 calendar days (proposed) | Identifying the need to patch | HIPAA Security Rule NPRM (proposed, not in force), proposed 164.308(a)(4)(ii)(C)(2) |
Rows marked Default keep the site template's suggested window; their clock starts as this section states.
Framework clauses, read 19 Nov 2026:
- HIPAA Security Rule (in force): 164.308(a)(1)(ii)(B): no number set; 164.308(a)(1)(ii)(A): no number set
- HIPAA Security Rule NPRM (proposed, not in force): Proposed 164.308(a)(4)(ii)(C)(1): 15 calendar days (proposed); Proposed 164.308(a)(4)(ii)(C)(2): 30 calendar days (proposed)
164.308(a)(1)(ii)
What is in force
The eCFR text of 45 CFR 164.308, whose latest amendment is dated 30 Dec 2016, does not use the word patch in the text read. Two clauses carry the weight. The risk analysis clause, 164.308(a)(1)(ii)(A), calls for "an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information." The risk management clause, 164.308(a)(1)(ii)(B), calls for "security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level."
Malware protection, 164.308(a)(5)(ii)(B), is an addressable specification reading "Procedures for guarding against, detecting, and reporting malicious software." Neither clause names a number of days, so a covered entity's own written window, justified by its risk analysis, is what an investigator would read.
164.308(a)(4)(ii)to policy 4.3
What the proposal would add
The notice of proposed rulemaking, published 6 Jan 2025 as 90 FR 898 (document 2024-30983, comments closed 7 Mar 2025), proposes a new patch management standard at 164.308(a)(4). It would require written policies and procedures "for identifying, prioritizing, acquiring, installing, evaluating, and verifying the timely installation of patches, updates, and upgrades," reviewed and tested at least once every 12 months.
| Proposed paragraph | Window | Condition |
|---|---|---|
| 164.308(a)(4)(ii)(C)(1) | 15 calendar days | Critical risk, counted from identifying the need to patch; where no patch is available, from when one becomes available |
| 164.308(a)(4)(ii)(C)(2) | 30 calendar days | High risk, same counting rule |
| 164.308(a)(4)(ii)(C)(3) | As documented in the entity's own policy | All other patches, updates and upgrades |
| 164.308(a)(4)(ii)(B) | 12 months | Review and test of the written policies and procedures |
The proposal bases the windows on the entity's own risk analysis, its vulnerability scans, monitoring of authoritative sources and penetration tests, "within a reasonable and appropriate period of time." The clock therefore starts at the entity's identification, not at vendor release, which differs from UK Cyber Essentials' 14 days from release.
The proposed exceptions
Two exceptions would apply, each only if documented: no patch, update or upgrade is available to address a risk found in the risk analysis, or the only available one "would adversely affect the confidentiality, integrity, or availability of electronic protected health information." Where an exception applies, the entity "must document in real-time" the exception and implement reasonable and appropriate compensating controls until a patch that does not cause that harm becomes available. The clause text is policy content only here; how to decide whether to accept a risk sits outside this site.
Status check: a Federal Register API search of documents published from 7 Jan 2025 to 19 Nov 2026 returned 23 hits, none a final Security Rule. The HHS fact sheet returned HTTP 403 and the Unified Agenda entry was not read, so "not final" rests on that search alone.
What a policy must write
- Today: a written patch window per risk level that follows from the risk analysis, with the analysis dated and tied to the window. No number is dictated.
- If preparing for the proposal: a 15 day window for critical risk and 30 days for high risk, counted from identifying the need to patch, and a documented rule for everything below.
- An annual review and test of the patch policy, with the test result recorded.
- A written exception step with real-time documentation, a named reason from the two permitted, and the compensating controls in place until the patch can be applied.
Evidence
Under the proposal, the entity would have to produce the written policies, the record of the 12 month review and test, and for each exception the real-time documentation and the compensating controls. The health-care template at HIPAA patch management policy carries the in-force wording and flags the proposed numbers separately. Row-level timing is in the Patch Window Table, and the proposal's dates are in dates to know.
Sources
- eCFR, 45 CFR 164.308 (current), read 19 Nov 2026
- Federal Register, HIPAA Security Rule to Strengthen the Cybersecurity of ePHI, 90 FR 898, read 19 Nov 2026
- Federal Register API, document 2024-30983 (dates), read 19 Nov 2026
- Federal Register API, status search 7 Jan 2025 to 19 Nov 2026, read 19 Nov 2026
Last reviewed 19 Nov 2026