Prepare Today for the Next HIPAA Security Rule

HHS has proposed significant changes to the HIPAA Security Rule, including more specific cybersecurity safeguards, risk-analysis documentation, workforce security awareness, and ongoing testing requirements. Independent practices can begin strengthening their compliance programs today.

HHS PLANNED FINAL ACTION: JULY 2027
January 6, 2025HHS published the proposed rule (90 FR 898).
July 2027Planned final action in the Federal Unified Agenda (RIN 0945-AA22). Planned dates can change.
After a final ruleEffective and compliance dates would be set by the final rule, if HHS finalizes it. The proposals are not current law.

Start with a Security Risk Analysis

A thorough, current risk analysis is already required (45 CFR §164.308(a)(1)(ii)(A)). HHS’s proposal would add more specific written documentation and require the assessment to be reviewed, verified, and updated at least every 12 months and when relevant changes occur.

That is about keeping the analysis accurate and documented. It would not automatically require a new third-party assessment every year.

Strengthen Workforce Security Awareness

Security awareness training is already part of the Security Rule. HHS’s proposal would require role-based security awareness training at least every 12 months, with more specific requirements for new employees and ongoing education.

A general online course can support that effort, but it does not replace training on your practice’s own policies and procedures.

What Is Changing?

Risk-analysis documentation

Proposed: More specific written documentation, with the analysis reviewed, verified, and updated at least every 12 months and when relevant changes occur.

For your practice: Keep dated, written records instead of a one-time report.

Annual role-based awareness training

Proposed: Role-based security awareness training at least every 12 months, with more specific requirements for new employees.

For your practice: Plan content by role and keep a training log.

Asset inventories and network mapping

Proposed: A written inventory of technology assets and a map of how ePHI moves through your systems, kept current.

For your practice: List computers, devices, software, and vendors that touch ePHI.

Multi-factor authentication

Proposed: MFA for access to systems that hold or reach ePHI, with limited exceptions.

For your practice: Identify email, EHR, and remote-access accounts that still use passwords alone.

Encryption

Proposed: Encryption of ePHI at rest and in transit, with limited exceptions.

For your practice: Check laptops, servers, backups, and email for unencrypted ePHI.

Vulnerability scanning and penetration testing

Proposed: Regular vulnerability scanning and periodic penetration testing of systems that hold ePHI.

For your practice: Ask your IT provider what is scanned today and how often.

Annual compliance audits

Proposed: A documented audit of Security Rule compliance at least every 12 months. This is separate from reviewing the risk analysis.

For your practice: Plan a yearly check that policies are actually being followed.

Incident response

Proposed: Written incident response plans and procedures, with testing.

For your practice: Decide who does what in the first hours of an incident.

Backup and restoration

Proposed: Written procedures to restore critical systems and data within a defined timeframe.

For your practice: Test a restore, not just the backup job.

Business associate verification

Proposed: Written verification, at least every 12 months, that business associates have deployed required safeguards.

For your practice: Keep a current business associate list and request written confirmation.

Written policies and documentation

Proposed: More specific written policies, procedures, plans, and analyses, maintained and reviewed.

For your practice: Keep everything in one organized place with owners and dates.

Required vs. addressable

Proposed: The “addressable” label would be removed so that implementation specifications are generally required, with limited exceptions.

For your practice: Do not rely on “addressable” to skip a safeguard; document your reasoning today.

What Your Practice Can Do Today

  1. Assess. Complete or refresh your Security Risk Analysis so you know where ePHI lives and what could go wrong.
  2. Prioritize. Rank findings by risk and start with the gaps that are cheapest and most protective, such as MFA, backups, and encryption.
  3. Educate. Train staff by role on phishing, passwords, and reporting, and refresh it regularly. See privacy training vs. security awareness and security awareness for everyday staff.
  4. Document. Write down policies, decisions, vendors, and training so you can show what you did and when.
  5. Prepare. Draft an incident response plan and test your backups, so you are ready whatever the final rule requires.

Sources

More in the full Reference Library. This page is general information, not legal advice.

Want help turning these proposals into a practical plan for your practice?

Schedule a HIPAA Consultation →
Scroll to Top