Opens in a new tab
Soc 2 vs hipaa how the two compliance standards differ

SOC 2 vs HIPAA: How the Two Compliance Standards Differ

Last Updated: October 30, 2026

Quick Summary

The main difference is enforceability: HIPAA is a federal law that governs protected health information, while SOC 2 is a voluntary assurance framework that customers often request. Organizations handling PHI as covered entities or business associates must meet HIPAA, but soc 2 hipaa compliance overlaps in shared controls such as risk analysis, access control and audit logging.

  • HIPAA is mandatory for covered entities and business associates that handle protected health information.
  • SOC 2 is voluntary and is evaluated by an independent CPA firm against the Trust Services Criteria.
  • A SOC 2 report does not satisfy HIPAA by itself, so HIPAA-specific documentation is still required.
  • Many controls such as risk analysis, access control and audit logging can be built once and mapped to both frameworks.
  • BAAs, the Notice of Privacy Practices and breach notification procedures remain HIPAA-specific obligations.

Table of Contents

What HIPAA Compliance Is and Who It Applies To

Understanding HIPAA compliance starts with a simple fact: HIPAA compliance is a legal requirement for covered entities and business associates that handle protected health information (PHI). Readers who need HIPAA compliance services can review HIPAA compliance services for medical practices. Department of Health and Human Services, Office for Civil Rights (HHS OCR), through HHS Office for Civil Rights HIPAA guidance.

A common misconception is that HIPAA applies to any company that touches health data. It does not. HIPAA’s scope is defined by the relationship to a covered entity, not by the subject matter of the data. That distinction determines whether a BAA is required, whether OCR has jurisdiction, and whether a SOC 2 report is the right assurance tool.

The three categories of covered entities

HIPAA defines a covered entity as one of three types of organizations:

  • Health plans, insurers, employer-sponsored group health plans, HMOs, and government programs that pay for care.
  • Healthcare clearinghouses, entities that process nonstandard health information into standard transactions (for example, billing clearinghouses).
  • Healthcare providers, doctors, dentists, clinics, hospitals, and other providers that transmit health information electronically in connection with a standard transaction, such as an electronic claim.

The provider prong is the one most small organizations misjudge. A practice that bills electronically is generally a covered entity even if it is a solo or small group.

Business associates and the BAA requirement

A business associate is any person or vendor that creates, receives, maintains or transmits PHI on a covered entity’s behalf. That includes most managed IT providers, cloud hosting vendors, billing services, transcription services, and EHR support contractors.

If a vendor touches PHI, a Business Associate Agreement (BAA) must be in place before access begins. Without one, the covered entity is out of compliance even if its own systems are secure, and the vendor may face direct enforcement.

What HIPAA does not cover

The limits of HIPAA matter as much as its reach. HIPAA does not generally apply to:

  • Consumer health apps and wearables sold directly to individuals, unless the vendor is acting as a business associate.
  • Employers acting in their employment capacity, such as wellness programs that are not part of a group health plan.
  • Life insurers, workers’ compensation carriers, and most schools and school districts.

Some of these organizations are regulated by other authorities, the Federal Trade Commission’s Health Breach Notification Rule, for example, can apply to vendors of personal health records outside HIPAA. A company can handle health-related data and still not be HIPAA-regulated, which is precisely where a SOC 2 report often becomes the customer-facing assurance mechanism.

The HIPAA Privacy Rule and Security Rule

HIPAA has two rules that matter most for IT teams. The Privacy Rule governs how PHI may be used and disclosed. The Security Rule governs the technical, physical and administrative safeguards that protect electronic PHI (ePHI).

The Security Rule is the one most IT managers deal with directly. It requires a documented risk analysis, access controls, audit logging, encryption where appropriate, and backup and contingency planning.

Pro Tip
Before assuming HIPAA applies, confirm your status. If you are a covered entity or business associate, HIPAA is mandatory. If you handle health-adjacent data outside those categories, HIPAA may not apply, but customer contracts and other regulators may still require SOC 2 or similar assurance.
::: Navigating these overlapping requirements remains essential for organizations striving to maintain robust health data security in an increasingly complex digital landscape.

A quick decision path by organization type

  • Hospital, clinic, dental or medical practice billing electronically, covered entity; HIPAA mandatory; BAA required with every PHI-touching vendor.
  • Billing service, MSP, EHR support, transcription, cloud host handling PHI, business associate; HIPAA mandatory; BAA required with each covered entity customer.
  • SaaS vendor selling to healthcare customers but not handling PHI, not a business associate; HIPAA generally not applicable; SOC 2 commonly requested by customers.

What SOC 2 Compliance Is and Who It Applies To

SOC 2 is a voluntary assurance framework, not a law. It was developed by the American Institute of CPAs (AICPA) for service organizations that store or process customer data. A licensed CPA firm examines the organization’s controls and issues a report describing whether those controls meet the criteria.

SOC 2 is most common among SaaS companies, data hosting providers, and professional services firms that handle client data, and organizations that must meet soc 2 hipaa compliance often find the two frameworks overlap in practice. Many enterprise customers ask for a SOC 2 report before signing a contract, making the framework a sales requirement rather than a regulatory one.

The five Trust Services Criteria

SOC 2 reports are organized around five Trust Services Criteria: security, availability, processing integrity, confidentiality and privacy. Security is required in every SOC 2 report. The other four are optional and chosen based on the services the organization provides.

A law firm or financial advisory firm will often include confidentiality. A cloud provider with uptime commitments will usually add availability.

Mandatory Law Versus Voluntary Assurance

The core difference is enforceability. HIPAA is federal law; a covered entity that fails to meet it can face civil penalties from HHS OCR and, in some cases, state attorneys general.

This distinction shapes how each framework should be approached. HIPAA compliance is a baseline you must meet. SOC 2 is a credential you choose to earn and then maintain.

Here is a quick summary:

Factor HIPAA SOC 2
Legal status Federal law Voluntary framework
Enforced by HHS Office for Civil Rights Not enforced; customers evaluate reports
Governs Protected health information Customer data, against the Trust Services Criteria
Verification Self-attestation plus OCR investigation Independent CPA examination
Typical trigger Handling PHI as a provider or vendor Customer or contract requirement

HIPAA Compliance Requirements and SOC 2 Compliance Requirements Side by Side

HIPAA compliance requirements are defined by the Security Rule’s standards and implementation specifications. Key requirements include a risk analysis, a risk management plan, workforce training, access controls, audit controls, integrity protections, and transmission security, each documented.

SOC 2 compliance requirements are defined by the Trust Services Criteria and the controls the organization describes in its system description. The auditor tests whether those controls operate effectively over a period of time, usually 3 to 12 months for a Type II report.

Get In Touch →

The practical difference: HIPAA tells you what must be protected. SOC 2 asks you to describe how you protect it, then prove it worked.

SOC 2 Audit vs. HIPAA Audit: What Evidence Each Requires

There is no HIPAA certification audit. HHS does not issue HIPAA certificates. Compliance is demonstrated through documentation, and OCR may investigate after a complaint or breach. The evidence you need is your risk analysis, policies, training records, access logs, and business associate agreements.

A SOC 2 examination is different in kind: an independent CPA firm tests your controls and issues an opinion under AICPA attestation standards, with the conclusion limited to the scope described in the report. Understanding what the report does and does not establish is essential before treating it as proof of security.

What a SOC 2 examination actually evaluates

A SOC 2 examination evaluates two things together: the suitability of the controls described in the organization’s system description, and their operating effectiveness against the selected Trust Services Criteria. The auditor does not certify the organization as secure; the auditor opines on whether the controls, as described and tested, met the criteria over the relevant period.

That means the report is only as meaningful as its scope. A security-only report says nothing about availability, confidentiality, processing integrity or privacy, and a report that excludes a business unit or system does not cover it. Check the system description, criteria selected, period covered, and any complementary user entity controls before relying on the report.

Type I versus Type II reports

  • Type I evaluates the fairness of the system description and the suitability of control design at a single point in time. It does not test whether controls operated effectively over a period.
  • Type II evaluates design and operating effectiveness across an observation window, commonly 3 to 12 months. It is the report enterprise customers usually request because it provides evidence of sustained operation.

A Type I report is a reasonable first milestone for an organization new to SOC 2, but it is not a substitute for a Type II when a customer contract requires proof of operating effectiveness.

What a SOC 2 report does not establish

A SOC 2 report is not a government certification, not a license, and not a blanket guarantee of security. It does not establish compliance with HIPAA, the Gramm-Leach-Bliley Act, or any other statute, does not eliminate the need for customer due diligence, and does not transfer risk: the report describes controls, but the customer still must evaluate whether those controls address its own obligations.

A SOC 2 report does not satisfy HIPAA by itself. Auditors evaluate against the Trust Services Criteria, not the HIPAA Security Rule, so you still need HIPAA-specific documentation, including a Security Rule risk analysis and BAAs.

 

Evidence that overlaps and evidence that does not

For most organizations, the evidence overlaps substantially. A well-documented HIPAA risk analysis can feed directly into SOC 2 risk assessment work. Access reviews, backup testing, and incident response records serve both.

Control area HIPAA evidence SOC 2 evidence Reusable?
Risk analysis Documented Security Rule risk analysis Risk assessment supporting the system description Yes, with mapping
Access control Unique user IDs, access authorization records Logical access controls, provisioning and deprovisioning evidence Yes
Audit logging Audit controls and log review records Monitoring and logging evidence tied to criteria Yes
Encryption Encryption decision and rationale Encryption controls where in scope Yes
Backup and recovery Contingency plan and test records Availability criteria evidence, if selected Yes, if availability is in scope
BAAs Signed BAAs with PHI-touching vendors Vendor management evidence Partially; BAAs are HIPAA-specific
Breach notification HIPAA breach notification procedures and logs Incident response evidence Partially; notification duties differ
Privacy notices Notice of Privacy Practices Privacy criteria evidence, if selected No; HIPAA-specific

The practical takeaway: build the control once, document it once, and map the evidence to both frameworks.

Compliance officers reviewing audit evidence for SOC 2 HIPAA compliance in a bright office conference room
Compliance officers reviewing audit evidence for SOC 2 HIPAA compliance in a bright office conference room

SOC 2 and HIPAA Compliance Checklist for Overlapping Controls

Many healthcare and SaaS organizations need both. A practical starting point is to map shared controls once and reuse the evidence. For a deeper walkthrough, see the HIPAA IT compliance checklist covering ePHI security, access, backup and MFA. Use this checklist as a planning tool:

  • Complete a documented risk analysis covering ePHI and customer data
  • Enforce multi-factor authentication on all administrative and remote access
  • Review user access quarterly and remove stale accounts

Watch out: a SOC 2 report does not satisfy HIPAA by itself. Auditors evaluate against the Trust Services Criteria, not the HIPAA Security Rule, so you still need HIPAA-specific documentation.

Booking a Compliance Readiness Review for Your Practice or Firm

Choosing between these frameworks, or deciding how to meet both, depends on your data, contracts and current controls.

AI Managed IT Services works with compliance-sensitive organizations. Contact us to discuss how our services can support your HIPAA or SOC 2 compliance needs.

If your IT provider has never walked you through HIPAA obligations, it is worth asking the hard questions. Use these ten questions for evaluating your IT provider’s HIPAA compliance before you book.

Contact AI Managed IT Services to discuss your compliance needs.

Frequently Asked Questions

Does SOC 2 compliance mean a company is HIPAA compliant?

No. SOC 2 is a voluntary attestation based on the AICPA Trust Services Criteria, and a SOC 2 report does not satisfy HIPAA’s Privacy Rule, Security Rule or Breach Notification Rule. HIPAA is a federal law enforced by the HHS Office for Civil Rights and applies only to covered entities and their business associates. A vendor with a clean SOC 2 Type II report may still need a signed business associate agreement and documented HIPAA safeguards before it can handle protected health information. Organizations that handle PHI should assess HIPAA separately, even when SOC 2 evidence is already in place.

Can a healthcare organization need both SOC 2 and HIPAA compliance?

Yes. A healthcare organization is legally obligated to meet HIPAA, while SOC 2 is often requested by customers, payers or partners as proof of independently examined controls. Many health technology vendors pursue both: HIPAA for the legal requirements on PHI, and SOC 2 Type II to give customers third-party evidence that access control, logging and change management operate effectively over time. The two efforts share a large body of safeguards, so evidence collected once can often support both reviews.

What is the difference between a SOC 2 audit and a HIPAA audit?

A SOC 2 audit is an independent examination by a licensed CPA firm that issues a report on the design (Type I) or design and operating effectiveness over a period (Type II) of controls against the Trust Services Criteria. A HIPAA audit has no single standard format; HHS may conduct compliance reviews, and organizations often run internal risk analyses against the Security Rule. Neither is a substitute for the other, and a SOC 2 report is not a HIPAA attestation.

Which is more demanding, SOC 2 or HIPAA?

It depends on the organization. HIPAA is mandatory for covered entities and business associates, and violations can bring civil monetary penalties and corrective action plans, so its legal scope is non-negotiable. SOC 2 has no legal mandate but requires an external CPA examination and a sustained period of evidence, which can make Type II work demanding in its own way. For a practice that handles PHI, HIPAA is the baseline requirement; SOC 2 becomes the added burden mainly when customers request it.

Call 310-444-4343

Let's discuss how we can protect your business from these common cybersecurity mistakes.
Call 310-444-4343