HIPAA security risk assessment: How to conduct one
When something goes wrong under HIPAA, the first document investigators ask for is your HIPAA security risk assessment. In 2025, the HHS Office for Civil Rights settled with BST & Co. CPAs, an accounting firm that handled patient information for a physician group’s tax work. Ransomware reached its network through a phishing email and exposed data on 170,000 people. OCR’s core finding was that the firm had never assessed the risks to the health information it held.
The requirement reaches well past clinics. It covers medical and dental practices and every business that handles patient data for one.
Key takeaways
- Every organization covered by HIPAA, and every business associate, must do an accurate and thorough risk analysis of the patient data it stores electronically.
- The analysis has to cover every place patient data lives or moves, rate each risk, and lead to a written plan to reduce it.
- Plan on a full assessment at least once a year, and an update whenever systems or operations change.
- Keep the documentation for at least six years.
Talk to an advisor
Ask about your own setup.
We ask what you’re trying to accomplish and tell you what we’d look at first. It costs nothing to talk, and no price comes up on this call.
What is a HIPAA security risk assessment?
The Security Rule calls it a risk analysis. People also say security risk assessment or SRA. They all mean a documented review of the risks to the confidentiality, integrity and availability of electronic protected health information (ePHI), followed by a plan to reduce those risks. Under 45 CFR 164.308, you must “conduct an accurate and thorough assessment of the potential risks and vulnerabilities” to the ePHI you hold, then “implement security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level.” The first part is risk analysis and the second is risk management. Regulators expect to see both.
Every covered entity (health plans, clearinghouses and providers who bill electronically) and every business associate must do one. That includes billing services, IT and cloud providers, transcription services, shredding companies, and attorneys and accountants who receive patient data.
How to conduct a HIPAA risk assessment, step by step
HHS guidance lays out the elements a risk analysis should include. In practice they become eight steps.

- Define the scope: all ePHI you create, receive, maintain or send, in every format and location, including the EHR, email, scanned documents, laptops, phones, backups, cloud apps, copiers and medical devices.
- Find where the data lives and moves. Interview staff, review systems and follow patient data from intake to billing to storage. Shadow copies, like a spreadsheet on someone’s desktop or files in a personal Dropbox, are what most reviews miss.
- Identify threats and vulnerabilities. Threats include phishing, ransomware, stolen laptops, insider snooping, hurricanes and power loss. Vulnerabilities are the gaps that let them through, such as unpatched software, shared logins or no offsite backup.
- Assess current safeguards such as MFA, encryption, access controls, backups, training and business associate agreements, and whether each one is actually used as intended.
- Rate likelihood and impact for each threat and vulnerability pair. A lost unencrypted laptop with 5,000 patient records is a very different risk from a single misdirected fax.
- Combine likelihood and impact into a risk level (high, medium, low) so you know what to fix first.
- Write a risk management plan listing each risk, the fix, who owns it and the target date. This is the part auditors most often find missing.
- Document and keep it for six years from when it was created or last in effect, whichever is later.
HIPAA security risk assessment checklist
When you finish, you should be able to hand an investigator each of these:
- A written scope listing every system, device, vendor and location that creates, receives, stores or sends ePHI.
- An asset inventory and a map of how patient data moves between those systems.
- A list of threats and vulnerabilities, each pairing rated for likelihood and impact.
- A risk level for every pairing, with the reasoning behind it.
- A risk management plan naming the fix, the owner and the target date for each risk.
- Signed business associate agreements with every vendor that stores or can reach ePHI.
- The policies, training records and access reviews the assessment relied on.
- A dated sign-off and the date of the next review.
Keep all of it, including versions you’ve replaced, for six years. The free HHS Security Risk Assessment Tool walks a small practice through most of this list.
How often to do one
The current rule doesn’t set a fixed schedule. HHS says risk analysis should be ongoing, and the documentation rules require you to review and update it when environmental or operational changes affect the security of ePHI. In practice, that means a full analysis at least once a year, an update after a significant change such as a new EHR, a cloud move, a new office or new remote work arrangements, and a review after any security incident, even one that didn’t become a reportable breach.
$175,000
Paid by accounting firm BST & Co. CPAs in a 2025 HHS settlement after OCR found it had not assessed risks to the patient data it held
The firm also agreed to two years of monitored corrective action.
What we find, and what our assessment includes
Every new client goes through our 14-page onboarding checklist, and Chad Odom, our owner, performs and signs that review himself. For practices and the business associates that serve them, the gaps fall into the same three groups the Security Rule uses:
- 01Administrative safeguards missing: the written policies, training and procedures the rule expects.
- 02Physical safeguards missing for offices, workstations and devices.
- 03Technical safeguards in place but misconfigured.
After onboarding, our healthcare clients get a risk assessment every year, delivered as a written report with a remediation plan. We also hold signed business associate agreements with every vendor that can touch PHI. Our healthcare IT services page explains how that fits into day-to-day support, and our guide to small business compliance shows how HIPAA sits alongside other rules you may fall under.
What the proposed Security Rule update would change
HHS published a proposed overhaul of the Security Rule in the Federal Register on January 6, 2025. As of October 2026, no final rule has been published, and HHS states that the current rule remains in effect while it works on the update. The proposal would make the risk analysis far more specific, requiring among other things:
- A written technology asset inventory and a network map showing how ePHI moves through your systems, updated at least once a year and whenever operations change.
- A written risk analysis that identifies threats, vulnerabilities and a risk level for each pairing.
- A compliance audit at least once every 12 months.
- Multifactor authentication and encryption of ePHI at rest and in transit, with limited exceptions.
- Written procedures to restore certain systems and data within 72 hours.
Build your next assessment around an asset inventory, a data flow map and MFA, and you’ll be in good shape whatever form the final rule takes. Our post on the new HIPAA Security Rule tracks the proposal.
Common mistakes
- Treating a checklist as a risk analysis. Yes and no answers about policies don’t rate specific risks to your own systems.
- Leaving backups, copiers, medical devices, phones, email or cloud apps out of scope.
- Finding risks and never fixing them, which can look worse than not looking.
- Missing business associate agreements with vendors that store or can reach patient data, including cloud email, backup and IT providers.
- Doing it once. An analysis from three years and two systems ago doesn’t reflect your current risks.
- Relying on a tool alone. The HHS Security Risk Assessment Tool costs nothing and gives small practices a good structure, but HHS says using it is neither required nor a guarantee of compliance.
An assessment more than a year old, or none at all, is the gap OCR keeps finding. Book a 15-minute call and we’ll talk through what yours should cover. Our compliance services and cybersecurity services handle the safeguards it turns up.
Frequently asked questions
What is the main purpose of a HIPAA risk assessment?
It finds the risks to the confidentiality, integrity and availability of the electronic patient information you hold, rates each one and leads to a written plan to reduce them. HIPAA requires it of every covered entity and business associate, and it’s the first document investigators ask for after an incident.
How often should a HIPAA risk assessment be done?
The current rule sets no fixed schedule, but HHS expects risk analysis to be ongoing. Plan on a full assessment at least once a year, an update after a significant change such as a new EHR or a new office, and a review after any security incident.
Is a HIPAA risk assessment mandatory?
Yes. Every covered entity, meaning health plans, clearinghouses and providers who bill electronically, and every business associate must do an accurate and thorough risk analysis of the electronic patient information it holds, then reduce the risks it finds. Business associates include billing services, IT and cloud providers, and attorneys and accountants who receive patient data.
What is the HHS SRA tool?
The HHS Security Risk Assessment Tool is free software from HHS that walks a small practice through a HIPAA risk assessment. It gives you a good structure, but HHS says using it is neither required nor a guarantee of compliance. You still have to rate the risks to your own systems and write a plan, with owners and dates, to reduce them.
Sources
- eCFR: 45 CFR 164.308, HIPAA administrative safeguards
- eCFR: 45 CFR 164.316, policies, procedures and documentation
- HHS: Guidance on risk analysis requirements under the HIPAA Security Rule
- HHS: HIPAA Security Rule NPRM fact sheet
- Federal Register: HIPAA Security Rule To Strengthen the Cybersecurity of ePHI (proposed rule), January 6, 2025
- HHS OCR: BST & Co. CPAs resolution agreement, 2025
- HHS: HIPAA resolution agreements and civil money penalties
- HealthIT.gov: Security Risk Assessment Tool
Next step
Let us handle this for you.
We tell you which rules apply, put safeguards in place and hand you the policies.
- 15 minutes
Tell us which question brought you here and how your office runs.
We’ll tell you how it applies to you and what we’d look at first.
If we’re not the right fit, we’ll say so.
