HIPAA9 min read

HIPAA Risk Assessment Guide

A risk assessment is the foundation of HIPAA compliance. The Security Rule requires covered entities and business associates to conduct an accurate and thorough assessment of potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI.

This guide walks through how to conduct a HIPAA-compliant risk assessment, what to document, and how to use findings to improve your security posture.

Key Takeaways

Aspect Details
Requirement Mandatory under Security Rule §164.308(a)(1)(ii)(A)
Frequency Initial assessment, then when changes occur (annually recommended)
Scope All ePHI you create, receive, maintain, or transmit
Output Documented assessment with risk ratings and remediation plan
Ownership Security Officer with input from technical and operational teams

Quick Answer: A HIPAA risk assessment identifies where your ePHI is, what could threaten it, how vulnerable you are, and what the impact would be if something went wrong. It's required by HIPAA, must be documented, and should drive your security program decisions.

Why Risk Assessment Matters

Regulatory Requirement

The HIPAA Security Rule explicitly requires:

  • "Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information held by the covered entity or business associate." §164.308(a)(1)(ii)(A)

Foundation for Compliance

Risk assessment drives:

  • Security control selection and implementation
  • Resource allocation decisions
  • Policy development
  • Training priorities
  • Vendor management focus

Enforcement Consideration

HHS OCR consistently cites inadequate risk assessment in enforcement actions. Common findings:

  • No risk assessment conducted
  • Risk assessment not comprehensive
  • Risk assessment not updated after changes
  • Findings not addressed

When to Conduct Risk Assessment

Required Triggers

Trigger Action
Initial implementation Conduct comprehensive assessment
New system or application Assess new ePHI environment
Significant change Assess impact of changes
Security incident Reassess affected areas
Periodic review Annual review recommended

Significant Changes Requiring Reassessment

  • New applications handling ePHI
  • Changes to network architecture
  • New vendors with ePHI access
  • Organizational changes (merger, acquisition)
  • New office locations
  • Changes to business processes
  • Major security incidents
  • Regulatory changes

Risk Assessment Framework

Step 1: Define Scope

Identify all ePHI:

  • Where is ePHI created?
  • Where is ePHI received?
  • Where is ePHI stored?
  • How is ePHI transmitted?
  • Who has access to ePHI?

Document ePHI inventory:

System/Location ePHI Type Volume Access
Production database Patient records 50,000 records App, DB admins
Backup storage Full database copies 50,000 records Backup admin
Customer support tool Support tickets with PHI 1,000/year Support team
Email system Occasional PHI in messages Low All employees

Step 2: Identify Threats

Threat categories:

Category Example Threats
Natural Floods, earthquakes, fires, power outages
Human (intentional) Hackers, malicious insiders, social engineering
Human (unintentional) Employee errors, misconfiguration, accidents
Environmental Hardware failures, software bugs, network issues

Common threats to ePHI:

  • Ransomware and malware
  • Phishing attacks
  • Unauthorized access by employees
  • Vendor security failures
  • Data exposure through misconfiguration
  • Lost or stolen devices
  • Insider threats
  • System failures
  • Natural disasters

Step 3: Identify Vulnerabilities

Vulnerability assessment areas:

Area Assessment Questions
Access controls Are access controls adequate? Is MFA implemented?
Encryption Is ePHI encrypted at rest and in transit?
Audit logging Are activities logged? Are logs reviewed?
Training Are employees trained on security?
Incident response Are procedures in place and tested?
Vendor management Are BAAs in place? Are vendors assessed?
Physical security Are facilities and devices secured?
Network security Are networks segmented and monitored?

Vulnerability discovery methods:

  • Technical vulnerability scanning
  • Configuration reviews
  • Policy and procedure review
  • Interviews with personnel
  • Penetration testing
  • Previous incident analysis
  • Audit findings

Step 4: Assess Current Controls

Document existing controls:

Control Area Current Controls Effectiveness
Access control RBAC, MFA for admins Partial (MFA not universal)
Encryption TLS in transit, none at rest Partial
Audit logging Application logs, no centralization Partial
Training Annual security awareness Adequate

Control effectiveness ratings:

  • Effective: Control fully mitigates the risk
  • Partial: Control reduces but doesn't eliminate risk
  • Ineffective: Control doesn't adequately address risk
  • None: No control in place

Step 5: Determine Likelihood

Likelihood rating factors:

  • Historical occurrence (internally and industry-wide)
  • Threat capability and motivation
  • Vulnerability exploitability
  • Current control effectiveness

Likelihood scale:

Rating Description Probability
High Expected to occur >50% in next year
Medium Could occur 10-50% in next year
Low Unlikely to occur <10% in next year

Step 6: Determine Impact

Impact assessment factors:

  • Number of individuals affected
  • Sensitivity of ePHI exposed
  • Operational impact
  • Financial impact
  • Reputational impact
  • Regulatory impact

Impact scale:

Rating Description Characteristics
High Severe impact Large breach, significant harm, major fines
Medium Significant impact Moderate breach, limited harm, operational disruption
Low Minor impact Small incident, minimal harm, easily contained

Step 7: Calculate Risk Level

Risk matrix:

Low Impact Medium Impact High Impact
High Likelihood Medium High Critical
Medium Likelihood Low Medium High
Low Likelihood Low Low Medium

Risk levels:

  • Critical: Immediate action required
  • High: Urgent remediation needed
  • Medium: Planned remediation
  • Low: Accept or monitor

Step 8: Document Risk Register

Create a risk register documenting all identified risks:

Risk ID Description Threat Vulnerability Likelihood Impact Risk Level Current Controls Remediation
R001 Unauthorized database access External attacker No MFA on DB Medium High High Passwords, network isolation Implement MFA
R002 Unencrypted backup exposure Data breach No encryption at rest Low High Medium Physical security Enable backup encryption
R003 Phishing compromise Social engineering Employee susceptibility High Medium High Annual training Increase training, add phishing simulation

Step 9: Develop Remediation Plan

For each identified risk, determine:

Element Description
Action Specific steps to address the risk
Owner Person responsible for remediation
Timeline Target completion date
Resources Budget, personnel, tools needed
Priority Based on risk level

Risk treatment options:

  • Mitigate: Implement controls to reduce risk
  • Transfer: Transfer risk to third party (insurance, vendor)
  • Accept: Accept risk with documented justification
  • Avoid: Eliminate the activity creating the risk

Remediation plan example:

Risk ID Action Owner Timeline Priority
R001 Implement MFA for database access CTO 30 days High
R002 Enable encryption on backup storage DevOps Lead 60 days Medium
R003 Implement quarterly phishing simulations Security Officer 90 days High

Step 10: Document and Maintain

Required documentation:

  • Risk assessment methodology
  • Scope and boundaries
  • Asset inventory
  • Threat and vulnerability analysis
  • Risk ratings and justifications
  • Remediation plan
  • Risk acceptance decisions (with rationale)
  • Review and update history

Retention: Maintain documentation for 6 years per HIPAA requirements.

Risk Assessment Template

Section 1: Assessment Information

Text
Assessment Date: [Date]
Assessment Lead: [Name/Title]
Participants: [Names/Titles]
Scope: [Description of what's covered]
Previous Assessment: [Date or N/A]

Section 2: ePHI Inventory

Text
For each system/location:
- System name
- Description
- ePHI types stored/processed
- Data volume
- Users with access
- Data flows (where data comes from/goes to)

Section 3: Threat Analysis

Text
For each threat:
- Threat description
- Threat source (natural, human, environmental)
- Affected systems
- Historical occurrence

Section 4: Vulnerability Analysis

Text
For each vulnerability:
- Vulnerability description
- Affected systems
- Discovery method
- Related threats

Section 5: Control Analysis

Text
For each control area:
- Control description
- Implementation status
- Effectiveness assessment
- Gaps identified

Section 6: Risk Analysis

Text
For each risk:
- Risk ID
- Risk description
- Associated threats and vulnerabilities
- Likelihood rating (with justification)
- Impact rating (with justification)
- Risk level
- Current controls

Section 7: Remediation Plan

Text
For each risk requiring remediation:
- Risk ID
- Remediation action
- Owner
- Timeline
- Resources required
- Success criteria

Section 8: Risk Acceptance

Text
For each accepted risk:
- Risk ID
- Risk description
- Justification for acceptance
- Approval authority
- Approval date
- Review date

Common Risk Assessment Mistakes

Mistake 1: Incomplete Scope

Problem: Missing ePHI locations (shadow IT, personal devices, etc.)

Solution: Conduct thorough data discovery, interview stakeholders, review data flows.

Mistake 2: Generic Threat Lists

Problem: Using generic threats without considering your specific environment.

Solution: Tailor threat analysis to your industry, size, and technical environment.

Mistake 3: Subjective Ratings

Problem: Inconsistent likelihood and impact ratings without criteria.

Solution: Define rating criteria before assessment, apply consistently.

Mistake 4: Assessment Without Action

Problem: Conducting assessment but not addressing findings.

Solution: Develop actionable remediation plan, track to completion.

Mistake 5: Point-in-Time Only

Problem: Treating risk assessment as one-time activity.

Solution: Establish triggers for reassessment, conduct annual reviews.

Risk Assessment Tools

Spreadsheet-Based

  • Simple for small organizations
  • Customizable
  • Low cost
  • Manual maintenance

GRC Platforms

  • Automated workflows
  • Centralized tracking
  • Reporting capabilities
  • Higher cost

HHS Resources

  • NIST SP 800-66 guidance
  • OCR audit protocol
  • HHS Security Risk Assessment Tool (SRA Tool)

Frequently Asked Questions

How often should we conduct risk assessments?

Conduct comprehensive assessment initially, then:

  • Annual review at minimum
  • When significant changes occur
  • After security incidents
  • When new systems handling ePHI are deployed

Who should conduct the risk assessment?

The Security Officer typically leads, with input from:

  • IT/Engineering team
  • Operations
  • Legal/Compliance
  • Executive leadership

External consultants can provide objectivity and expertise.

How detailed should the assessment be?

Detailed enough to:

  • Identify all ePHI locations
  • Document threats and vulnerabilities specific to your environment
  • Justify risk ratings
  • Drive meaningful remediation actions
  • Demonstrate compliance if audited

Can we use a vendor's risk assessment?

Cloud providers' assessments (SOC 2, etc.) can inform your assessment but don't replace it. You must assess:

  • How you configure and use their services
  • Your application layer security
  • Your policies and procedures
  • Your specific ePHI handling

What if we can't remediate all risks immediately?

Prioritize based on risk level:

  • Address critical/high risks urgently
  • Plan for medium risks
  • Accept or monitor low risks
  • Document all decisions and rationale

How Bastion Helps

Bastion helps technology companies conduct effective risk assessments:

  • Methodology: Proven risk assessment framework
  • Facilitation: Guide assessment workshops
  • Documentation: Comprehensive assessment documentation
  • Remediation planning: Actionable plans with prioritization
  • Ongoing support: Annual reassessments and updates

Ready to conduct your HIPAA risk assessment? Talk to our team


Sources