If you could do only one thing for HIPAA Security Rule compliance, it should be the risk analysis. It's the foundation every other safeguard builds on, it's required of both covered entities and business associates, and its absence or inadequacy shows up again and again in HHS Office for Civil Rights (OCR) enforcement actions.
What the Security Rule requires
The Security Rule's administrative safeguards require organizations to "conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information" and to implement security measures sufficient to reduce those risks to a reasonable and appropriate level.
In plain terms: find all your ePHI, understand what could go wrong with it, decide how likely and harmful each scenario is, and do something about the risks that matter.
What OCR expects to see
HHS guidance describes the elements of a sound risk analysis. In practice, OCR looks for:
- Scope that covers all ePHI — every system, application, device, location and vendor that creates, receives, maintains or transmits it, including cloud services and mobile devices.
- Data collection — documentation of where ePHI lives and how it moves.
- Threats and vulnerabilities — reasonably anticipated threats and the vulnerabilities they could exploit.
- Current security measures — what's already in place and how effective it is.
- Likelihood and impact — an assessment of how likely each threat is to occur and how severe the impact would be.
- Risk levels — risk ratings that drive prioritization.
- Documentation — a written record of the analysis and its results.
- Periodic review and updates — the analysis must stay current as the environment changes.
Common mistakes
Treating a gap assessment as a risk analysis. A checklist of Security Rule standards with "yes/no" answers tells you about compliance, not risk. OCR has repeatedly found that such assessments don't meet the requirement.
Leaving systems out. Risk analyses often focus on the EHR and miss the billing system, email, file shares, imaging, medical devices, backups and vendors.
Never updating it. A risk analysis from three years and two system migrations ago no longer describes your environment.
Stopping at analysis. The Security Rule requires risk management too: a documented plan to reduce risks, with owners and timelines, and evidence that the plan is being executed.
A practical approach
- Inventory ePHI and assets. Build a list of systems, data flows and vendors, and keep it current.
- Identify threats and vulnerabilities for each asset — ransomware, phishing, misconfiguration, lost devices, insider misuse, vendor compromise and more.
- Evaluate existing controls such as MFA, encryption, backups, logging and access reviews.
- Rate likelihood and impact consistently using a defined scale.
- Prioritize risks and agree on treatments with leadership.
- Document and track the risk management plan through to completion.
- Revisit at least annually and whenever there are significant changes.
The proposed Security Rule update
In January 2025, HHS published a notice of proposed rulemaking that would substantially update the Security Rule. Among other changes, the proposal would:
- Remove the distinction between "required" and "addressable" implementation specifications
- Require a written technology asset inventory and network map
- Make risk analysis requirements more specific and require review at least every 12 months
- Require safeguards such as encryption and multi-factor authentication, with limited exceptions
- Add requirements for vulnerability scanning, penetration testing and contingency planning
As of this writing, the proposed rule has not been finalized, and the current Security Rule remains in effect and enforced. Even so, many of the proposed safeguards, includiong asset inventories, MFA, encryption, and tested backups are best practice today and reduce risk regardless of the rule's outcome.
The bottom line
A strong risk analysis is enterprise-wide, honest about threats, specific about risk and tied to a plan that actually gets executed. Get it right, keep it current, and it becomes the roadmap for your security program, and your best evidence if OCR ever comes calling.