Skip to main content
HIPAA

HIPAA vs SOC 2: Differences and Which You Need

Published
Last updated
HIPAA
Two overlapping glowing circles, one with a medical shield and one with an audit report, with lock, key and log icons in the shared area, representing the overlap between HIPAA and SOC 2

HIPAA and SOC 2 come up together all the time, especially for health tech and SaaS vendors selling to US healthcare. They are different things: one is a law, the other is an attestation report. This guide explains what each covers, who asks for which, how much the controls overlap and how to do both without duplicating work. For hands-on help, see our HIPAA compliance consulting and SOC 2 consulting pages.

What is the difference between HIPAA and SOC 2?

HIPAA is a US law that protects health information and applies to covered entities and their business associates. SOC 2 is a voluntary attestation report, issued by a licensed CPA firm, on how well a service organisation's controls meet the Trust Services Criteria. You must comply with HIPAA if it applies; you choose to get SOC 2.

That difference shapes everything else:

  • HIPAA sets legal duties. The Security Rule (45 CFR Part 164 Subpart C) requires administrative (§164.308), physical (§164.310) and technical (§164.312) safeguards for electronic protected health information (ePHI), plus a risk analysis and six years of documentation (§164.316). There is no official HIPAA certification.
  • SOC 2 is a report. A licensed CPA firm tests your controls and issues a Type 1 report (design at a point in time) or a Type 2 report (operating effectiveness over an observation period). It covers security and, if you choose, availability, processing integrity, confidentiality and privacy.

Who asks for HIPAA and who asks for SOC 2?

US healthcare customers, such as hospitals, clinics, health plans and health tech companies, ask vendors handling PHI to sign a business associate agreement and show HIPAA compliance. SaaS and enterprise customers in every industry ask for a SOC 2 report during security reviews. Health tech vendors often get both requests from the same customer.

A typical pattern looks like this:

SituationWhat is usually requested
You handle PHI for a US healthcare customerA signed BAA and evidence of HIPAA safeguards
You sell SaaS to US enterprisesA SOC 2 report, often Type 2
You sell SaaS to US healthcareBoth: a BAA and HIPAA evidence, plus a SOC 2 report
A large hospital or payer is the customerSometimes HITRUST as well; see do I need HITRUST?

How much do HIPAA and SOC 2 overlap?

The controls overlap a great deal. Both expect risk assessment, access control, encryption, logging and monitoring, incident response, vendor management, security training and documented policies. HIPAA adds health-specific duties, such as business associate agreements, breach notification rules and individuals' rights over PHI, that a standard SOC 2 report does not cover.

Where they overlap:

  • Risk assessment. HIPAA requires a risk analysis; SOC 2 expects a risk assessment process.
  • Access control. Unique user IDs, least privilege and access reviews.
  • Encryption and transmission security.
  • Logging and monitoring. Audit controls under HIPAA; monitoring controls under SOC 2.
  • Incident response and business continuity.
  • Vendor management. Subcontractor BAAs under HIPAA; vendor risk under SOC 2.
  • Training and policies.

Where HIPAA goes further:

  • Business associate agreements, including with your own subcontractors.
  • Breach notification: individuals without unreasonable delay and no later than 60 days after discovery; HHS and the media when more than 500 residents of a state or jurisdiction are affected.
  • Privacy Rule duties around permitted uses and individuals' rights, where they apply to you.
  • Six-year documentation retention.

HIPAA vs SOC 2: side-by-side comparison

HIPAASOC 2
What it isUS lawVoluntary attestation report
Who it applies toCovered entities and business associatesAny service organisation that chooses it
Who assessesNo official certifier; an independent assessor can issue an assessment reportA licensed CPA firm
OutputYour risk analysis, safeguards and an assessment reportSOC 2 Type 1 or Type 2 report
ScopeePHI and the systems that handle itSystems in scope for the Trust Services Criteria you choose
Health-specific dutiesYes: BAAs, breach notification, PHI rightsNo
Typical requesterUS healthcare customersEnterprise customers in any industry

Where does SOC 2 fall short for HIPAA?

A SOC 2 report shows that your controls meet the Trust Services Criteria, which covers much of the HIPAA Security Rule, but it does not address every HIPAA requirement, such as business associate agreements and breach notification duties. So on its own it is not enough: you still need a HIPAA risk analysis and documented HIPAA safeguards.

A SOC 2 report is still valuable evidence for healthcare customers, because it shows an independent CPA firm has tested your controls. Pair it with HIPAA-specific documentation and the gap is small.

How do you do HIPAA and SOC 2 with one control set?

Build one set of controls, map each one to both the HIPAA Security Rule and the SOC 2 criteria, and collect evidence once. Then fill the HIPAA-only gaps, such as BAAs and breach notification procedures. CyberWave GRC maps shared controls across SOC 2, ISO 27001, HIPAA and HITRUST so your team builds each control once.

A practical order:

  1. Scope both together. Draw one data flow showing ePHI and the systems in your SOC 2 scope.
  2. Run one risk assessment that meets the HIPAA risk analysis requirement and feeds SOC 2.
  3. Write one policy set that covers both, with HIPAA-specific sections where needed.
  4. Map controls to each framework in a single register.
  5. Collect evidence once, in a form both the CPA firm and a HIPAA assessor can use.
  6. Close the HIPAA-only items: BAAs, breach notification and documentation retention.

Can you add HIPAA to a SOC 2 report?

Some CPA firms can extend a SOC 2 engagement to report on HIPAA Security Rule requirements as well, often called a SOC 2+ HIPAA report. Whether this is available, what it covers and how it is worded is the CPA firm's decision, so discuss it during audit planning, before your readiness work is finished.

A combined report can reduce the number of separate reviews healthcare customers ask for. It does not replace your own HIPAA duties, such as signing BAAs or meeting breach notification deadlines. If your customers want a CPA opinion specifically on HIPAA, read HIPAA audit vs AT-C 315.

Which should you do first, HIPAA or SOC 2?

If you handle PHI for a US healthcare customer, HIPAA comes first, because it is a legal duty and your customer will ask for a BAA before sharing any data. If your buyers are mainly enterprises outside healthcare, start with SOC 2. Many health tech vendors work on both at once using one control set.

Things to weigh:

  • Who is asking right now, and what they need to see to sign.
  • Timelines. A SOC 2 Type 1 takes about 8 to 10 weeks if basic controls are already in place, or 3 to 4 months if you're starting from scratch.
  • Budget. Doing both together costs less than doing them one after the other, because the shared controls are built once.

For more on SOC 2 report types, see SOC 2 Type 1 vs Type 2. For cost planning, see HIPAA compliance cost.

Frequently asked questions

No. A SOC 2 report shows a licensed CPA firm has tested your controls against the Trust Services Criteria, which covers much of the HIPAA Security Rule. It does not cover every HIPAA duty, such as business associate agreements and breach notification. You still need a HIPAA risk analysis, documented safeguards and HIPAA-specific procedures.

Partly. Some CPA firms can extend a SOC 2 engagement to report on HIPAA Security Rule requirements too, often called a SOC 2+ HIPAA report. Whether that is available is the CPA firm's decision. Either way, CyberWave GRC prepares one control set and one evidence library so both reviews draw on the same work.
Hi! I'm your AI Assistant 💬