HIPAA Security Rule: What Healthcare Organizations Must Implement

Compliance

The HIPAA Security Rule requires administrative, physical, and technical safeguards for electronic protected health information. Here is what covered entities and business associates need to know.

G
GRC2 Advisory Team
••5 min read
HIPAA Security Rule: What Healthcare Organizations Must Implement

Healthcare organizations face a unique security challenge: the data they handle is among the most sensitive in existence, the regulatory framework governing it is among the most prescriptive, and the consequences of a breach — financial, reputational, and operational — are among the most severe.

The HIPAA Security Rule establishes the minimum security requirements for protecting electronic protected health information (ePHI). Understanding what it requires — and how to implement it effectively — is essential for every covered entity and business associate. Note that HHS published a significant update to the Security Rule in 2025, with a compliance deadline projected around July 2027 — see our post on the 2025 HIPAA Security Rule update for what is changing and how to prepare.

Who Must Comply

Covered entities include healthcare providers who transmit health information electronically, health plans, and healthcare clearinghouses.

Business associates are organizations that create, receive, maintain, or transmit ePHI on behalf of a covered entity. This includes a wide range of vendors: EHR vendors, billing companies, cloud hosting providers, IT managed service providers, and many others.

Business associates must sign a Business Associate Agreement (BAA) with the covered entity and are directly liable for HIPAA compliance under the HITECH Act.

The Three Safeguard Categories

The HIPAA Security Rule organizes its requirements into three categories of safeguards. Each category contains a mix of required and addressable specifications.

Required specifications must be implemented. There is no flexibility.

Addressable specifications must be implemented if reasonable and appropriate for the organization's size, complexity, and capabilities. If an addressable specification is not implemented, the organization must document why and implement an equivalent alternative measure.

Administrative Safeguards

Administrative safeguards are the policies, procedures, and processes that govern how ePHI is managed and protected. They represent the largest category of HIPAA Security Rule requirements.

Key requirements include:

Security Management Process (Required). Implement policies and procedures to prevent, detect, contain, and correct security violations. This includes a risk analysis and risk management program.

Risk Analysis (Required). Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI. This is one of the most frequently cited deficiencies in HIPAA enforcement actions.

Risk Management (Required). Implement security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level.

Workforce Training (Addressable). Implement a security awareness and training program for all workforce members.

Contingency Plan (Required). Establish policies and procedures for responding to an emergency or other occurrence that damages systems containing ePHI. This includes data backup, disaster recovery, and emergency mode operation plans.

Physical Safeguards

Physical safeguards govern physical access to systems that contain ePHI.

Facility Access Controls (Addressable). Implement policies and procedures to limit physical access to electronic information systems and the facilities in which they are housed.

Workstation Use (Required). Implement policies and procedures that specify the proper functions to be performed, the manner in which those functions are to be performed, and the physical attributes of the surroundings of a specific workstation.

Device and Media Controls (Required). Implement policies and procedures that govern the receipt and removal of hardware and electronic media that contain ePHI into and out of a facility.

Technical Safeguards

Technical safeguards are the technology and related policies and procedures that protect ePHI and control access to it.

Access Control (Required). Implement technical policies and procedures for electronic information systems that maintain ePHI to allow access only to those persons or software programs that have been granted access rights.

Audit Controls (Required). Implement hardware, software, and procedural mechanisms that record and examine activity in information systems that contain or use ePHI.

Integrity (Addressable). Implement policies and procedures to protect ePHI from improper alteration or destruction.

Transmission Security (Addressable). Implement technical security measures to guard against unauthorized access to ePHI that is being transmitted over an electronic communications network.

The Risk Analysis: The Most Critical Requirement

The risk analysis is the foundation of HIPAA Security Rule compliance. It is also the most frequently cited deficiency in OCR enforcement actions and audits.

A compliant risk analysis must:

  • Identify the scope of the analysis (all ePHI, regardless of format or location)
  • Collect data on the systems, applications, and processes that create, receive, maintain, or transmit ePHI
  • Identify and document potential threats and vulnerabilities
  • Assess current security measures
  • Determine the likelihood of threat occurrence
  • Determine the potential impact of threat occurrence
  • Determine the level of risk
  • Finalize documentation and review periodically

The risk analysis is not a one-time exercise. It must be reviewed and updated periodically and when environmental or operational changes occur.

Common HIPAA Security Rule Deficiencies

Based on OCR enforcement actions and audit findings, the most common deficiencies are:

  • Incomplete or outdated risk analysis
  • Insufficient risk management following the risk analysis
  • Lack of information system activity review
  • Inadequate access controls
  • Missing or inadequate workforce training
  • Failure to execute BAAs with all business associates
  • Inadequate contingency planning

The GRC2 Approach to HIPAA Compliance

We help covered entities and business associates build HIPAA compliance programs that go beyond checkbox compliance to actually protect ePHI. We start with a comprehensive risk analysis, build a risk management program based on the findings, and implement the administrative, physical, and technical safeguards appropriate to the organization's risk profile.

HIPAA compliance is not a destination — it is an ongoing program. We help organizations build the governance structures and operational processes to sustain it.

Related reading: The 2025 HIPAA Security Rule update — what changes before July 2027 | SOC 2 compliance guide | Building a security program from scratch | GRC2 compliance readiness services

Explore Topics

#HIPAA#healthcare security#PHI#ePHI#covered entity#business associate
G

Written by

GRC2 Advisory Team

Content creator and writer sharing insights and stories.