Identity Vendor Certifications 2026
SOC 2 Type II, ISO 27001, HIPAA BAA, FedRAMP and PCI DSS across 155 identity vendors in 16 categories, sourced to their own trust pages and official registries
- 118 of 155 identity vendors (76.1%) document a SOC 2 Type II report and 102 (65.8%) document ISO 27001 certification, but only 51 of those 102 (50.0%) name the ISO/IEC 27001:2022 edition, per vendor trust centers, docs and official registries checked November 5, 2026.
- 13 of 28 CIAM platforms (46.4%) document all three of SOC 2 Type II, ISO 27001 and a HIPAA Business Associate Agreement: Akamai Identity Cloud, Amazon Cognito, Auth0, Descope, Frontegg, FusionAuth, Google Cloud Identity Platform, Kinde, LoginRadius, MojoAuth, Salesforce Identity, Scalekit and Stytch.
- Only 31 of 155 identity vendors (20.0%) document that they sign a HIPAA BAA, 17 of them CIAM platforms; none of the 63 PAM, IGA, ITDR, identity verification, zero trust, PKI, machine identity, CIEM and AI identity vendors does, and 87 of the 109 non-hyperscaler vendors with SOC 2 Type II (79.8%) document no BAA.
- 42 of 155 identity vendors (27.1%) document a FedRAMP authorization; 11 are AWS, Google, Microsoft and Oracle services, and of the other 31, 20 cover a separate government edition, 5 come through a partner's authorization package and 1 covers a different product, leaving 5 listed under the vendor's own commercial product name.
- 43 of 155 identity vendors (27.7%) document a PCI DSS attestation; of the 35 that are not hyperscaler services, 9 state Level 1 or a QSA Report on Compliance, 6 attest through a self-assessment questionnaire (SAQ) and 20 state no level.
- 21 of 155 identity vendors (13.5%) have none of the five core certifications confirmed on a public vendor page or official registry, among them OneLogin, Entrust, Transmit Security, Semperis, Sectigo (certificate lapsed) and NordPass; 130 (83.9%) publish a trust center or security page, but only 52 (33.5%) document data residency regions.
- Vendor trust centers, security and compliance pages, docs, pricing pages and certificates for 155 identity vendors, 248 unique source links, every vendor checked on 2026-11-05 (URLs per cell in the dataset)
- FedRAMP Marketplace: https://marketplace.fedramp.gov/
- FedRAMP, Certification Classes: https://www.fedramp.gov/2026/agencies/use/classes/
- Cloud Security Alliance STAR Registry: https://cloudsecurityalliance.org/star/registry
- 45 CFR 164.502(e), disclosures to business associates: https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.502
- SWI analysis script: scripts/reports/vendor-certifications-report.mjs
Most identity vendors document SOC 2 Type II. Far fewer document the rest of what a regulated buyer asks for. Of 155 identity vendors in Start with Identity's Identity Vendor Certifications Directory, 118 (76.1%) document a SOC 2 Type II report, but only 31 (20.0%) document that they sign a HIPAA Business Associate Agreement, and only 13 of 28 CIAM platforms document SOC 2 Type II, ISO 27001 and a BAA together. FedRAMP looks common at 42 vendors until you read the scope: 11 are hyperscaler services, and 20 of the other 31 cover a separate government edition.
Every cell in the directory links to the vendor's own trust center, documentation, certificate or an official registry, checked on November 5, 2026. The data is free to reuse under CC BY 4.0.
Methodology
Scope. 155 identity vendors in 16 categories: CIAM (28), identity verification (20), workforce IAM (14), password management (14), MFA (13), secrets management (9), authorization (8), zero trust (8), AI and non-human identity (7), PAM (6), PKI (6), ITDR (6), managed open-source identity (6), IGA (5), machine identity (3) and CIEM (2). We started from the vendors readers look up most on this site and added each category's flagships. Self-hosted-only projects (Keycloak, authentik), discontinued products (Aserto, Styra DAS) and vendors with no managed service (Curity) are left out.
Evidence. A "yes" needs the vendor's own trust center, security page, documentation, pricing page, certificate or newsroom, or an official registry: the FedRAMP Marketplace, the CSA STAR Registry or a hyperscaler's "services in scope" list. Review sites, blogs and third-party directories do not count. Of the 607 "yes" cells, 332 rest on a trust center, 143 on documentation, 106 on an official registry or in-scope list, 14 on a vendor press release, 7 on a pricing page and 5 on a certificate.
Values. Yes, in progress (the vendor says so), no (only when the vendor says it does not hold it) and not documented. "Not documented" is never counted as "no". Each "yes" carries a scope: the ISO edition, the plan a BAA needs, the edition and class a FedRAMP listing covers, the PCI level.
Hyperscalers. AWS, Google Cloud, Microsoft and Oracle identity, secrets and identity threat services (11 records, including Microsoft Defender for Identity) inherit their cloud's certifications service by service. We report some figures with and without them, because they inflate FedRAMP and PCI counts for reasons that say little about specialist vendors.
Limits. A trust-center badge is not the report behind it. Many trust centers render only in a browser (Vanta, SafeBase, Conveyor, Laika), and three vendor sites (Entrust, OneLogin, NordPass) blocked automated reading entirely and Prove's trust center did not render, so some "not documented" cells reflect what we could read, not what exists. Company-level certifications are recorded with that scope when the vendor does not name the product. Category groups are small, so read category rates as directions. scripts/reports/vendor-certifications-report.mjs prints every number below with its denominator.
Finding 1: SOC 2 Type II is the baseline, ISO editions often go unnamed
| Certification | Vendors documenting it (of 155) | Share |
|---|---|---|
| SOC 2 Type II | 118 | 76.1% |
| ISO 27001 | 102 | 65.8% |
| PCI DSS | 43 | 27.7% |
| FedRAMP | 42 | 27.1% |
| HIPAA BAA | 31 | 20.0% |
By category:
| Category | Vendors | SOC 2 Type II | ISO 27001 | HIPAA BAA | FedRAMP | PCI DSS |
|---|---|---|---|---|---|---|
| CIAM | 28 | 22 | 18 | 17 | 5 | 8 |
| Identity verification | 20 | 16 | 15 | 0 | 3 | 5 |
| Workforce IAM | 14 | 9 | 10 | 3 | 7 | 4 |
| Password management | 14 | 9 | 9 | 2 | 0 | 1 |
| MFA | 13 | 9 | 7 | 1 | 4 | 2 |
| Secrets management | 9 | 8 | 7 | 3 | 3 | 5 |
| Authorization | 8 | 5 | 1 | 3 | 1 | 1 |
| Zero trust | 8 | 8 | 5 | 0 | 5 | 2 |
| AI and non-human identity | 7 | 5 | 5 | 0 | 1 | 1 |
| PAM | 6 | 6 | 6 | 0 | 4 | 5 |
| PKI | 6 | 4 | 4 | 0 | 1 | 1 |
| ITDR | 6 | 4 | 4 | 0 | 3 | 1 |
| Open source, managed | 6 | 4 | 3 | 2 | 0 | 2 |
| IGA | 5 | 5 | 4 | 0 | 2 | 1 |
| Machine identity | 3 | 2 | 2 | 0 | 1 | 2 |
| CIEM | 2 | 2 | 2 | 0 | 2 | 2 |
SOC 2 Type II is close to universal among vendors that publish anything: every PAM, IGA, zero trust and CIEM vendor here documents it. ISO 27001 is less consistent, and only 51 of the 102 vendors that document it (50.0%) name the ISO/IEC 27001:2022 edition. The rest say "ISO 27001" with no year, so the certificate itself is the only way to check edition, issuer and scope. Clerk is the one vendor that says plainly it is not ISO 27001 certified, and Hanko Cloud lists ISO 27001 as in progress.
Finding 2: fewer than half of CIAM platforms document the full regulated set
The query buyers type is some version of "CIAM SOC 2 Type II, ISO 27001 and HIPAA". 13 of 28 CIAM platforms (46.4%) document all three: Akamai Identity Cloud, Amazon Cognito, Auth0, Descope, Frontegg, FusionAuth, Google Cloud Identity Platform, Kinde, LoginRadius, MojoAuth, Salesforce Identity, Scalekit and Stytch.
| CIAM platforms (28) | Documented | Share |
|---|---|---|
| SOC 2 Type II | 22 | 78.6% |
| ISO 27001 | 18 | 64.3% |
| HIPAA BAA | 17 | 60.7% |
| SOC 2 Type II and a BAA | 16 | 57.1% |
| All three | 13 | 46.4% |
Three more are one certification short: Clerk, WorkOS and Strivacity document SOC 2 Type II and a BAA but not ISO 27001. Two caveats on the list. Akamai Identity Cloud is past end of sale and Akamai's docs give a decommission date of December 31, 2027. Salesforce does not name Identity in any certification scope, so its row maps to the Lightning Platform and Experience Cloud services that are named.
Finding 3: HIPAA BAAs are a CIAM thing
HIPAA requires a covered entity to document a business associate's safeguards "through a written contract" before that vendor handles protected health information (45 CFR 164.502(e)). A vendor that says it is "HIPAA compliant" without offering one does not meet that need, so the directory records only documented BAAs.
31 of 155 vendors (20.0%) document a BAA, and 17 of the 31 are CIAM platforms. The rest are workforce IAM (AWS IAM Identity Center, Microsoft Entra ID, Okta), secrets (the AWS, Azure and Google services), authorization (Amazon Verified Permissions, Permit.io, Warrant through WorkOS), managed open source (Logto Cloud, Supabase), password management (Proton Pass, Zoho Vault) and MFA (Twilio Verify). None of the 63 PAM, IGA, ITDR, identity verification, zero trust, PKI, machine identity, CIEM and AI identity vendors documents one. Tailscale is the only vendor that says no outright: it states none of its services are in HIPAA scope because it stores only metadata.
The gap between audit and contract is wide: 87 of the 109 non-hyperscaler vendors with SOC 2 Type II (79.8%) document no BAA. At least 15 describe HIPAA compliance or a HIPAA assessment without documenting a BAA, among them Keeper Security, Teleport, Persona, Incode, Cloudflare, Zscaler, Bitwarden, Infisical and ZITADEL. Where a BAA exists, the terms vary: 11 of the 31 are tied to a named plan or edition (Clerk, Frontegg, MojoAuth, SSOJet, Stytch, WorkOS and Logto on Enterprise; Descope from Growth; Supabase from Team; Twilio on Security or Enterprise Edition; Warrant through WorkOS), 6 are "on request", 8 come under a hyperscaler's platform BAA, and 6 are offered with no plan terms stated.
Finding 4: FedRAMP usually means a government edition
42 of 155 vendors (27.1%) document a FedRAMP authorization, and 5 more (Bitwarden, CLEAR, Incode, LexisNexis Risk Solutions and DigiCert) say they are in progress. Eleven of the 42 are hyperscaler services, where authorization typically applies in government regions (AWS GovCloud, Azure Government) or the provider's authorized cloud. The other 31:
| Route to FedRAMP | Vendors | Examples |
|---|---|---|
| Separate government edition | 20 | Okta for Government, RSA ID Plus for Government, IBM Verify for Government, Duo Federal, Salesforce Government Cloud Plus, Socure for Government, Persona for Government, BeyondTrust Identity Security for Government, Keeper for Government, CyberArk (Idira) Government Services, Cloudflare for Government, Zscaler Government |
| Through a partner's package | 5 | Ping Identity (UberEther IAM Advantage), Descope (Palantir FedStart), 1Kosmos (HRTec FedHIVE), Delinea Secret Server (UberEther), Akeyless (Second Front Game Warden) |
| A different product | 1 | OneSpan (OneSpan Sign, its e-signature product) |
| The vendor's commercial product | 5 | Axiad Conductor, SailPoint Identity Security Cloud, Saviynt Enterprise Identity Cloud, ID.me Identity Gateway, Orca Cloud Security Platform |
So 26 of 31 independent FedRAMP listings need a scope check: the commercial tenant a buyer trials is usually not the authorized one. Read the level carefully too. The Marketplace now lists Certification Classes A to D, and FedRAMP says agencies "should not treat Certification Classes as one-for-one replacements for Low, Moderate, or High impact levels". Classes measure how much assurance information the provider commits to, not security. The directory records the listing's exact class and, where a vendor says "High", notes it as the vendor's description. No password manager or managed open-source service in the set holds an authorization. For agencies, the government identity tools ranking covers the wider field.
Finding 5: "PCI DSS compliant" rarely says which level
43 of 155 vendors (27.7%) document a PCI DSS attestation. Eight are hyperscaler services inheriting AWS, Azure or Google Cloud assessments. Of the 35 others:
| What the vendor documents | Vendors | Examples |
|---|---|---|
| Level 1 or a QSA Report on Compliance | 9 | Salesforce (Level 1 AoC), Twilio Verify, Stripe Identity, Keeper Security, HashiCorp Vault and Boundary (Level 1); Okta, Wiz, CrowdStrike (ROC) |
| Self-assessment questionnaire | 6 | Descope, Strivacity, Ory Network, Orca (SAQ-D); Duo (SAQ); 1Password (SAQ A) |
| No level or role stated | 20 | Auth0, LoginRadius, Stytch, IBM Verify, Supabase, Jumio, Persona, Cloudflare, Zscaler, Teleport and 10 more |
An identity service that never touches card data can reasonably attest by SAQ, and Clerk says outright that PCI DSS does not apply because it stores no cardholder data. But an SAQ is the vendor's own assessment, not a Qualified Security Assessor's, and SAQ A is a merchant questionnaire. If your PCI DSS scope includes the identity layer, ask for the Attestation of Compliance and read its service-provider section.
Finding 6: one vendor in eight documents none of the core five
21 of 155 vendors (13.5%) have none of SOC 2 Type II, ISO 27001, a BAA, FedRAMP or PCI DSS confirmed on a page we could read. They are a mix:
- No public attestation found: Transmit Security, SuperTokens (lists "SOC2" on pricing without a type), Veridium, Secret Double Octopus, RoboForm, Sticky Password, Uniqkey (its ISO 27001 claim is its data centre's), PlainID, Oso ("SOC 2 certified" with no type), Stack Auth and Semperis.
- Below the bar or lapsed: Trusona holds SOC 2 Type I and lists Type II as a roadmap item, and the ISO/IEC 27001:2022 certificate Sectigo publishes expired on 2026-10-09 with no renewal posted.
- Acquired, scope unclear: SGNL (CrowdStrike), Nok Nok Labs (OneSpan), Venafi (Palo Alto Networks) and Astrix Security (joining Cisco); the parents' certifications do not name the product.
- Sites or trust centers we could not read: OneLogin, Entrust, NordPass and Prove. These need a manual check, and we will update them from a readable public page.
The positive side: 130 of 155 (83.9%) publish a trust center or security page. Data residency is thinner: only 52 (33.5%) document where customer data can be hosted, 49 of them with an EU option. Transparency is a vendor-risk signal on its own: a vendor that makes you file an NDA request to learn whether it has SOC 2 at all will be slower on every later question.
What to ask a vendor
- The SOC 2 Type II report, not the badge: the audit period, the auditor, exceptions and the services in scope.
- The ISO 27001 certificate: edition (2022), issuing body and scope statement. Then check that the product you are buying is in that scope.
- The BAA and its plan: whether it is available on the plan you will buy, and which products it covers.
- For FedRAMP, the Marketplace listing: whether the authorization is the vendor's own, its Certification Class, which edition it covers and whether that is the tenant you will use.
- For PCI DSS, the AOC: level, service-provider role and whether the identity service is in scope.
Pair this with the SOC 2 for identity teams guide, identity controls for HIPAA and for ISO 27001. For ranked shortlists, see compliant CIAM platforms, compliant PAM platforms, compliant IGA platforms and HIPAA-ready CIAM for healthcare.
About the data
Download the CSV (one row per vendor, one column per core certification plus scope) or the JSON (every certification with its source URL and evidence type). Cite "Start with Identity, Identity Vendor Certifications Directory 2026" with a link, and link a figure with its finding anchor, such as #finding-3. Vendors that spot a wrong or missing cell can send a public link through our contact page; we update from public pages only, and every change carries its check date.
Frequently asked questions
- Which CIAM platforms are SOC 2 Type II, ISO 27001 and HIPAA compliant?
- As of November 5, 2026, 13 of the 28 CIAM platforms in SWI's Identity Vendor Certifications Directory document a SOC 2 Type II report, ISO 27001 certification and a signed HIPAA Business Associate Agreement on their own trust center, docs or an official registry: Akamai Identity Cloud, Amazon Cognito, Auth0, Descope, Frontegg, FusionAuth, Google Cloud Identity Platform, Kinde, LoginRadius, MojoAuth, Salesforce Identity, Scalekit and Stytch. Clerk, WorkOS and Strivacity document SOC 2 Type II and a BAA but not ISO 27001 (Clerk says it is not ISO 27001 certified).
- Which identity providers are FedRAMP authorized?
- Among workforce IAM, CIAM and MFA vendors, Okta (Okta for Government), RSA (ID Plus for Government), IBM Verify (Verify for Government), Duo (Duo Federal), Salesforce (Government Cloud Plus) and Axiad Conductor have FedRAMP listings, and Ping Identity, Descope and 1Kosmos reach FedRAMP through a partner's package. Microsoft Entra ID, AWS IAM Identity Center, Amazon Cognito, Google Cloud Identity Platform and Oracle OCI IAM inherit their cloud's authorization. Across all 155 vendors, 42 document FedRAMP. The Marketplace now lists Certification Classes A to D, which FedRAMP says are not one-for-one replacements for Low, Moderate and High.
- Which identity vendors are PCI DSS Level 1 service providers?
- The AWS and Azure identity and secrets services inherit their cloud's Level 1 service provider status. Among other vendors, Salesforce, Twilio Verify, Stripe Identity, Keeper Security, HashiCorp Vault and HashiCorp Boundary state Level 1, and Okta, Wiz and CrowdStrike state a QSA Report on Compliance. Six vendors, including Descope, Strivacity and 1Password, attest through a self-assessment questionnaire, and 20, including Auth0 and Stytch, state no level.
- Do password managers sign HIPAA BAAs?
- Rarely, by their own documentation. Of 14 password managers checked on November 5, 2026, only Proton Pass (any Proton user, on request) and Zoho Vault (template on request) document a Business Associate Agreement. Bitwarden says it is HIPAA compliant but does not say it signs a BAA, and 1Password, Dashlane and LastPass document SOC 2 Type II and ISO 27001 but no BAA. Keeper Security, listed under PAM, also states HIPAA compliance without documenting a BAA.
- Is a SOC 2 Type II report the same as HIPAA compliance?
- No. SOC 2 Type II is an auditor's opinion that a vendor's controls operated over a period, usually a year. HIPAA requires a covered entity to document a business associate's safeguards in a written contract before that vendor handles protected health information (45 CFR 164.502(e)). In SWI's directory, 87 of the 109 non-hyperscaler vendors with SOC 2 Type II (79.8%) document no BAA.
Cite this report
Free to quote and reuse under CC BY 4.0 with a link back. Each key finding has its own anchor (for example #finding-1) so you can link the exact figure you cite. Published November 17, 2026, last updated November 17, 2026.
SWI Community Team. (2026). Identity Vendor Certifications 2026. Start with Identity. https://startwithidentity.com/reports/identity-vendor-certifications-2026/