Search for how to get HIPAA certification and you will land on pages selling a badge, a seal, or a certificate of compliance. None of them point to a real credential. HIPAA has no certifying body, no accreditation scheme and no public registry comparable to PCI DSS or ISO/IEC 27001. What a vendor can actually produce is a signed Business Associate Agreement, evidence of a HITRUST validated assessment, or a SOC 2 report whose controls are mapped onto the Security Rule. This piece walks through why the certificate does not exist and what to ask for instead.
There is no HIPAA certifying body
The US Department of Health and Human Services (HHS) writes and enforces the HIPAA Privacy, Security and Breach Notification Rules through its Office for Civil Rights. HHS does not run an audit scheme, does not accredit assessors, and does not issue certificates. There is no HIPAA equivalent of an ISO/IEC 27001 certification body or a PCI Qualified Security Assessor network. Any vendor page, badge or marketplace listing that claims to be "HIPAA certified" is describing something that is not issued by anyone with the authority to issue it. For the same reason you will never see "SOC 2 certified" or "GDPR certified" used correctly: a SOC 2 outcome is a report with an auditor's opinion, not a pass or fail stamp, and the same logic applies here. The HIPAA framework page lists vendors by the evidence actually captured against their name, not by a certificate that nobody issues.
What the Security Rule actually asks a vendor to do
HIPAA applies to covered entities and their business associates. A SaaS vendor that stores, processes or transmits protected health information (PHI) on behalf of a healthcare customer is typically a business associate, and the relationship is governed by a contract, not a badge. The regulations page for HIPAA breaks down what the Security Rule expects in practice: administrative safeguards such as risk assessments and workforce training, physical safeguards covering facility and device access, and technical safeguards covering access control, audit logging and encryption. None of this is a one-time test. It is an ongoing programme, which is exactly why there is no single artefact that can certify it finished.
- Administrative safeguards: risk analysis, sanction policy, workforce training, incident response
- Physical safeguards: facility access controls, workstation and device security
- Technical safeguards: access control, audit controls, integrity controls, transmission security
- Organisational requirements: the BAA itself, which sets out each party's obligations for PHI
The paperwork that actually appears against a vendor
Instead of a certificate, three kinds of evidence show up repeatedly in vendor reviews, and each proves something different. Knowing the difference matters more than knowing the search term that got you here.
| Artifact | What it actually proves | Where it lives |
|---|---|---|
| Signed BAA | A contractual commitment to handle PHI under HIPAA's rules, with each party's responsibilities named | Negotiated privately between buyer and vendor, not published in any public registry |
| HITRUST validated assessment | An independent assessor confirmed controls against a specific framework and level (r2, i1 or e1) | Recorded in HITRUST's own database against the vendor's legal name |
| SOC 2 report mapped to the Security Rule | An auditor's opinion on whether controls operated effectively, sometimes cross-walked to HIPAA safeguards in a supplementary bridge | Shared under NDA, not published in full |
| HIPAA badge on a trust centre | A vendor's own claim of alignment, usually self-attested with no independent verification behind it | Self-published trust pages, which is why it needs checking against the other three rows |
What appears against a vendor name instead of a certificate.
How often each artifact actually shows up
Across vendor pages carrying a HIPAA badge, the gap between the badge and the underlying evidence is common enough to be the default rather than the exception.
- HIPAA badge present, no BAA captured
- Most common pattern
- in the CertReports index on 2026-11-10
- HITRUST validated assessment listed
- Minority of HIPAA-tagged vendors
- in the CertReports index on 2026-11-10
- SOC 2 report explicitly cross-mapped to HIPAA
- Fewer than half of SOC 2 vendors serving healthcare buyers
- in the CertReports index on 2026-11-10
None of these figures mean a vendor has no public evidence at all. It means the badge alone is not the evidence, and a buyer still has to pull the contract and the report to close the gap. The state of public compliance evidence in 2026 covers the broader pattern across 3,000 vendor pages, and the same gap between a stated badge and a captured artefact turns up across every framework, not just HIPAA.
What to actually do, in order
- 1
Start with the BAA, not the badge
Ask the vendor's sales or legal contact for their standard Business Associate Agreement before you evaluate anything else. If PHI will touch the product and no BAA is offered, nothing else in this list matters. See how to get a BAA signed with a vendor for the questions to raise during negotiation. - 2
Request the SOC 2 report and check the mapping
A current SOC 2 Type II report, read properly, shows which controls were tested and how often they failed. Some vendors attach a supplementary letter mapping Trust Services Criteria to HIPAA safeguards. Ask for that mapping by name. - 3
Check for a HITRUST validated assessment
If the vendor claims HITRUST, confirm the level (e1, i1 or r2) and the validity window directly against HITRUST's own record, not against a vendor's self-description. - 4
Treat the trust centre badge as a prompt, not proof
A HIPAA badge on a trust page tells you to ask the three questions above. It does not answer them. See how to read a trust centre for the rest of the page worth checking. - 5
Record the gap, do not leave it blank
If the vendor has a badge but no BAA on file, write that down as the current state rather than assuming anything. Say there is no public evidence of the artefact you need, and chase it before contract signature.
HITRUST is the closest thing to a certification, and it is still not HIPAA's
HITRUST runs its own assessment programme, with its own assessors, its own scoring and its own validity periods. A HITRUST r2 validated assessment is a real, independently checked artefact that gets recorded against a vendor's name, and it maps heavily onto HIPAA's safeguards alongside other frameworks. But HITRUST is a private company's framework, not a government scheme, and passing it is not the same as HHS certifying anyone. The distinction between HITRUST's e1, i1 and r2 levels, and what each one actually checks, is covered in what HITRUST's R2, I1 and E1 levels mean. If a vendor's HIPAA badge links through to a HITRUST record, that is a stronger signal than a badge alone, but it is still worth confirming the level and the date rather than taking the badge's word for it.
Reading a trust centre's HIPAA claim correctly
The gap between a stated badge and a captured artefact is easiest to see on a real vendor page. Look at how the HIPAA row sits next to the other framework rows: a badge with no linked BAA reads differently from a SOC 2 Type 2 report with a stated report type, or a Data Privacy Framework listing with an active status and a renewal date attached.
Pendo · Trust report
Analytics · Public evidence as of 16 Nov 2026
Framework overview
CertReports state for each framework with public evidence: 3 verified, 5 vendor-stated.
HIPAAVendor-statedBadge only, BAA not captured
DPFVerifiedValid to 29 Oct 2027
SOC 2VerifiedSOC 3, period to 31 Dec 2025
SOC 3VerifiedSOC 3, period to 31 Dec 2025GDPRVendor-statedTrust centre · 30 Sep 2026
PCI DSSVendor-statedTrust centre · 30 Sep 2026CCPAVendor-statedTrust centre · 30 Sep 2026
TX-RAMPVendor-statedTrust centre · 30 Sep 2026
3Documents and agreements
Legal and review documents Pendo publishes or offers, as of 30 Sep 2026.
- Subprocessor list · Public
- Privacy policy · Public
- Public trust centre documents · SOC 3 Report for 2026 (Audit Period 1 Jan 2025 to 31 Dec 2025); Pendo Penetration Test Attestation Letter - September 2025
1Security practices
Public statements from Pendo, shown as statements, not attestations, as of 30 Sep 2026.
- Penetration testing · annual
9Subprocessors
Named on Pendo's public subprocessor list, last seen 30 Sep 2026.
Amazon Web Services- ACAnthropic Claude
- COCore10
- ECElastic.co
Google Cloud Platform
LangChain
Microsoft Azure
OpenAITray.ai
HHS does not endorse, certify or approve any product, service or organisation as being "HIPAA compliant", and there is no such thing as a federally recognised HIPAA certification.
HIPAA eligible is also not the same claim
Cloud providers such as AWS and Azure describe certain services as "HIPAA eligible", meaning the service can be configured to support a BAA-covered workload. That label is not a compliance statement about your particular configuration, and it is not a certificate either. The difference between a platform being eligible and your specific deployment being covered by a signed BAA is explained in HIPAA eligible vs HIPAA compliant SaaS, and it is worth reading before you assume an underlying cloud's label covers the application built on top of it.
Build the file instead of chasing the certificate
A workable vendor file for a HIPAA-relevant vendor holds four things: a signed BAA with the current legal entity named correctly, the latest SOC 2 report with its period dates checked, any HITRUST validated assessment record with its level and expiry, and a note on subprocessors who also touch PHI. None of these is a certificate, and none of them should be described as one in your own records either. Treat a stated HIPAA badge on a trust centre as a starting point for the conversation, not as the answer to it.
What to ask for on the first call
Ask directly: can you send your standard BAA, your latest SOC 2 report, and confirmation of any HITRUST validated assessment with its level and expiry date. If the answer to all three is no, treat that as the current state and escalate before data starts flowing, rather than waiting for a badge to change.
People also ask
How to hipaa certification?
There is no process that ends in a HIPAA certificate, because HHS does not run one. What you can obtain from a vendor is a signed BAA covering your specific relationship, a current SOC 2 report ideally mapped to the Security Rule, and in some cases a HITRUST validated assessment. Ask for all three rather than searching for a certification that does not exist.
How to hipaa certified?
You cannot become "HIPAA certified" because the phrase describes a credential nobody issues. A covered entity or business associate instead builds a documented security programme covering administrative, physical and technical safeguards, signs BAAs with every vendor touching PHI, and keeps that evidence current. HITRUST's r2 validated assessment is the closest independently checked equivalent available today.
How to get hipaa certification?
You cannot get it, because HHS has not created a certification scheme for HIPAA and no accredited body issues one on its behalf. What you get instead is a signed BAA from each vendor handling PHI, a SOC 2 report with controls mapped to the Security Rule where available, and optionally a HITRUST validated assessment at the e1, i1 or r2 level, each recorded separately rather than bundled into one certificate.
How to get hipaa certified?
Solomon Amos · Founder, CertReports
Solomon builds CertReports, the public evidence index for vendor security reviews. PhD in machine learning and cybersecurity, two years embedded at HMRC digital programmes, founder of TapTax. He writes about what registries, trust centres and auditors actually publish, and how buyers can use it before the questionnaire goes out.
Read next on CertReports
You might also like
How to Get a Business Associate Agreement Signed With a Vendor
Solomon Amos · 30 Oct 2026 · 9 min read
The BAA checklist: what to check before sending PHI to a vendor
Solomon Amos · 9 Sep 2026 · 11 min read