Key takeaways
- HHS proposed a major Security Rule update on January 6, 2025; it is still a proposal, and the latest federal agenda lists final action for July 2027.
- The current Security Rule stays fully in force until a final rule replaces it.
- The proposal would end the option to skip addressable safeguards, expressly require encryption with limited exceptions, and require multi-factor authentication, an asset inventory and a network map.
- Most of the proposed measures are already good practice, so preparing now lowers risk whatever the final rule says.
Where the proposal stands
The HHS Office for Civil Rights published its proposed rule to strengthen the cybersecurity of electronic protected health information in the Federal Register on January 6, 2025, and the comment period closed on March 7, 2025[1]. It would be the most significant change to the Security Rule since the rule was first written.
As of this writing it has not been finalized. The federal regulatory agenda now lists the rulemaking under long-term actions, with final action projected for July 2027[2]. Agenda dates are planning estimates, not commitments, and they have moved before. A final rule could look different from the proposal, could arrive later, or could be narrowed.
Nothing about the proposal pauses the current rule. Your practice must keep meeting today's Security Rule requirements, including risk analysis and safeguards, and enforcement continues under it.
What the proposal would change
The proposal is long, and much of it restates or clarifies duties that already exist. For a medical or dental practice, five changes matter most.
- No more skipping addressable safeguards. Today, many safeguards are labelled addressable, and a practice may document why an alternative is reasonable. The proposal relies on a recommendation to eliminate from addressable specifications the choice not to implement, and HHS states that compliance with them is not, and should not be, optional[1].
- Encryption by default. HHS says it wants regulated entities to understand their obligation to have encryption mechanisms in place and deployed throughout the organization, and the proposal would expressly require encryption, with limited exceptions[1].
- Multi-factor authentication. The proposal would require verification of at least two of three categories of factors: something you know, something you have and something you are[1].
- A technology asset inventory and a network map. Practices would have to inventory their technology assets and create a map of how electronic patient information moves through their systems[1].
- Checking on vendors. A new requirement would have practices verify that business associates have deployed the required technical safeguards, rather than relying on the agreement alone[1].
The proposal also adds more specific expectations for testing, vulnerability management and recovery planning. If you are budgeting for next year, read the summary of proposed changes in the Federal Register notice, or ask your IT partner to map it against what you already do.
Today's rule next to the proposal
| Safeguard | Current Security Rule | Proposed rule |
|---|---|---|
| Unique user identification | Required | Still required |
| Encryption of stored information | Addressable: implement or document a reasonable alternative | Expressly required, with limited exceptions |
| Encryption in transit | Addressable, whenever deemed appropriate | Expressly required, with limited exceptions |
| Automatic logoff | Addressable | No longer optional if the addressable choice is removed |
| Authentication | Verify that a user is who they claim to be; method not specified | Multi-factor: two of three factor categories |
| Asset inventory and network map | Implied by an accurate risk analysis | Explicit written requirement |
| Business associate safeguards | Satisfactory assurance in a written agreement | Agreement plus verification of technical safeguards |
Under the current rule, unique user identification is required, automatic logoff and encryption are addressable, and person or entity authentication requires only that you verify a user is who they claim to be[3]. The shift in the proposal is less about inventing new safeguards and more about removing flexibility that many small practices have used to delay them.
Why it reaches every practice
The Security Rule covers electronic patient information, and almost every practice now holds it. In 2024, 91% of office-based physicians used a certified EHR and another 4% used a non-certified system[4]. A rule written with large-scale cyberattacks in mind will also land on the two-physician practice with a cloud EHR, a shared front desk computer and a fax server.
- Certified EHR 91%
- Non-certified EHR 4%
- No EHR reported (remainder) 5%
Source: Office of the National Coordinator for Health IT (ASTP/ONC), HHS, 2024[4]
Show the data
| Item | Value |
|---|---|
| Certified EHR | 91% |
| Non-certified EHR | 4% |
| No EHR reported (remainder) | 5% |
That is also why the current rule's penalties matter while you wait. Civil money penalties for HIPAA violations are capped at $2,190,294 per calendar year for violations of an identical provision, after inflation adjustment[5]. A practice that has already done the work the proposal describes is in a much better position under either rule.
What it would feel like at the front desk
Security rules are usually discussed as IT projects, but front office staff would notice several of these changes first. Multi-factor sign-in means a second step when logging in to the EHR, email or the phone system's admin screen, which can slow a busy check-in line if it is set up badly. Shared logins, still common at front desks, would be very hard to defend. Every workstation would need encryption and an automatic lock, including the old computer that only runs the label printer.
Plan the rollout around the people who will feel it. Choose authentication methods that work quickly, such as tap badges or authenticator apps with push approval, and test them during a quiet afternoon rather than on a Monday morning. Give each person their own login before you switch on any lockout rules. Explain why: a short huddle on the phishing and ransomware attacks that these measures are designed to stop does more for adoption than a policy memo.
A preparation plan for the next two quarters
Build the inventory and map
List every device, application and service that stores or touches patient information, then sketch how data moves between them: check-in, EHR, billing, portal, fax, referrals, backups. Keep it to one page if you can.
Turn on multi-factor sign-in
Start with email, the EHR, remote access and any admin accounts. Use an authenticator app or hardware key rather than text messages where your systems allow it.
Close encryption gaps
Confirm full-disk encryption on every laptop and desktop, encrypted backups, and encrypted connections for portals, email and remote access.
Revisit every addressable decision
For each safeguard you chose not to implement, write down why. If the honest answer is cost or habit, put it on the plan.
Ask vendors for evidence
Ask your EHR, phone, texting and IT vendors for a short written description of their safeguards, such as encryption and multi-factor sign-in, and keep the replies with their agreements.
Refresh the risk analysis
Update your security risk analysis with the new inventory and decisions, and keep the documentation for at least six years[6].
Questions to ask your IT partner now
- Which of our systems already support multi-factor sign-in, and which would need an upgrade or replacement?
- Is every laptop, desktop and backup encrypted today, and how would we prove it?
- Do we have a current list of every device and service that touches patient information?
- Could we draw a simple map of how patient data moves between our systems this month?
- How long would it take to restore the EHR, scheduling and phones from backup, and when did we last test it?
- Which vendors could give us a written description of their safeguards if we asked?
The answers become your gap list. Some items will cost nothing but time, others may need budget next year, and a few may depend on vendors. Sorting them now means a final rule, whenever it arrives, becomes a scheduling question rather than an emergency.
What to watch for next
- The regulatory agenda entry for the rule, which shows the projected timing and stage.
- Any final rule in the Federal Register, which will set an effective date and a compliance date, usually some months apart.
- Guidance or recognized security practices published by HHS alongside a final rule.
- Your EHR and IT vendors' plans for supporting new requirements, especially multi-factor sign-in and audit features.
When a final rule appears, read the compliance date carefully before you panic or relax. Final rules typically give regulated entities time to comply after the effective date. If you have already worked through the plan above, most of that time will go into documentation rather than new projects.
Example: one quarter of preparation
Example (fictional): A three-provider pediatric practice decides not to wait for the final rule. In the first month, the office manager and the IT contractor build a one-page inventory and network map, and find a forgotten fax server and a laptop without disk encryption. In the second month, they switch on multi-factor sign-in for email and the EHR and encrypt the laptop.
In the third month, they ask five vendors for written safeguard summaries and get four back; the fifth is flagged for review at renewal. The manager updates the risk analysis, records each change with the date, and notes the remaining work as planned items with owners. Whatever the final rule says, the practice is less exposed than it was three months earlier.
Frequently asked questions
Is the new HIPAA Security Rule in effect?
No. It was proposed in January 2025 and has not been finalized. The current Security Rule remains in force and enforceable.
When will the final rule come out?
The federal regulatory agenda currently projects final action for July 2027, listed as a long-term action. Those dates are estimates and can change.
Will small practices be exempt?
Do not count on it. The proposal includes a discussion of small and rural health care providers, but any special treatment would have to appear in the final rule, so check the final text when it is published.
Should we start now or wait?
Start with the measures that are good practice anyway, such as multi-factor sign-in, encryption and an asset inventory. They reduce real risk under the current rule as well.
References
HHS Office for Civil Rights (Federal Register via GovInfo) (2025). HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information (proposed rule, 90 FR 898) (opens in a new tab) ↑
Office of Information and Regulatory Affairs (Reginfo.gov) (2025). Unified Agenda: HIPAA Security Rule to Strengthen the Cybersecurity of Electronic Protected Health Information (RIN 0945-AA22) (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.312 - Technical safeguards (opens in a new tab) ↑
Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Office-based Physician Electronic Health Record Adoption, 2008-2024 (ONC Data Brief) (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 102.3 - Penalty adjustment and table (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.530 - Administrative requirements (opens in a new tab) ↑