For a health-tech vendor, HITRUST vs SOC 2 is usually not an either-or. A hospital or payer sends a security questionnaire, and depending on who is asking you end up needing a SOC 2 report, HITRUST certification, or proof of HIPAA compliance, sometimes all three. They are different kinds of thing: HIPAA is a law, SOC 2 is an attestation by a CPA firm, and HITRUST is a certification against a defined control set. This guide explains what each one is, how they overlap, and the part that matters for scheduling, which is the penetration testing each expects. The good news is that one well-scoped test can serve all three.
If you already know which framework you need, our HITRUST penetration testing, SOC 2 penetration testing and HIPAA penetration testing pages cover scoping and fixed prices for each.
HITRUST vs SOC 2 vs HIPAA at a glance
| HIPAA | SOC 2 | HITRUST | |
|---|---|---|---|
| What it is | A US federal law (the Security Rule for ePHI) | An attestation report by a CPA firm against the Trust Services Criteria | A certification against the HITRUST CSF |
| Who checks you | No one certifies; HHS OCR enforces through investigations | Your audit firm | A HITRUST Authorized External Assessor, then HITRUST quality assurance |
| Result | Compliance, self-attested | An attestation report (Type I or Type II) | A certification, valid 1 or 2 years |
| Controls | Required and addressable safeguards, method left to you | Criteria you map your own controls to | A defined set of requirement statements |
| Penetration testing | Not named in the current rule; a proposed rule would require it annually | Not named; auditors expect it as evidence | Where your requirement statements call for it |
| Time to a first result | Nothing to wait for; the obligation applies from the day you handle ePHI | Type I is a point in time; Type II needs an observation period, usually 3 to 12 months | e1 around 30 days on average, i1 6 to 12 months for most companies, r2 the longest |
| What drives cost | Your own safeguards and risk analysis | The audit firm’s fee, by criteria and scope | The assessor’s fee, by level: e1 lowest, r2 highest |
HITRUST vs HIPAA: the difference in three sentences
HIPAA is a federal law that tells covered entities and their business associates to protect ePHI; HHS OCR enforces it, and there is no certificate at the end. HITRUST is a private certification: an Authorized External Assessor tests you against the HITRUST CSF, and HITRUST reviews the work before it certifies. HIPAA is mandatory if you handle ePHI and HITRUST is voluntary, and buyers ask for HITRUST because it is the independent check that HIPAA itself does not provide.
| HIPAA | HITRUST | |
|---|---|---|
| Type | Federal law (Privacy, Security and Breach Notification Rules) | Private certification against the HITRUST CSF |
| Mandatory | Yes, for covered entities and business associates | No, unless a customer contract requires it |
| Who checks you | HHS OCR, after a complaint, a breach or an audit | An Authorized External Assessor, then HITRUST quality assurance |
| What you receive | Nothing; compliance is self-attested | A certification valid 1 year (e1, i1) or 2 years (r2) |
| How specific it is | Required and addressable safeguards, method left to you | A defined set of requirement statements |
| What a hospital asks you for | A signed business associate agreement | The certification letter or the validated report |
The business associate agreement is the piece of hospital vendor review that sits under HIPAA and not under HITRUST or SOC 2. The Security Rule lets a covered entity hand ePHI to a vendor only if it “obtains satisfactory assurances” that the vendor will safeguard it, documented in a written contract (45 CFR 164.308(b)). Expect to sign one before any ePHI moves, whatever report or certificate you hold. A HITRUST letter or a SOC 2 report does not replace it.
HIPAA: the law underneath
HIPAA is the baseline for anyone handling electronic protected health information (ePHI). It is a federal law, not a certification, and that distinction trips vendors up. There is no HIPAA certificate. HHS is explicit: it “does not endorse or otherwise recognize private organizations’ ‘certifications’ regarding the Security Rule,” and such certifications “do not absolve covered entities of their legal obligations” (HHS FAQ). A vendor can say it is HIPAA compliant, but nobody independent has confirmed it, which is exactly why buyers ask for SOC 2 or HITRUST on top. That is the short answer to HITRUST vs HIPAA: HIPAA is the obligation, and HITRUST is one independently checked way to show how you meet it.
For the obligation itself, our HIPAA compliance checklist lists what the rules require, safeguard by safeguard.
On testing, the Security Rule in force today requires a risk analysis and a periodic evaluation of safeguards, and leaves the method to you; it does not use the words “penetration test.” A rule proposed in January 2025 would change that by requiring penetration testing at least every twelve months and vulnerability scanning at least every six months, but as of November 2026 it remains proposed. Our page on HIPAA penetration testing requirements covers what is required now versus proposed, and what OCR actually penalizes, and our guide to the HIPAA technical safeguards shows which of the five technical standards a test gives evidence for.
SOC 2: an attestation, not a certificate
SOC 2 is a report produced by a CPA firm under AICPA standards, against the Trust Services Criteria in five categories: security, availability, processing integrity, confidentiality and privacy. Security is the one everyone includes; the rest are added when they fit the service. It results in an attestation report, not a certificate, and it comes in two forms:
- Type I examines the design of your controls at a single point in time.
- Type II examines whether those controls operated effectively over a period, usually 3 to 12 months.
SOC 2 does not name penetration testing as a required control, but in practice it is one of the most common ways to evidence the security criterion, and most auditors ask for a recent report. The timing is what catches people out, especially for Type II, where the test needs to land inside the observation period with time left to fix and retest. Our SOC 2 penetration testing requirements guide walks through the Type I versus Type II timing in detail, and the SOC 2 evidence checklist lists every item an auditor asks for.
SOC 2 vs HIPAA: does a SOC 2 report cover HIPAA?
Not on its own. SOC 2 is a voluntary attestation against the Trust Services Criteria, and HIPAA is a law with its own required safeguards; a standard SOC 2 report does not say whether you meet them. The two overlap on access control, logging, encryption, risk assessment and incident response, so most SOC 2 control work also counts toward the Security Rule. HIPAA still has requirements with no SOC 2 equivalent, such as business associate agreements, breach notification and the Privacy Rule.
Audit firms close the gap with a SOC 2 report that includes a HIPAA mapping, often sold as “SOC 2 + HIPAA”. AICPA guidance allows a service organization to engage the auditor to “examine and report on subject matters in addition” to the standard system description and controls, measured against additional criteria (AICPA). In practice the CPA firm tests your controls against the HIPAA Security Rule requirements in the same examination and reports on both. The result is still an auditor’s opinion, not a HIPAA certificate, but it gives a hospital’s vendor risk team one document that answers both questions. If you handle ePHI and SOC 2 is your first report, raise the HIPAA mapping when you scope the audit, because it is easier to include at the start than to add later.
HITRUST: a certification with three levels
HITRUST offers what HIPAA and SOC 2 do not: a certification with a defined control set, testing by an External Assessor and central quality assurance by HITRUST. The HITRUST CSF (v11.9.0 as of November 2026) harmonizes more than 70 authoritative sources (HITRUST), including HIPAA, NIST SP 800-53, ISO 27001, PCI DSS and GDPR, so one assessment can map to several of them at once. There are three validated assessments:
| Assessment | Control set | Valid for |
|---|---|---|
| e1 (essentials) | 44 foundational controls | 1 year |
| i1 (implemented) | 182 curated controls | 1 year |
| r2 (risk-based) | Tailored to your risk factors, the most thorough | 2 years, with an interim assessment after year one |
HITRUST distinguishes itself from SOC 2 in exactly these terms: unlike SOC 2, which is “an attestation with flexible criteria and no third-party validation, HITRUST i1 is a certification with a defined control set, external assessor testing, and centralized HITRUST quality assurance” (HITRUST). That is HITRUST’s framing: a SOC 2 report is still issued by an independent CPA firm, but no central body reviews it afterward the way HITRUST reviews every validated assessment.
The e1 and i1 control sets are fixed, while an r2 set comes out of scoping in HITRUST’s MyCSF tool based on your risk factors, so which requirement statements call for penetration testing depends on the assessment you choose. Where one does, your assessor expects a dated report covering the systems in scope. Our HITRUST penetration testing page shows how the test grows from e1 to r2.
Cost and timeline: HITRUST e1, i1 and r2 vs SOC 2
The figures below are the ones HITRUST publishes on its own assessment pages and in its CSF v11.9.0 release advisory, checked in November 2026. HITRUST does not publish prices there, and SOC 2 fees are set by each audit firm, so the cost row is relative, not a quote.
| SOC 2 Type I | SOC 2 Type II | HITRUST e1 | HITRUST i1 | HITRUST r2 | |
|---|---|---|---|---|---|
| Control set | Your controls, mapped to the criteria | Your controls, mapped to the criteria | 44 foundational controls in CSF v11.9.0 (HITRUST advisory) | 182 curated controls | Tailored, the highest level of control requirements (HITRUST) |
| Time to a result | Point in time, no observation period | Observation period, usually 3 to 12 months, then the report | Around 30 days on average, per HITRUST | 6 to 12 months for most companies, per HITRUST | Not published; plan for the longest of the three |
| Renewal | Usually replaced by a Type II | Typically every year | Every year | Every year | Every 2 years, with an interim assessment after year one |
| Relative cost | Lowest | Moderate | Lowest of the HITRUST levels | Middle | Highest |
Two things move the total more than the framework name. The first is scope: fewer systems holding ePHI means fewer controls to test in either program. The second is readiness: a vendor that already runs a SOC 2 program has much of the evidence an e1 or i1 assessor asks for, which is why most vendors add HITRUST after SOC 2 and not before.
How they fit together
These are complementary, not competing, and buyers often ask for more than one:
- You can report SOC 2 and HITRUST together. A “SOC 2 + HITRUST” report is a combined attestation that evaluates controls under both the SOC 2 Trust Services Criteria and the HITRUST CSF. It does not by itself produce HITRUST certification, which needs the validated assessment and HITRUST’s quality assurance, but it lets one examination serve two audiences.
- HITRUST maps to HIPAA. Because HIPAA is one of the CSF’s authoritative sources, a HITRUST assessment can produce a HIPAA Insights Report that maps the controls to HIPAA requirements. It is evidence of alignment, not a HIPAA certificate, which does not exist.
- The buyer usually decides. Many large health systems ask vendors for HITRUST because it is independently certified. Smaller buyers and many enterprise procurement teams accept SOC 2. HIPAA underlies all of it if you touch ePHI.
- One firm can often do both. A SOC 2 report has to come from a CPA firm, and a HITRUST validated assessment has to come from a HITRUST External Assessor, which HITRUST describes as “the only entities authorized to perform the validated assessments that are submitted to HITRUST for certification” (HITRUST). Some firms hold both roles, and HITRUST’s assessor directory can be filtered by AICPA membership, so one team can run both. Our list of SOC 2 audit firms is a starting point for that shortlist.
The one thing that serves all three: the penetration test
Here is the practical payoff. None of the three names a specific, different test. SOC 2 auditors expect one as security evidence, HITRUST expects one where your requirement statements call for it, and HIPAA’s proposed rule would require an annual one. A single, well-scoped penetration test of the systems that hold the covered data, reported so each finding maps to the framework it touches, satisfies all three at once. You pay for the work once, not three times.
For most health-tech vendors that scope is the product and the cloud behind it. Invadel’s fixed prices for the pieces these frameworks lean on:
- Web application penetration test of the product your customers log into, from $5,200
- API penetration test of the interfaces behind it, from $4,000
- External network penetration test of the internet-facing edge, from $4,200
- Cloud penetration test of the AWS, Azure or GCP account that hosts it, from $6,800
Every price is fixed in writing before work starts, and every test includes a free retest so the report shows the findings closed. The report, executive summary and attestation letter come as separate files so you can attach the right one to SOC 2 evidence, a HITRUST requirement statement, or a HIPAA risk analysis. For the health-tech buyer specifically, our page for healthcare and health-tech covers how a typical engagement is scoped.
If you are still comparing providers, our list of healthcare penetration testing vendors describes the firms that test for hospitals and health-tech companies.
Which one should a vendor pursue first?
- Selling to enterprises and startups: SOC 2 Type II is usually the first ask.
- Selling to hospitals and health systems: expect HITRUST, often starting at e1 or i1 and moving to r2 as deals get larger.
- Handling ePHI at all: HIPAA is not optional, and it underlies whichever certificate or report you pursue.
Budget often settles the order. Our guide to SOC 2 audit cost breaks down what the first report costs before you add HITRUST on top.
Whichever comes first, book the penetration test with enough lead time to fix and retest before the audit or assessment. Waiting until the week before is the most common reason a finding ends up open in front of an assessor.
Frequently asked questions
Is HITRUST better than SOC 2? Neither is “better”; they answer different questions. SOC 2 is an attestation your auditor produces and enterprise buyers widely accept. HITRUST is an independent certification that many large healthcare buyers require. Many vendors end up with both, and can report them together.
HITRUST vs HIPAA: does a HITRUST certification prove HIPAA compliance? It demonstrates strong alignment, and a HITRUST HIPAA Insights Report maps the controls to HIPAA requirements, but there is no official HIPAA certificate and HHS does not recognize private certifications as absolving your obligations. HITRUST is evidence, not a substitute for meeting the Security Rule.
Do SOC 2 and HITRUST both require a penetration test? Neither names one as a hard requirement in its text. SOC 2 auditors expect a recent test as security evidence; HITRUST expects one where your requirement statements call for it. In practice a vendor needs a test for both, which is why one test scoped to the covered systems is the efficient answer.
Can one penetration test cover HIPAA, SOC 2 and HITRUST? Yes. Scope it to the systems that hold the regulated data and have the report map each finding to the relevant framework. One engagement produces evidence all three can use, rather than paying for the same work three times.
How long is each valid? A SOC 2 Type II report covers its observation period and is typically renewed annually. HITRUST e1 and i1 certifications are valid for one year; r2 is valid for two, with an interim assessment after the first year. HIPAA is ongoing, so testing is usually annual.
Which should a health-tech startup get first? Usually SOC 2 Type II, because it is widely accepted, then HITRUST when a hospital or health-system deal requires it. Keep HIPAA covered throughout if you handle ePHI.
Can I use the same auditor for SOC 2 and HITRUST? Yes, if the firm is both a licensed CPA firm and a HITRUST External Assessor. Only a CPA firm can issue a SOC 2 report, and only an External Assessor can perform a validated assessment that HITRUST will certify. Ask the firm to confirm both roles in writing and to plan the two engagements together.
Is SOC 2 enough for HIPAA compliance? No. A SOC 2 report is an auditor’s opinion on your controls against the Trust Services Criteria; it does not say you meet the HIPAA rules, and it does not cover business associate agreements, breach notification or the Privacy Rule. A SOC 2 report with a HIPAA mapping gets closer, but the legal obligation stays with you.
Do hospitals require HITRUST from every vendor? No. It depends on the buyer and on how much ePHI you handle. Many large health systems ask for HITRUST, while smaller buyers often accept a SOC 2 report. A signed business associate agreement is the one item every covered entity needs from a vendor that touches ePHI.
Fixed price, fixed scope, free retest. Scope your test and tell us which frameworks you carry; we will map the findings to each.
Written by
Azad Khan, Senior GRC & Compliance
26+ years in the field. Focus: GRC, ISO 27001 & PCI DSS consulting. Part of the team that scopes, tests, and reports for our clients. Full profile →