regulation
HIPAA Security Rule Update 2026: Status Tracker and Readiness Checklist
By Art Kukharenko · Published · Updated
Independent legal reviewer not yet supplied. General information; confirm current obligations with qualified counsel.
Browse regulation resourcesThe HIPAA Security Rule overhaul proposed in January 2025 is not final as of 17 October 2026. HHS's regulatory agenda lists a final action for July 2027 under "Long-Term Actions"; under the proposal, compliance would fall 180 days after the rule's effective date, which is itself 60 days after publication. It would make encryption, multi-factor authentication (MFA), asset inventories and annual audits mandatory. Use the status table and checklist below.
Who this is for: security and privacy leads who run customer data platform (CDP), email, analytics and tag systems that touch electronic PHI (ePHI). Part of the regulation hub.
Status table
Scroll horizontally to compare all columns ↔
| Milestone | Date | Source |
|---|---|---|
| HHS OCR announces the proposed rule | 27 Dec 2024 | HIPAA Journal 1 |
| Notice of proposed rulemaking published, 90 FR 898 (RIN 0945-AA22) | 6 Jan 2025 | Federal Register 2 |
| Tribal consultation meeting | 6 Feb 2025 | Federal Register 2 |
| Comment period closes | 7 Mar 2025 | Federal Register 23 |
| Comments received | More than 4,700 | HIPAA Journal, citing OCR's director 1 |
| Coalition of 100+ hospital systems and provider associations asks HHS to withdraw the proposal | 2025 to 2026 (date not given) | HIPAA Journal 1 |
| Unified Agenda entry (pubId 202510, shown as "2026" on reginfo.gov): stage "Long-Term Actions", final action "07/00/2027" | Fall 2025 edition | reginfo.gov 4 |
| OCR's earlier final-rule target (May 2026) moved to July 2027 | By Oct 2026 | HIPAA Journal 5 |
| Status: no final rule; the administration has not decided whether to finalize | 6 Oct 2026 | HIPAA Journal 5 |
| Proposed timing if a final rule is published: effective 60 days later; compliance 180 days after that (about 240 days after publication) | Not before final rule | Federal Register 2 |
The July 2027 date is an agenda target, not a commitment.
What the proposed rule would require
The notice would rewrite the Security Rule's text (45 CFR 164.304 to 164.318). The main proposals, from the proposed regulatory text 2:
Scroll horizontally to compare all columns ↔
| Area | Proposed requirement | Proposed section |
|---|---|---|
| Addressable vs required | Remove the distinction; every implementation specification is required, with limited exceptions | 164.306(c) |
| Asset inventory and network map | Written inventory of technology assets (identification, version, accountable person, location) and a network map of how ePHI moves; update at least every 12 months and on changes | 164.308(a)(1) |
| Risk analysis | Written assessment with listed elements, including risk from business associates; review at least every 12 months | 164.308(a)(2) |
| Patching | Critical-risk patches within 15 calendar days, high-risk within 30 | 164.308(a)(4) |
| Multi-factor authentication | MFA on all technology assets in relevant systems; exceptions for unsupported assets (with a migration plan), emergencies and certain FDA-authorized devices | 164.312(f) |
| Encryption | Encrypt all ePHI at rest and in transit, with documented exceptions | 164.312(b) |
| Vulnerability scanning and penetration testing | Automated scans at least every six months (or per risk analysis); penetration test by a qualified person at least every 12 months | 164.312(h) |
| Restoration and backups | Procedures to restore critical systems and data within 72 hours; backups no more than 48 hours old; test restorations at least monthly | 164.308(a)(13); 164.312(i) |
| Annual compliance audit | Documented audit of each standard at least every 12 months | 164.308(a)(14) |
| Business associates | Annual written verification and certification of technical safeguards; business associate must report contingency-plan activation within 24 hours | 164.308(b)(2); 164.314(a)(2)(i)(D) |
| Workforce access | Terminate access within one hour of employment ending; notify other entities within 24 hours of a change | 164.308(a)(9) |
HHS says most of these codify what a thorough risk analysis already implies, such as inventorying assets and mapping ePHI movement, and that it would apply the standard 180-day compliance period 2. It estimates first-year costs of about $9 billion and about $6 billion a year in years two to five 2.
What provider groups objected to
According to HIPAA Journal, a coalition of more than 100 hospital systems and provider associations urged HHS to withdraw the proposal, citing substantial new financial burdens, an unreasonable implementation timeline, and a conflict with the administration's deregulatory agenda; the group asked instead for a collaborative effort to develop practical standards 1. A later HIPAA Journal item says critics also raised reduced flexibility for technical safeguards and the difficulty small organizations would have meeting an eight-month (240-day) timeframe, and that a CHIME-led coalition petitioned for withdrawal 5. HHS's own notice asked whether removing the addressable distinction would have unintended negative consequences 2. We found no primary text of the coalition letters; treat these descriptions as secondary.
Likely timeline
Scroll horizontally to compare all columns ↔
| Scenario | What it would mean | Illustrative dates |
|---|---|---|
| Final rule meets the agenda target | Final rule in July 2027; effective 60 days after publication; compliance 180 days later | Published 1 Jul 2027: effective 30 Aug 2027; compliance 26 Feb 2028 |
| Rule is narrowed or phased | Longer or tiered compliance periods; some mandates relaxed | Unknown |
| Rule is withdrawn or slips again | Current Security Rule stays; OCR relies on risk-analysis enforcement | Unknown |
The dates in the first row follow the NPRM's own periods and are arithmetic, not a forecast 2. Plan to the proposal's content, not to a date.
HIPAA Security Rule 2026 readiness checklist for customer data platform (CDP) and martech systems
You can do most of this under the current rule, which already requires an accurate and thorough risk analysis 2. The column on the right shows where it lands in a customer data platform (CDP) or marketing stack.
Scroll horizontally to compare all columns ↔
| Proposed area | Do now | In your CDP or martech stack |
|---|---|---|
| Asset inventory and network map | List every system that stores or can reach ePHI; draw ePHI flows | CDP, email and SMS platforms, tag manager, analytics, call tracking, warehouse, SDKs and pixels, plus each destination |
| MFA | Enforce MFA or SSO everywhere; document exceptions | Admin consoles of the CDP, ESP, tag manager and cloud account; rotate API keys and service tokens |
| Encryption | Encrypt at rest and in transit; plan for key custody | Databases, object storage, backups, queues, TLS to every destination |
| Patching and scanning | Set 15-day (critical) and 30-day (high) targets; scan every six months; test annually | Self-hosted CDP nodes, container images, tag-manager containers, public APIs |
| 72-hour restoration | Write the runbook; test restore of identity graph, consent state and audiences | Backups no older than 48 hours; monthly test restores |
| Annual audit | Map controls to each standard; keep evidence | Export access, change and activation logs to the audit store |
| Business associates | Collect annual written verification; add a 24-hour contingency notice clause | Vendor register; see the BAA checklist and the vendor-by-vendor BAA answers |
| Offboarding | Deprovision within one hour of departure | SCIM from the identity provider to each marketing tool |
Security is separate from marketing permission: see HIPAA marketing rules for authorization, and HIPAA-compliant customer data platforms for buying criteria. A customer-owned PrivyCDP deployment (on-premise, private cloud or VPC) places these controls under the provider's own management; see the HIPAA-ready page.
Track every date in one place with the regulatory deadline tracker, and return to the regulation hub for related guides.
Frequently asked questions
Has the HIPAA Security Rule update been finalized?
Was the HIPAA Security Rule update postponed?
What is the HIPAA Security Rule final rule 2027 date?
Would MFA and encryption become mandatory?
Under the proposal, yes. MFA would be required on all technology assets in relevant systems, and all ePHI would have to be encrypted at rest and in transit, with documented exceptions such as assets that cannot support them 2. Today encryption is an addressable specification that must be assessed and implemented if reasonable and appropriate 2.
What does removing "addressable" mean?
Today, covered entities assess addressable specifications and may document an alternative. The proposal would remove that distinction so every implementation specification is required, with specific, limited exceptions 2. HHS says this would clarify the floor of protection while keeping some scalability 2.
Who would be affected besides hospitals?
Covered entities and business associates, which include vendors that create, receive, maintain or transmit ePHI on a covered entity's behalf. The proposal would add annual written verification of business associates' technical safeguards and a 24-hour notice when a business associate activates its contingency plan 2. Marketing and customer-data vendors that hold ePHI would be included.
How much would the proposed rule cost?
HHS estimates first-year costs of about $9 billion across regulated entities and health plan sponsors, and about $6 billion a year in years two through five. The notice reports annualized costs of $6.8 billion at a 2 percent discount rate, so the compliance burden is a central point in the objections 2.
Sources
- HIPAA Journal, "Final Rule Implementing HIPAA Security Rule Updates Edges Closer" (20 Mar 2026, updated July 2026) Open source
- HHS, HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, 90 FR 898 (6 Jan 2025): (full text read at Open source · Additional source
- Federal Register API record for document 2024-30983 (comment close 2025-03-07) Open source
- reginfo.gov Unified Agenda, RIN 0945-AA22 Open source
- HIPAA Journal, HIPAA updates and changes (6 Oct 2026) Open source
Put this evaluation into practice.
Assess your deployment requirementsThis article is general information, not legal advice.
Further reading
- Customer data regulation guides
- HIPAA-Compliant CDP: What It Takes
- HIPAA architecture
- Regulatory deadline tracker
- HIPAA Marketing Rules: Authorization
Published: · Updated:
Publication date recorded for the approved release. Editorial updates do not establish legal approval or a customer result.