HIPAA Information

HIPAA Security Rule Checklist for 2026

A practical 2026 HIPAA Security Rule checklist: every current safeguard, what OCR asks for after a breach, and which proposed changes to start now.

Article Image

Key takeaways

  • The current HIPAA Security Rule is still the law in 2026. The overhaul HHS proposed in January 2025 is not final, and HHS now says it plans to finish it in July 2027.
  • OCR keeps settling cases for the same failure: no accurate and thorough risk analysis. If you only fix one item on this checklist, make it that one.
  • "Addressable" does not mean optional. You either put the safeguard in place or write down why something else works just as well.
  • Keep Security Rule policies, risk analyses and related records for six years.
  • Some proposed requirements cost little to start now and lower your risk today: an asset inventory, MFA, and scheduled vulnerability scans.

Most practices that end up in an OCR settlement didn't miss some obscure control. Usually the risk analysis was years old or missing, or the policy binder hadn't been opened since a consultant wrote it. This HIPAA Security Rule checklist for 2026 covers every standard in the current rule, grouped the way the regulation is (45 CFR Part 164, Subpart C). It also points out the proposed changes worth starting before they become required.

Where the HIPAA Security Rule stands in 2026

HHS published its proposed overhaul of the Security Rule in the Federal Register on January 6, 2025, and the comment period closed that March. HHS's regulatory agenda from fall 2025 listed May 2026 as the target for a final rule. That month passed with nothing published. The 2026 agenda then moved the rule to "long-term actions" with a new target of July 2027. That date is a plan, not a legal deadline.

In the meantime, CHIME and a coalition of more than 100 provider organizations asked HHS to withdraw the proposal or cut it back sharply. They argued that HHS underestimated compliance costs, especially for smaller and rural providers. The final version may look different from the 2025 draft, or it may never be finished.

For now, OCR measures your practice against the rule written in 2003 and last revised in 2013. Penalty amounts haven't changed either. HHS announced there would be no inflation adjustment for 2026, because the fall 2025 government shutdown stopped the release of the price data the adjustment depends on. The 2025 penalty levels still apply, with an annual cap of $2,190,294 per violation category at the most serious tier.

Required vs. addressable Each standard below has implementation specifications marked (R) for required or (A) for addressable. For an addressable item, you assess whether it's reasonable for your practice. Then you either put it in place or document why an equivalent alternative works, or why the item doesn't apply. "We skipped it" with no paperwork is a violation.

Administrative safeguards checklist (45 CFR 164.308)

More than half of the Security Rule's requirements are administrative safeguards, and most OCR findings come from this section. These are the policies, people and processes behind your technology.

Security management process

  • Risk analysis (R). Find every place electronic protected health information (ePHI) lives or travels. That includes the EHR, practice management and billing systems, email, phones, scanners, backups, cloud apps and anything a vendor hosts for you. For each one, record the threats, the weak spots, how likely a problem is and how bad it would be. Put a date on it.
  • Risk management (R). Write a plan that ties each high or medium risk to a fix, an owner and a due date. A risk analysis that nobody acts on is the most common finding in OCR settlements.
  • Sanction policy (R). Have a written policy for disciplining staff who break security rules, and records showing you've used it.
  • Information system activity review (R). Review audit logs, access reports and security incident tracking on a regular schedule. Keep a record that the reviews happened.

The current rule doesn't say how often to repeat the risk analysis. It says to review and update it periodically, and to do so whenever your environment changes. Examples include a new EHR, an office move, a merger or a security incident. Most OCR corrective action plans now require yearly updates, and the proposed rule would make every 12 months the legal minimum. Plan on doing it once a year.

If nobody on staff can run a vulnerability scan or trace where patient data moves across your network, this is the step to hand off. PolySec does on-site HIPAA security risk assessments for healthcare practices. The work covers network and vulnerability scans, a review of your policies and business associate agreements, an audit-ready findings report and a remediation roadmap. PolySec also stays involved while you fix what the report finds.

People and access

  • Assigned security responsibility (R). Name one security official in writing. In a small practice this can be the office manager, but it has to be a named person.
  • Workforce security (A). Have written steps for authorizing and supervising staff, screening them before they get access, and removing access when someone leaves. Check that former employees' accounts are actually disabled, including EHR, email, VPN and any shared logins.
  • Information access management. Give access based on job role (A) and record who approved it and when access changed (A). Healthcare clearinghouses also have to keep their clearinghouse functions separate from the rest of the organization (R).

Training

  • Security awareness and training. Train every staff member, and keep sign-in sheets or LMS records as proof. The addressable specifications cover security reminders, protection from malicious software, monitoring of login attempts and password management. Phishing deserves the most time, since it was the way in for several 2025 and 2026 settlements.

Incidents and contingency planning

  • Security incident procedures (R). Write down how staff report a suspected incident, who responds and how the response is documented. Keep an incident log, even if every entry so far is minor.
  • Data backup plan (R). Keep exact, retrievable copies of ePHI. At least one copy should be offline or immutable (unchangeable), so ransomware can't encrypt your backups along with everything else.
  • Disaster recovery plan (R) and emergency mode operation plan (R). These cover how you restore data and how you keep protecting it while systems are down.
  • Testing and revision (A). Restore something from backup at least once a year and write down how long it took. Many practices only find out their backups don't work during a ransomware attack.
  • Applications and data criticality analysis (A). Rank your systems by what has to come back first. For most practices that means scheduling, the EHR and e-prescribing.

Evaluation and vendors

  • Evaluation (R). Every so often, check your safeguards against the rule as a whole, and do it again after major changes. This is a broader compliance check than the risk analysis.
  • Business associate contracts (R). Have a signed BAA with every vendor that creates, receives, keeps or sends ePHI for you. Examples include IT providers, cloud backup, billing companies, answering services and shredding vendors.

Physical safeguards checklist (45 CFR 164.310)

A stolen laptop or an unlocked server closet doesn't take much technical skill to exploit. This short section protects against that kind of exposure.

  • Facility access controls (A). Have a facility security plan, procedures for who can get in, rules for letting staff in during emergencies, and records of repairs to doors, locks and alarms.
  • Workstation use (R). Write down what each type of workstation is for and how it should be used. That includes laptops staff take home.
  • Workstation security (R). Put physical barriers in place. Screens at the front desk should face away from patients, and server rooms and network closets should stay locked.
  • Disposal (R) and media re-use (R). Wipe or destroy drives before devices leave the building, and keep certificates of destruction. Copiers and fax machines often have hard drives, so include them.
  • Accountability (A) and data backup and storage (A). Track where hardware and media go, and make a backup before you move equipment.

Technical safeguards checklist (45 CFR 164.312)

  • Unique user identification (R). Give everyone their own login. Shared front-desk accounts make it impossible to tell who looked at a record.
  • Emergency access procedure (R). Have a documented way to reach ePHI when normal logins fail, such as "break-glass" accounts that are monitored.
  • Automatic logoff (A). Lock idle sessions after a set time. Shared clinical workstations need a shorter timeout than private offices.
  • Encryption and decryption (A). Encrypt ePHI stored on laptops, desktops, phones, servers and backups.
  • Audit controls (R). Turn on logging in the EHR and other systems with ePHI, and make sure someone actually reviews the logs (see "information system activity review" above).
  • Integrity (A). Use controls that would show whether ePHI has been changed or deleted without authorization.
  • Person or entity authentication (R). Confirm users are who they claim to be. Today that can mean passwords. MFA is the stronger choice and is likely to become required.
  • Transmission security (A). Encrypt ePHI sent over email, patient portals, file transfers and remote connections, and use integrity controls on those transmissions.
Why encryption pays for itself ePHI encrypted to HHS's standards doesn't count as "unsecured" PHI under the Breach Notification Rule. If an encrypted laptop is stolen and the key wasn't stolen with it, there's generally no breach to report. The same theft from an unencrypted laptop can mean notifying patients, reporting to HHS and possibly an investigation.

Is your risk assessment current?HIPAA requires one. We'll handle it for you.

Contact us

Policies, documentation and BAA requirements (45 CFR 164.314 and 164.316)

An OCR investigator will treat anything without paperwork as if it never happened. This part of the rule covers how you write things down and keep them.

  • Written policies and procedures for every standard above, adjusted to your practice's size and systems. A copied template that names software you don't use is a red flag.
  • Record retention for six years from when a document was created or last in effect, whichever is later. This covers risk analyses, policies, training records and evaluations.
  • Availability. The people responsible for carrying out the procedures must be able to get to them.
  • Periodic review. Review the documents on a schedule and update them when your operations or environment change. Each document should show a revision date.
  • BAA terms. Each BAA should require the vendor to follow the Security Rule, report security incidents and breaches to you, and get the same commitments from any subcontractors that touch your ePHI.

Proposed Security Rule changes to start on now

None of the following is required yet. Several items are still worth doing in 2026, because they make the current risk analysis easier and close the holes ransomware groups use most.

  • Technology asset inventory and network map. The proposal would require a written inventory of every system that touches ePHI and a map of how ePHI moves, both updated at least once a year. You need this information for an accurate risk analysis anyway.
  • MFA and encryption as required controls. The "addressable" label would go away for most safeguards, and MFA and encryption would be required with only narrow exceptions.
  • Vulnerability scans every six months and a penetration test every 12 months.
  • Network segmentation, so one compromised workstation can't reach everything else on the network.
  • Faster offboarding. A departing staff member's access would have to end within one hour after they leave. Other regulated entities would have to be told within 24 hours when someone's access changes or ends.
  • 72-hour restoration. Written procedures to restore critical systems and data within 72 hours of an incident.
  • Yearly business associate verification. Business associates would have to confirm in writing, at least once a year, that they've deployed the required technical safeguards. They would also have to notify you within 24 hours of activating their contingency plan.
  • Yearly compliance audit and yearly testing of whether your security measures actually work.
Important These are proposals, and the details may change before a final rule is published, if one is. Don't rewrite your policies to say the proposed rule is in effect. Do treat MFA, encryption and tested backups as risk decisions your current risk analysis has to address. OCR already expects that.

What OCR asks for after a breach

A ransomware investigation turns into a review of what you had in place before the attack. On April 23, 2026, OCR announced four settlements from separate ransomware cases. Together they affected more than 427,000 people and totaled $1,165,000. OCR's finding was the same in all four: no accurate and thorough risk analysis. In June 2026, an employer-sponsored group health plan paid $450,000 and agreed to a two-year corrective action plan. That was OCR's 14th action under its Risk Analysis Initiative. Business associates are included too. In March 2026, OCR settled with MMG Fusion, a dental software company, over a breach affecting about 15 million people.

When a data request arrives, have these ready to send:

  1. Your most recent risk analysis and the one before it, both dated, so OCR can see you repeat it.
  2. A risk management plan showing which fixes are done, in progress or accepted, with reasons.
  3. Policies and procedures with revision dates.
  4. Training records for every staff member with access to ePHI.
  5. Signed BAAs for every vendor that handles ePHI.
  6. Records of audit log reviews, backup restore tests and your incident log.

If item 1 is missing or stale, the rest won't carry much weight. Every 2026 corrective action plan above required a new risk analysis.

HIPAA Security Rule FAQ

Is the new HIPAA Security Rule in effect in 2026?

No. The January 2025 proposal is still a proposal, and HHS's current target for a final rule is July 2027. Practices must follow the existing Security Rule, which OCR is actively enforcing.

How often does HIPAA require a security risk assessment?

The current rule doesn't set an exact interval. It requires periodic review and updates after significant changes. Once a year is the practical standard. OCR corrective action plans usually require it, and the proposed rule would make it mandatory.

Is encryption required under HIPAA?

Under the current rule, encryption is addressable. You need to implement it or document a reasonable alternative. For laptops, phones and email containing ePHI, it's hard to justify an alternative, and encrypted data can keep a lost device from becoming a reportable breach.

Is multi-factor authentication required?

Not explicitly today. The proposed rule would require it for most systems. Remote access, email and the EHR should be first in line, since stolen passwords are a common starting point for ransomware.

Does a small practice have to meet the same Security Rule standards as a hospital?

The standards are the same, but the rule lets you scale how you meet them. A three-provider clinic's risk analysis and policies can be much simpler than a hospital's. They still have to be accurate, written down and kept up to date.

How long do HIPAA security records need to be kept?

Six years from the date a document was created or last in effect, whichever is later.

Your next step

Start with the date on your last risk analysis. If it's more than a year old, came before a major system change, or doesn't cover your vendors and cloud apps, update it first. Everything else on this checklist depends on it. After that, work through the administrative, physical and technical items, and give each gap an owner and a deadline.


This article is for general information and isn't legal advice. Talk to a qualified professional about your practice's specific situation.

Written by the PolySec Team

PolySec performs HIPAA Security Risk Assessments for healthcare practices and business associates nationwide.

Get your required HIPAA risk assessment done.

Tell us about your practice and we'll scope the assessment for you.

Contact us