Shieldra

HIPAA Compliance Checklist 2026

A practical, 12-step checklist for building a documented HIPAA compliance program under the Security Rule in force today — what each step requires, why OCR cares about it, and what evidence proves you did it. Updated November 2026 (includes the proposed Security Rule changes).

Key takeaways

  • There are 12 steps. HHS proposed making MFA, encryption, and annual penetration testing mandatory in January 2025 (90 FR 898); that proposal has not been finalized, but hospitals already expect those controls.
  • Start with the Security Risk Analysis: OCR launched a Risk Analysis Initiative in 2024 and has announced a run of settlements centered on missing or inadequate risk analyses.
  • Every covered entity and business associate needs a Security Official; covered entities also need a Privacy Official.
  • Every step needs evidence, not just intent: appointment letters, risk analyses, access reviews, training records, and incident documentation.
  • The HIPAA civil monetary penalty maximum for 2026 is $2,190,294, effective for penalties assessed on or after January 28, 2026.

The 12-step HIPAA compliance checklist

Each step below maps to a HIPAA requirement in force today or to a control hospitals routinely expect. The "why" is what an OCR investigator, auditor, or hospital reviewer is looking for when they ask about it.

1. Designate a Security Officer (and, for covered entities, a Privacy Officer)

Every covered entity and business associate must assign a Security Official (45 CFR 164.308(a)(2)); covered entities must also designate a Privacy Official (164.530(a)). One person can hold both roles at a small organization, but the responsibilities must be assigned in writing. Hospital security questionnaires ask who owns HIPAA at your company, and the written designation is the evidence.

2. Conduct a Security Risk Analysis — and update it annually

The Security Rule requires a thorough, accurate, and current risk analysis identifying threats and vulnerabilities to ePHI. Many organizations skip it or treat it as a one-time exercise. OCR launched a Risk Analysis Initiative in 2024 and has announced a run of settlements centered on missing or inadequate risk analyses.

3. Implement multi-factor authentication on all systems with ePHI

The current Security Rule requires person or entity authentication (45 CFR 164.312(d)) but does not name MFA. The January 2025 proposed update would make MFA mandatory; it has not been finalized. Hospitals and payers already expect MFA on every EHR, billing system, cloud console, email, and remote access tool touching ePHI.

4. Encrypt ePHI at rest and in transit

Encryption is the only safe harbor under the Breach Notification Rule. Encrypted PHI exposed in a breach typically does not trigger notification obligations, which makes this the highest-leverage control on the list.

5. Sign Business Associate Agreements with every vendor that touches PHI

Disclosing PHI to a vendor without a BAA is itself a HIPAA violation, and OCR has settled cases over missing BAAs. Maintain a vendor inventory, and confirm each vendor will actually sign — many popular tools will not.

6. Document and enforce role-based access controls

Workforce members viewing records they have no reason to see is a recurring theme in OCR enforcement, and access reviews are a standard question in hospital security reviews. Minimum necessary access must be defined, enforced, and reviewed on a schedule you can evidence.

7. Enable audit logging across all systems that handle PHI

The Security Rule requires audit controls (45 CFR 164.312(b)) and regular review of information system activity (164.308(a)(1)(ii)(D)). Logs nobody reviews do not satisfy that, and hospital security reviews ask how alerts are triaged.

8. Train every workforce member on HIPAA — and document it

Security awareness and training is a named Security Rule standard (164.308(a)(5)). Missing or stale training is one of the easiest findings for an auditor to cite, because the absence of a record is unambiguous.

9. Build and test an incident response plan against the 60-day notification clock

Covered entities must notify affected individuals without unreasonable delay and no later than 60 days after discovering a breach of unsecured PHI (45 CFR 164.404); business associates must notify the covered entity within the same outer limit (164.410), and many BAAs set shorter deadlines. A late notification is a violation in its own right, and an untested plan is not a plan.

10. Implement business continuity and test your recovery

The current rule requires a contingency plan with data backup, disaster recovery, and emergency-mode operation (45 CFR 164.308(a)(7)). The proposed update would add a 72-hour restoration target; it has not been finalized. Untested backups fail, and ransomware specifically targets healthcare backup chains.

11. Track and remediate findings between audits — not just at audit time

The Security Rule requires risk management (164.308(a)(1)(ii)(B)): reducing the risks your analysis found to a reasonable and appropriate level. Reviewers ask whether you acted on your risk analysis, so each finding needs an owner, a due date, and a documented fix.

12. Produce auditor-ready evidence on demand — not on deadline

Organizations that scramble during an audit make mistakes that turn minor findings into major ones. Evidence kept current as it is produced flips the dynamic: the reviewer is checking what is already documented rather than waiting for you to assemble it.

What the proposed Security Rule update would change

In January 2025 HHS proposed changes to the Security Rule (90 FR 898), including stricter encryption, MFA, asset-inventory and testing requirements. As of November 2026, that proposal has not been finalized; the rule in force is the current 45 CFR Part 164, Subpart C. Many hospitals already ask for those controls in security reviews, so treat them as buyer expectations rather than law.

Proposed, not yet in force

  • Multi-factor authentication required rather than left to the risk analysis
  • Encryption of ePHI at rest and in transit required, with limited exceptions
  • Restoration of critical systems within 72 hours
  • Annual penetration testing and more frequent vulnerability scanning

Separately, the inflation-adjusted civil monetary penalty maximum for 2026 is $2,190,294, for penalties assessed on or after January 28, 2026 (45 CFR 102.3).

How to work through the checklist

Do not work top to bottom. Start with the Security Risk Analysis, because it tells you which of the remaining steps carry real risk in your environment, and it is the item OCR asks for first. Then close the two controls hospitals ask about first: encryption and MFA.

After that the work is mostly documentation discipline — BAAs, access reviews, training records, incident documentation — and the constraint is usually not knowing what to do but keeping evidence current as staff, vendors, and systems change.

That maintenance is what Shieldra helps with: take the free readiness check to see where you stand, then convert gaps into owned, dated tasks with evidence attached to each requirement. Plans start at $299/month with a 14-day free trial.

Frequently asked questions

What is on the HIPAA compliance checklist for 2026?

Twelve steps: designate a Security Officer (and, for covered entities, a Privacy Officer), conduct and regularly update a Security Risk Analysis, implement MFA, encrypt ePHI at rest and in transit, sign BAAs with every vendor touching PHI, enforce role-based access controls, enable audit logging, train and document your workforce, build and test an incident response plan, implement and test business continuity, track and remediate findings between audits, and keep auditor-ready evidence available on demand.

What HIPAA failure does OCR focus on most?

A missing, incomplete, or out-of-date Security Risk Analysis. OCR launched a Risk Analysis Initiative in 2024 and has announced a run of settlements centered on risk analysis failures. Risk management, acting on what the analysis found, is a separate required specification.

Is multi-factor authentication required under HIPAA?

Not by name today. The current Security Rule requires person or entity authentication (45 CFR 164.312(d)) and does not name MFA. The January 2025 proposed update (90 FR 898) would make MFA mandatory for systems with ePHI; as of November 2026 it has not been finalized. Hospitals and payers routinely expect MFA in security reviews, so treat it as required in practice.

What is the maximum HIPAA penalty in 2026?

The inflation-adjusted HIPAA civil monetary penalty maximum for 2026 is $2,190,294, effective for penalties assessed on or after January 28, 2026.

How often does a HIPAA risk assessment need to be updated?

The current Security Rule sets no fixed interval: the analysis must be accurate and current, reviewed periodically and after any significant change to systems, vendors, or operations. At least annually is common practice, and the January 2025 proposed rule (not yet final) would make annual review explicit. A risk analysis from three years ago will not satisfy a reviewer.

Do I need a BAA with every vendor?

You need one with every vendor that creates, receives, maintains, or transmits PHI on your behalf. Many widely used tools will not sign a BAA at all, which means they cannot be used with PHI regardless of their security posture.