Certifications named in API security
Naming SOC 2 or ISO 27001 publicly is the low bar; not naming them is a signal.
4 of 12 vendors we measured here publish it, that is 33%. Last checked 2026-09-02.
33% here against 33% across every category we measure. API security sits exactly at the overall share for this criterion.
Back to Certifications named across all categories, or to API security.
Published
SOC 2 or ISO 27001 named on a public page.
| Vendor | What we found |
|---|---|
| Beagle Security | https://beaglesecurity.com/security |
| Cequence | https://trust.cequence.ai/ |
| Pynt | https://www.pynt.io/trust-center |
| ThreatX | https://www.threatx.com/security/ |
No named certification found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| 42Crunch | 6 addresses checked |
| Akto | 6 addresses checked |
| APIsec | 6 addresses checked |
| Approov | 6 addresses checked |
| Aptori | 6 addresses checked |
| Data Theorem | 6 addresses checked |
| FireTail | 6 addresses checked |
| Salt Security | 6 addresses checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
None. Every vendor here was measured for this criterion.
Found something we missed? Tell us and the next run picks it up.