HHS has proposed the biggest change to the HIPAA Security Rule in years. It is still a proposal, and the current rule still applies. This guide explains where it stands as of November 2026, what the proposal would change in general terms and the practical steps vendors can take now, whatever the final text says. For hands-on help, see our HIPAA compliance consulting page.
We describe the proposal only in general terms. Until HHS publishes a final rule, the detail could change, so treat anything you read about exact requirements or deadlines with care.
What is the status of the proposed HIPAA Security Rule update?
HHS proposed a major update to the HIPAA Security Rule in January 2025. As of November 2026 the rule is not final, so it is still only a proposal. HHS's regulatory agenda points to a final rule around July 2027, but that is a target, not a commitment, and the final text and timing could change.
What this means for you today:
- The current Security Rule applies. Administrative (§164.308), physical (§164.310) and technical (§164.312) safeguards, a risk analysis and six years of documentation (§164.316) are all still required.
- Nothing in the proposal is yet a legal requirement.
- Compliance dates are not set. They will be in the final rule, if one is published.
What would the proposed Security Rule change?
The proposal would make the Security Rule more specific and more prescriptive. Its main themes are more specific technical requirements, such as encryption and multi-factor authentication, written asset inventories, and more frequent testing and review of security controls. It aims to replace some of today's flexibility with clearer, more detailed expectations.
In general terms, the themes are:
| Theme | What the proposal points to | What applies today |
|---|---|---|
| Technical requirements | More specific expectations for safeguards such as encryption and multi-factor authentication | Safeguards chosen and justified through your risk analysis |
| Asset inventory | A documented inventory of systems that handle ePHI | Not spelled out as a separate requirement, though a risk analysis is hard to do without one |
| Testing | More frequent testing and review of controls | Periodic evaluation of your safeguards |
| Documentation | More detailed written records | Documentation kept for six years |
We are not listing specific deadlines, frequencies or exceptions, because those belong to the final rule and could change before it is published.
Does the proposed update apply now?
The proposed update does not apply yet. It is not law, and HIPAA-covered entities and business associates don't have to follow it. The current Security Rule still applies in full, including the required risk analysis, risk management, the administrative, physical and technical safeguards, breach notification rules and six-year documentation retention. Plan for the proposal, but comply with the current rule.
Breach notification is unchanged by the proposal's status: individuals must be notified without unreasonable delay and no later than 60 days after discovery, and HHS and the media when more than 500 residents of a state or jurisdiction are affected.
How should vendors prepare for the Security Rule update now?
Start with the themes most likely to survive into a final rule: enable multi-factor authentication, encrypt ePHI at rest and in transit, build and maintain an asset inventory, and test your controls on a regular schedule. These are good practice already, customers ask about them, and they strengthen your current risk analysis whatever the final rule says.
1. Multi-factor authentication
Turn on MFA for all workforce access to systems holding ePHI, starting with administrators, remote access and email. Hospital security questionnaires already ask about it.
2. Encryption
Encrypt ePHI at rest and in transit across databases, backups, laptops and file transfers. Document how keys are managed.
3. Asset inventory
List every system, application, device and cloud service that creates, receives, stores or transmits ePHI, with an owner for each. Keep it current. Our HIPAA risk assessment guide shows how the inventory feeds the risk analysis.
4. More frequent testing
Schedule vulnerability scanning, penetration testing and control reviews, and record the results and fixes. See our security testing service if you need help.
5. Documentation
Write down what you do and why. Clear records make any future requirement easier to meet and satisfy today's six-year retention rule.
What does the proposal mean for your risk analysis?
Your risk analysis remains the centre of HIPAA compliance under the current rule, and it is the best place to plan for the proposal. Use it to record where you already meet the proposal's themes, where gaps remain and what each gap would take to close, so you can act quickly if a final rule is published.
A simple way to do this:
- Add a column to your risk register noting whether each risk relates to MFA, encryption, asset inventory or testing.
- Rate the gaps with the same likelihood and impact scale you already use.
- Put the quick wins into your current risk management plan, because they reduce real risk today.
- Keep the larger changes on a watch list with rough effort estimates, ready to schedule once the final text is known.
- Review the list whenever HHS publishes news on the rule.
This keeps the work inside the process you already run, rather than starting a separate project for a rule that is not yet final.
How does the update affect SaaS and business associates?
Business associates are directly responsible for the Security Rule today, so a final rule would apply to them too. SaaS vendors that handle ePHI for healthcare customers should expect the same themes in customer questionnaires and BAAs, sometimes before any final rule, because customers want vendors to meet the standard they expect to face themselves.
Practical steps for SaaS and other business associates:
- Check that your cloud provider's BAA covers every service holding ePHI.
- Make MFA and encryption the default in your product and internal tools.
- Keep your asset inventory in step with your architecture.
- Review BAAs for new security clauses, especially on testing and incident reporting.
For more, see HIPAA compliance for SaaS companies and business associate agreements explained.
What should you not do while the rule is only proposed?
Don't stop working on your current obligations while you wait, and don't rebuild everything around details of the proposal that could change. Avoid treating news articles or vendor marketing about exact requirements as settled law, and don't assume a long gap before compliance dates. Focus on the themes that are good practice anyway.
CyberWave GRC tracks the proposal and builds the likely themes into readiness work, so clients don't face a scramble if a final rule is published. Our HIPAA work covers a gap assessment, guidance and templates, then an independent assessment report by an assessor who did no readiness work for that client.
How can you track the final rule?
Watch for HHS publishing a final rule, which would set out the final requirements and compliance dates. HHS's regulatory agenda currently points to around July 2027. When a final rule appears, compare it with your risk analysis and controls, update your policies and plan any remaining changes before the compliance date.
Until then, keep your program current with the HIPAA compliance checklist, and budget for the work using HIPAA compliance cost.


