Subprocessor list in SIEM and security operations
Naming the actual subprocessors is what turns a privacy promise into something you can check.
1 of 17 vendors we measured here publish it, that is 6%. Last checked 2026-09-03.
6% here against 8% across every category we measure. SIEM and security operations sits below the overall share for this criterion.
Back to Subprocessor list across all categories, or to SIEM and security operations.
Published
The actual list is published, not just a promise to keep one.
| Vendor | What we found |
|---|---|
| Panther | https://panther.com/subprocessors |
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 |
|---|---|
| Anvilogic | 7 addresses checked |
| Arctic Wolf | 7 addresses checked |
| Blumira | 7 addresses checked |
| Corelight | 7 addresses checked |
| Cybereason | 7 addresses checked |
| Devo | 7 addresses checked |
| Exabeam | 7 addresses checked |
| Filigran | 7 addresses checked |
| Gigamon | 7 addresses checked |
| Hunters | 7 addresses checked |
| Huntress | 7 addresses checked |
| Red Canary | 7 addresses checked |
| Stellar Cyber | 7 addresses checked |
| Todyl | 7 addresses checked |
| Trend Micro | 7 addresses checked |
| Vectra AI | 7 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.
| Vendor | What we found |
|---|---|
| ExtraHop | The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured. |
Found something we missed? Tell us and the next run picks it up.