Subprocessor list in Container and cloud workload security
Naming the actual subprocessors is what turns a privacy promise into something you can check.
2 of 26 companies we measured here publish it, that is 8%. Last checked 2026-10-19.
8% here against 7% across every category we measure. Container and cloud workload security sits above the overall share for this criterion.
This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.
Back to Subprocessor list across all categories, or to Container and cloud workload security.
- Found2
- Not found at checked addresses24
- Not measured2
28 companies in total. Unmeasured companies are excluded from the published share.
Published
The actual list is published, not just a promise to keep one.
| Vendor | What we found |
|---|---|
| Socket | https://socket.dev/subprocessorsChecked |
| Upwind | https://www.upwind.io/sub-processorsChecked |
No subprocessor list 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 |
|---|---|
| Anchore | 7 addresses checkedChecked |
| Armo | 7 addresses checkedChecked |
| Cast AI | 7 addresses checkedChecked |
| Chainguard | 7 addresses checkedChecked |
| Docker Scout | 7 addresses checkedChecked |
| Endor Labs | 7 addresses checkedChecked |
| Fairwinds | 7 addresses checkedChecked |
| Falco | 7 addresses checkedChecked |
| Isovalent | 7 addresses checkedChecked |
| Kubescape | 7 addresses checkedChecked |
| Kubex | 7 addresses checkedChecked |
| Kyverno | 7 addresses checkedChecked |
| Nirmata | 7 addresses checkedChecked |
| Prisma Cloud | 7 addresses checkedChecked |
| Rafay | 7 addresses checkedChecked |
| Sedai | 7 addresses checkedChecked |
| Spectro Cloud | 7 addresses checkedChecked |
| Stackrox | 7 addresses checkedChecked |
| Sweet Security | 7 addresses checkedChecked |
| Tetragon | 7 addresses checkedChecked |
| Tigera | 7 addresses checkedChecked |
| Trivy | 7 addresses checkedChecked |
| vCluster | 7 addresses checkedChecked |
| Zesty | 7 addresses checkedChecked |
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.
| Vendor | What we found |
|---|---|
| Clair | The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.Checked |
| Cloudsmith | The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked |
Other criteria in Container and cloud workload security
- Data processing agreement
- Data location stated
- Status page with history
- Public pricing
- Certifications named
- Uptime SLA with a figure
- HTTPS enforced with HSTS
- No third-party tracking before consent
- security.txt (RFC 9116)
- Notice before subprocessors change
- Named privacy contact
Subprocessor list in related categories
Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.