More than 167 million individuals were affected by large health data breaches in 2023, according to HHS. A single 2024 attack on Change Healthcare exposed records for roughly 190 million people. Electronic health information has become both essential to care and a prime criminal target.
That pressure produced the biggest proposed rewrite of the HIPAA Security Rule in 20 years. A distinction is critical for anyone searching HIPAA Security Rule 2026: the current rule remains in effect, and the cybersecurity overhaul is still a proposal.
The Most Important Point
Current rule: The existing HIPAA Security Rule remains operative and enforceable.
Proposed changes: HHS announced a Security Rule notice of proposed rulemaking (NPRM) on December 27, 2024, and the Federal Register published it on January 6, 2025. The comment period closed March 7, 2025, with about 4,745 comments.
Status as of October 2026: No final rule exists. HHS’s regulatory agenda now lists July 2027 for final action, after an earlier target of May 2026 passed. Dates on the agenda are not binding. The proposal could be finalized, modified, delayed, or withdrawn, and more than 100 hospital and provider groups have asked HHS to withdraw it.
Treat every item below under “proposed” as non-binding until the Federal Register says otherwise.
Why HHS Proposed an Overhaul
HHS cited rapid growth in hacking and ransomware. It reported that between 2018 and 2023, large breaches attributed to hacking rose 102 percent and ransomware attacks rose 264 percent. The existing rule dates from 2003, with updates in 2013, and it was written for a world of fewer connected systems.
Another issue is flexibility. The current rule labels many specifications “addressable,” including encryption, which organizations can address through alternative measures after documenting a reason. OCR leadership has noted that this flexibility sometimes became discretion to skip controls.
The Proposed Changes at a Glance
| Proposed area | What organizations may need to do | Operational implication |
|---|---|---|
| Required vs. addressable | End the distinction; most specifications become required | Fewer exceptions |
| Risk analysis | Written, regularly reviewed, with asset inventory and network map | Stronger governance |
| Encryption | Encrypt ePHI at rest and in transit, with limited exceptions | Infrastructure changes |
| Multi-factor authentication | Required for many access points | Login redesign |
| Security testing | Vulnerability scans at least every six months, annual penetration tests | More cybersecurity workload |
| Incident response | Written plans, restore critical systems within 72 hours | Faster recovery |
| Business associates | Annual written verification of safeguards, 24-hour notice of contingency plan activation | Vendor oversight |
| Compliance audits | Annual audits | Documentation burden |
If finalized, HHS proposed a window of roughly 240 days between publication and compliance. These details come from the NPRM and could change.
The Current Rule in Plain English
The Security Rule protects electronic protected health information (ePHI). HHS describes its goals as confidentiality, integrity, and availability: only authorized people see data, data stays accurate, and data is accessible when needed.
Administrative safeguards
These cover risk analysis, risk management, workforce training, sanctions, contingency plans, and assigned security responsibility. The risk analysis is the most frequently cited weakness in OCR enforcement.
Physical safeguards
These protect facilities and equipment: access controls to server rooms, workstation security, and device and media disposal.
Technical safeguards
These include access controls, audit logs, integrity controls, authentication, and transmission security.
What to Audit Regardless of the Final Rule
OCR has already emphasized risk analysis failures, missing multi-factor authentication, and asset inventory gaps in enforcement. A sensible checklist therefore applies today.
- Enterprise-wide risk analysis, updated regularly
- Access controls and least-privilege permissions
- Multi-factor authentication
- Tested backups, including offline copies
- Incident response plan with tabletop exercises
- Vendor risk reviews
- Workforce phishing training
- Encryption of laptops, mobile devices, and data in transit
- System monitoring and log review
- Disaster recovery with recovery time targets
What Each Audit Item Means
The audit checklist is useful when each item is understood.
Enterprise-wide risk analysis. This is a documented review of where ePHI lives, what threatens it, and how likely and damaging each threat is. It is the foundation of the Security Rule and the item OCR cites most often in enforcement. A real analysis covers every system, including laptops, cloud tools, and medical devices.
Access controls. Staff should only reach the data their job requires. Least privilege limits damage when an account is compromised, and regular reviews remove access for people who changed roles.
Multi-factor authentication. A stolen password alone should not open the EHR, email, or remote access. Many ransomware incidents begin with stolen credentials, so MFA blocks a common path.
Tested backups. Backups only matter if they can be restored. At least one copy should be offline or immutable so ransomware cannot encrypt it.
Incident response plan. A written plan names who decides, who calls the lawyer and insurer, and how care continues on paper. Tabletop exercises reveal gaps before a real attack.
Vendor risk reviews. A practice is responsible for what its vendors do with data. Reviews should cover security controls, breach notification terms, and subcontractors.
Workforce training. Phishing is the most common entry point, and short, frequent training works better than a yearly lecture.
Encryption. Encrypting laptops, phones, and data in transit means a lost device does not become a reportable breach in many cases.
System monitoring. Logs and alerts help detect unusual access, such as a user opening thousands of records at night.
Disaster recovery. Recovery time goals tell leaders how long they can operate without a system and what to restore first.
Business Associates Are a Critical Weak Point
Cloud hosts, billing companies, laboratories, software vendors, and clearinghouses all handle ePHI. A breach at one vendor can affect hundreds of provider clients. The Change Healthcare incident showed how a single clearinghouse failure disrupted claims and payments nationwide.
Covered entities need business associate agreements with clear security duties, plus technical verification. A signed contract alone does not prove a vendor is secure.
Why Ransomware Changes the Conversation
Many people associate HIPAA with privacy. Ransomware highlights availability. When systems are encrypted, clinicians may lose access to records, imaging, and medication orders. Hospitals have diverted ambulances and canceled procedures, even when no patient data is proven stolen.
That is why proposed requirements around backup, restoration, and recovery time matter. Protecting access to data can protect patient safety directly.
What a Final Rule Could Mean for Smaller Organizations
Small practices and rural hospitals face the heaviest burden. Many have one IT contractor and limited budgets. Provider groups argue that the proposal would strain them financially.
Practical responses include managed security services, shared compliance resources, staged implementation, and stronger vendor contracts. Documentation will be a major workload, since many controls require written evidence.
Questions to Ask Business Associates
Contracts should be paired with technical due diligence. Practical questions include:
- Does the vendor encrypt ePHI at rest and in transit?
- Is multi-factor authentication required for all administrative access?
- When did the vendor last complete a documented risk analysis?
- How quickly will the vendor notify the customer of an incident?
- Are backups tested and stored offline?
- Which subcontractors touch the data?
Answers should be documented. If a vendor cannot answer, that is information.
Low-Cost Steps for Smaller Organizations
Small teams cannot do everything at once. Prioritizing helps.
- Complete or update the enterprise risk analysis, since it drives every other decision.
- Turn on multi-factor authentication for email, remote access, and the EHR.
- Keep at least one backup copy offline and test restores quarterly.
- Train staff on phishing with short, frequent exercises.
- Maintain an inventory of devices and systems that store ePHI.
- Draft a one-page incident response plan with contact numbers.
None of these steps depends on a final rule, and each addresses a pattern that appears repeatedly in breach reports.
Current Versus Proposed Requirements
| Topic | Current Security Rule | 2024 proposal (not final) |
|---|---|---|
| Encryption | Addressable | Required, with limited exceptions |
| Multi-factor authentication | Not explicitly required | Required for many access points |
| Asset inventory and network map | Implied by risk analysis | Explicitly required and updated |
| Vulnerability scanning | Not specified | At least every six months |
| Penetration testing | Not specified | At least annually |
| Restoration after incident | Contingency plan required | Critical systems restored within 72 hours |
| Compliance audit | No fixed schedule | Annual |
Only the left column is legally binding today.
Enforcement Is Already Happening
OCR launched a risk analysis enforcement initiative in late 2024 and has announced multiple settlements since. Many cite the same failure: an organization never completed an accurate, thorough enterprise-wide risk analysis. Resolution agreements often require corrective action plans lasting several years, in addition to monetary penalties.
The pattern shows that waiting for a final rule is a poor strategy. Regulators can already cite missing risk analyses, weak access controls, and absent audit logs under existing law.
A Practical Scenario
A five-physician clinic uses a cloud-based electronic health record and an outsourced billing company. One morning, a staff member opens a phishing email, and ransomware encrypts the local file server that holds scanned documents. The clinic has backups, but they sit on a drive connected to the same network and are also encrypted.
Appointments are rescheduled, and staff work on paper for days. Under the current rule, the clinic should have had a documented risk analysis, a contingency plan, and tested backups. Under the proposed rule, offline backups, a 72-hour restoration target, and an asset inventory would be explicit expectations. The scenario shows why the proposals focus on resilience and not only on confidentiality.
How to Track Changes Without Being Misled
Use a source hierarchy:
- Federal Register
- HHS Office for Civil Rights (OCR)
- CMS, where relevant
- Official enforcement guidance and resolution agreements
- State regulators
- Professional compliance organizations
- Secondary reporting and vendor blogs
Many vendor articles describe proposals as if they were final. Check whether a source links to a published final rule.
What a Practical Roadmap Looks Like
Organizations can phase work without waiting for the final rule. In the first 30 days, assign an accountable security lead, collect an inventory of systems that store ePHI, and review the last risk analysis. Over the next 60 days, close the highest risks, such as missing multi-factor authentication and untested backups, and review the top vendor contracts.
By 90 days, run a tabletop exercise that simulates ransomware, update the incident response plan, and document what was learned. Leadership should receive a short written summary. Documentation is a recurring theme in OCR enforcement, and it would become even more important under the proposed rule.
What Each Source in the Hierarchy Offers
The source hierarchy helps avoid misinformation, but each level has a different role.
1. Federal Register. The legal record of proposed and final rules. A rule is not final until it appears here as a final rule with an effective date.
2. HHS Office for Civil Rights. OCR enforces HIPAA and publishes guidance, fact sheets, and settlements. It speaks for the agency that will apply the rule.
3. CMS, where relevant. CMS rules intersect with HIPAA through electronic transactions and program participation.
4. Official enforcement guidance. Resolution agreements show how OCR interprets requirements in real cases.
5. State regulators. States may have stricter privacy and breach laws, so compliance often involves more than HIPAA.
6. Professional compliance organizations. Groups such as industry associations explain practical implications and often file public comments.
7. Secondary reporting. Blogs, vendor sites, and news articles are useful for context, but they should link to the primary source.
The Cost of a Breach
Cybersecurity budgets are easier to justify with the numbers in view. IBM’s annual Cost of a Data Breach report has ranked healthcare as the most expensive industry for breaches for many consecutive years, with average costs in the millions of dollars per incident. Beyond direct costs, breaches trigger notification duties, regulatory investigation, lawsuits, and reputational damage.
The 2024 Change Healthcare attack, which affected roughly 190 million people, showed that the impact reaches payment systems and pharmacies, not only the targeted organization. Disruptions lasted weeks for many providers and forced emergency financing measures.
Compliance Today, Preparedness for Tomorrow
Organizations should separate what is legally required now from what may become required later. The current Security Rule already demands risk analysis, access controls, and contingency planning. Strengthening those controls is worthwhile whether HHS finalizes the proposal in 2027, revises it, or drops it.
For compliance leaders, the practical approach is to treat the proposal as a preview of enforcement priorities, not as a binding calendar. Organizations that already have a current risk analysis, MFA, tested backups. Vendor oversight will find any final rule much easier to meet, and they are less likely to appear in an OCR settlement under the existing one.
Leaders should also keep boards informed. Cybersecurity is now a patient safety and financial risk issue. Clear metrics help decision makers fund it: percentage of systems covered by MFA, time to restore critical systems in the last test, number of vendors reviewed, and percentage of staff completing phishing training.
Disclaimer: This article is general information about a regulatory topic and is not legal advice. Consult qualified counsel or a compliance professional for decisions affecting a specific organization.
FAQ
Q: Is the HIPAA Security Rule changing in 2026?
A: Not yet. HHS proposed a major update in December 2024, but it has not been finalized, and the current rule remains in force. The regulatory agenda lists July 2027 for final action.
Q: What is the current HIPAA Security Rule?
A: It is a federal rule requiring covered entities and business associates to protect electronic protected health information through administrative, physical, and technical safeguards.
Q: What did the 2024 Security Rule proposal change?
A: It proposed making most specifications mandatory, requiring encryption and multi-factor authentication, mandating testing and asset inventories, and tightening business associate oversight.
Q: Does HIPAA require encryption?
A: Under the current rule, encryption is an addressable specification, so organizations must implement it or document an equivalent alternative. The proposal would make it required with limited exceptions.
Q: What are HIPAA administrative safeguards?
A: They are policies and procedures for managing security, including risk analysis, workforce training, access management, and contingency planning.
Q: What are HIPAA technical safeguards?
A: They are technology controls such as access controls, audit logs, authentication, integrity checks, and transmission security.
Q: How does HIPAA apply to business associates?
A: Business associates that handle ePHI must comply with the Security Rule directly and sign agreements with covered entities describing their safeguards.
Q: What should healthcare organizations review for cybersecurity?
A: Review risk analysis, access controls, multi-factor authentication, backups, incident response, vendor risk, training, encryption, monitoring, and disaster recovery.