The risk analysis is the one Security Rule requirement OCR returns to most often, and the one most often found inadequate. Under 45 CFR §164.308(a)(1)(ii)(A), covered entities and business associates must conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of the ePHI they hold.
The rule does not prescribe a method. HHS guidance and NIST SP 800-66 Rev. 2 describe the elements a defensible analysis should contain, and this checklist follows that structure. Use it to plan the work, to check a vendor’s deliverable, or to prepare for a HIPAA security risk assessment engagement.
Key points
- Scope must cover all ePHI the organization creates, receives, maintains or transmits — in every location and format.
- Risk = likelihood × impact for each threat–vulnerability pair, rated against current controls.
- A risk analysis is not an audit, and it is not finished until it feeds a risk management plan.
- Update it on a schedule and whenever operations or technology change.
Before you start: planning checklist
- Name an owner (usually the security official under §164.308(a)(2)) and an executive sponsor who can approve remediation spending.
- Decide on a methodology and rating scale before collecting data, so results are comparable year to year.
- Gather prior risk analyses, audit findings, incident logs and remediation plans.
- Identify interviewees: IT, clinical or product leads, HR, facilities, finance and key vendors.
- Set the assessment period and the date the analysis will be considered current as of.
- Agree on where evidence and working papers will be stored and who can access them.
Step 1: Define scope
HHS guidance is explicit that the analysis should include all ePHI regardless of the electronic medium — servers, laptops, mobile devices, removable media, cloud services and medical or IoT devices. A common failure is scoping only the EHR or only production cloud infrastructure.
- All locations, including remote workers and satellite sites
- All systems that store, process or transmit ePHI, including backups and logs
- Third-party and cloud environments under your control or configuration
- Data flows to and from business associates and subcontractors
- Explicitly documented exclusions, with the reason for each
Step 2: Build the asset and ePHI inventory
| Field | Why it matters |
|---|---|
| System or asset name and owner | Someone must be accountable for remediation |
| Type of ePHI and approximate record volume | Drives impact ratings |
| Where it is stored, hosted or transmitted | Defines physical and technical exposure |
| Who has access (roles, vendors) | Feeds access control and workforce findings |
| Interfaces and data flows | Reveals transmission and integration risk |
| Business associate involved, if any | Confirms a BAA is needed and in place |
Step 3: Identify threats and vulnerabilities
A threat is something that could exploit a weakness; a vulnerability is the weakness itself. Document both and pair them, because risk only exists where a credible threat can act on a real vulnerability.
Threat sources to consider
- Human, intentional: ransomware operators, phishing, insider snooping, theft of devices
- Human, unintentional: misdirected email or fax, misconfigured cloud storage, accidental deletion
- Environmental: power loss, fire, flood, HVAC failure in server rooms
- Technical: hardware failure, software defects, vendor outages
How to find vulnerabilities
- Interviews and walkthroughs of how staff actually handle PHI
- Configuration reviews of identity, endpoints, cloud and network
- Vulnerability scan results and patch status (recommended practice inputs)
- Review of prior incidents and near misses
Step 4: Assess current security controls
For each threat–vulnerability pair, record the controls already in place and whether they are actually used and configured as intended. Look at administrative, physical and technical controls together; a strong technical control can be undone by a missing termination procedure.
Step 5: Rate likelihood and impact
Use a consistent scale. The matrix below is a common three-level approach; many organizations use five levels. The specific scale matters less than applying it consistently and explaining it in your documentation.
| Likelihood \ Impact | Low | Medium | High |
|---|---|---|---|
| High | Medium | High | High |
| Medium | Low | Medium | High |
| Low | Low | Low | Medium |
Step 6: Determine risk levels and document the results
- Assign a risk level to every threat–vulnerability pair and list the corrective actions considered.
- Record addressable-specification decisions and the reasoning tied to specific risks.
- Produce a risk register that can be sorted, assigned and tracked — not just a narrative report.
- Have the results reviewed and accepted by leadership, with any risk acceptance documented.
- Retain the analysis and supporting evidence for at least six years (§164.316(b)(2)(i)).
Step 7: Hand off to risk management and keep it current
Risk analysis and risk management are separate requirements. §164.308(a)(1)(ii)(B) requires security measures sufficient to reduce risks to a reasonable and appropriate level. Our HIPAA risk management page covers that phase in detail.
- 1
Prioritize the register
Rank high risks first and set realistic remediation dates.
- 2
Assign owners and budgets
Unfunded remediation is the most common reason risk plans stall.
- 3
Track progress
Review open items monthly or quarterly with the security official.
- 4
Update on triggers
Revisit the analysis after new systems, migrations, mergers, new vendors, major incidents or relevant regulatory changes — and on a regular schedule, commonly annually.
Common reasons a risk analysis falls short
The free SRA Tool from ONC and OCR can help small practices structure the work, but using it does not by itself ensure compliance. The analysis still has to reflect your actual systems and risks. If terminology is causing confusion internally, see risk analysis vs. risk assessment.
- Scope limited to one system or one site
- A questionnaire or tool output with no organization-specific findings
- No likelihood or impact ratings, so nothing can be prioritized
- Treating a gap analysis or compliance checklist as the risk analysis
- Never updated after the first year
Frequently asked questions
Is a risk assessment the same as a HIPAA audit?
No. A risk analysis identifies and rates risks to ePHI so you can manage them. An audit tests whether controls meet a defined standard. Neither one is a government audit, and neither results in a certification.
How often is a HIPAA risk analysis required?
The rule does not set a fixed frequency. It requires the analysis to be accurate and thorough and to be reviewed and updated as needed. Most organizations update annually and after significant changes.
Can we use the HHS SRA Tool instead of a consultant?
Yes, many small practices do. The tool helps structure the work, but the answers must reflect your environment, and using it does not by itself demonstrate compliance.
Do cloud-hosted systems need to be in scope?
Yes. If ePHI is in a cloud service, the configuration and access you control are in scope. A cloud provider signing a BAA does not transfer your responsibility for how you use the service.
What deliverables should a risk analysis produce?
At minimum: a scope statement, an asset and ePHI inventory, a threat and vulnerability list, current-control descriptions, likelihood and impact ratings, a prioritized risk register and documented addressable decisions.
Authoritative sources
- HHS: Guidance on Risk Analysis Requirements under the HIPAA Security Rule
- NIST SP 800-66 Rev. 2: Implementing the HIPAA Security Rule
- HealthIT.gov: Security Risk Assessment (SRA) Tool
- eCFR: 45 CFR Part 164 (Security and Privacy)
This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.