Compyl

The Complete Guide to HIPAA Compliance

June 04, 2026
Regulation · HIPAA

The Complete Guide to HIPAA Compliance

By Compyl ResearchLast updated: November 9, 202616 min read

HIPAA compliance means meeting the Privacy, Security and Breach Notification Rules that HHS enforces for covered entities (health plans, healthcare clearinghouses and most providers) and their business associates. The Security Rule requires administrative, physical and technical safeguards for electronic protected health information, starting with an accurate and thorough risk analysis. A major Security Rule update was proposed in January 2025; final action is now projected for July 2027.

Key takeaways
  • HIPAA applies to covered entities and business associates. Vendors that create, receive, maintain or transmit PHI for a covered entity are directly liable under the Security Rule.
  • The risk analysis is the foundation of the Security Rule and the most frequently cited gap in OCR enforcement.
  • Breach deadlines are fixed: notify individuals and, for 500+ people, HHS and the media within 60 days of discovery; report smaller breaches to HHS within 60 days of the end of the calendar year.
  • 2024 set a record: 725 large breaches affecting more than 275 million people, 81% from hacking and about 30% at business associates.
  • The proposed Security Rule overhaul would make MFA, encryption, network segmentation, annual penetration tests and tested incident response plans explicit. Final action is projected for July 2027; adopting those controls now is good practice either way.

Who has to comply with HIPAA?

HIPAA’s Administrative Simplification rules apply to two groups:

Group Who it includes Obligations
Covered entities Health plans, healthcare clearinghouses, and providers that conduct standard electronic transactions such as claims Privacy, Security and Breach Notification Rules in full
Business associates Vendors that create, receive, maintain or transmit PHI on a covered entity’s behalf: billing, EHR and cloud hosting, IT services, analytics, health tech platforms, law and consulting firms Security Rule in full, parts of the Privacy Rule, breach notice to the covered entity, BAAs with their own subcontractors
Subcontractors Vendors of business associates that handle PHI Treated as business associates

A cloud provider that stores encrypted PHI is still a business associate even if it never views the data. See who HIPAA applies to.

What do the HIPAA rules require?

Rule What it governs Key requirements
Privacy Rule Uses and disclosures of PHI in any form Minimum necessary standard, notice of privacy practices, patient rights to access and amend records, authorizations
Security Rule Electronic PHI (ePHI) Risk analysis and risk management; administrative, physical and technical safeguards; policies and documentation retained six years
Breach Notification Rule Unsecured PHI that is acquired, accessed, used or disclosed impermissibly Four-factor risk assessment; notice to individuals, HHS and sometimes media
Enforcement Rule Investigations and penalties Civil money penalties in four tiers based on culpability, adjusted annually for inflation

What safeguards does the HIPAA Security Rule require?

The Security Rule groups its standards into three safeguard types. Some implementation specifications are “required”; others are “addressable,” which means you must implement them, implement an equivalent, or document why neither is reasonable. Addressable does not mean optional.

Safeguard Standards include What it looks like in practice
Administrative Security management process (risk analysis, risk management, sanctions, activity review), assigned security official, workforce security, access management, awareness training, incident procedures, contingency plan, evaluation, BAAs A maintained risk register, a named security officer, onboarding and offboarding, training records, an incident response plan, backups and disaster recovery, annual evaluation
Physical Facility access controls, workstation use and security, device and media controls Badge access, screen locks, encrypted laptops, media disposal records
Technical Access control (unique IDs, emergency access, automatic logoff, encryption), audit controls, integrity, authentication, transmission security SSO and MFA, audit logging, integrity checks, TLS for data in transit, encryption at rest

The risk analysis under 164.308(a)(1) is the cornerstone. OCR expects an accurate and thorough assessment of risks to all ePHI the organization creates, receives, maintains or transmits, updated when systems or operations change. A one-time spreadsheet rarely meets that bar. See the HIPAA IT compliance checklist.

What are the HIPAA breach notification deadlines?

Who must be notified When Applies to
Affected individuals Without unreasonable delay, no later than 60 days after discovery All breaches of unsecured PHI
HHS (500 or more people) Within 60 days of discovery, via the OCR breach portal Large breaches
HHS (fewer than 500 people) Within 60 days of the end of the calendar year in which the breach was discovered Small breaches, logged and reported annually
Prominent media Within 60 days of discovery Breaches affecting more than 500 residents of a state or jurisdiction
Covered entity (from a business associate) Without unreasonable delay, no later than 60 days after discovery; BAAs often set shorter windows Breaches at a business associate

Encrypted PHI that meets HHS guidance is not “unsecured,” which is one reason encryption is the most valuable addressable specification to implement. Timelines are summarized from HIPAA Journal; see also how long you have to report.

What does the 2024 breach data show?

According to HIPAA Journal’s analysis of HHS data, 725 breaches of 500 or more records were reported to OCR in 2024, affecting more than 275 million people. Hacking and IT incidents accounted for 589 of them (81.2%), and about 30% occurred at business associates. Two lessons follow for compliance programs: technical safeguards such as MFA, patching and backups now matter more than physical loss, and vendor oversight is a core Security Rule activity, not an afterthought.

Where does the HIPAA Security Rule update stand?

HHS published a notice of proposed rulemaking in the Federal Register on January 6, 2025. Among other changes, it would remove the distinction between required and addressable specifications and make several practices explicit, including multi-factor authentication, encryption, network segmentation, annual penetration testing, more prescriptive risk analyses, written incident response plans tested at least annually, and verification of business associates’ safeguards. HHS had targeted May 2026 for a final rule; the federal regulatory agenda now projects July 2027.

No new compliance date exists yet, but the proposed controls already appear in customer security reviews and cyber insurance applications. Our HIPAA Security Rule update readiness guide walks through each proposed change.

What should a business associate agreement include?

A BAA is required before a business associate handles PHI. At minimum it should:

  • Describe permitted and required uses and disclosures of PHI.
  • Require appropriate safeguards and compliance with the Security Rule.
  • Require reporting of security incidents and breaches, with a defined timeline.
  • Flow the same obligations down to subcontractors.
  • Give individuals access to and amendment of their PHI where applicable.
  • Make books and records available to HHS.
  • Require return or destruction of PHI at termination.

A signed BAA is necessary but not sufficient. Covered entities should also tier business associates by risk, review their security evidence, and monitor them between reviews. See our guide to third-party risk management in healthcare.

How do you build a HIPAA compliance program step by step?

  1. Inventory PHI. Map where PHI and ePHI are created, stored, processed and transmitted, including SaaS tools and vendors.
  2. Appoint privacy and security officials. One person can hold both roles in smaller organizations.
  3. Conduct the risk analysis. Assess threats and vulnerabilities to ePHI and rate likelihood and impact.
  4. Implement safeguards. Prioritize MFA, encryption, logging, backups, access reviews and endpoint protection.
  5. Write and adopt policies. Cover each standard, and keep documentation for six years.
  6. Execute BAAs and assess vendors. Tier business associates and review their controls.
  7. Train the workforce. At onboarding and periodically, with records.
  8. Prepare for incidents. Build and test a response plan that includes the breach risk assessment and notification steps.
  9. Monitor and evaluate. Review controls continuously and evaluate the program at least annually or after major change.

Many healthcare organizations also pursue HITRUST or SOC 2 for customers. Mapping HIPAA to those frameworks in one control library avoids running three programs. See HITRUST vs ISO 27001 and our post on GRC challenges for mid-market healthcare.

Frequently asked questions

Who must comply with HIPAA?
Covered entities, meaning health plans, healthcare clearinghouses and providers that conduct standard electronic transactions, and their business associates and subcontractors that create, receive, maintain or transmit PHI on their behalf.
What are the three types of HIPAA safeguards?
Administrative safeguards such as risk analysis, training and contingency planning; physical safeguards such as facility and device controls; and technical safeguards such as access control, audit logging, integrity and transmission security.
How long do you have to report a HIPAA breach?
Notify affected individuals without unreasonable delay and no later than 60 days after discovery. Breaches affecting 500 or more people must also be reported to HHS, and to the media for more than 500 residents of a state, within 60 days. Smaller breaches are reported to HHS within 60 days of the end of the calendar year.
Is the new HIPAA Security Rule final?
No. HHS proposed the update in January 2025. Final action is now projected for July 2027, so there is no new compliance date yet.
Does HIPAA require encryption?
Under the current rule, encryption is an addressable specification: you must implement it, an equivalent, or document why neither is reasonable. The proposed update would make it a required standard. Encrypted PHI that meets HHS guidance is not considered unsecured for breach notification.
Is there an official HIPAA certification?
No. HHS does not certify HIPAA compliance. Organizations demonstrate it through risk analyses, documentation and often third-party assessments such as HITRUST or SOC 2 reports mapped to HIPAA.
How long must HIPAA documentation be kept?
Six years from the date of creation or the date it was last in effect, whichever is later.

Run HIPAA, HITRUST and SOC 2 From One Program With Compyl

Compyl keeps your HIPAA risk analysis live in a risk register, collects Security Rule evidence from 125+ in-house integrations, manages business associate risk, and maps every control across HIPAA, HITRUST, SOC 2 and 70+ other frameworks.

Request a demo →

About this guide. By Compyl Research. Last updated November 9, 2026. This is general information, not legal advice — consult counsel for your specific obligations. Compyl is an AI-powered, agentic GRC platform built by CISOs.


Monitoring thousands of environments daily
By clicking “Accept”, you agree to the use of cookies on your device in accordance with our Privacy and Cookie policies