Notice before subprocessors change in Vulnerability management
A list is a snapshot. Art. 28(2) GDPR gives you a right to object, and that needs advance notice.
0 of 11 vendors we measured here publish it, that is 0%. Last checked 2026-09-02.
0% here against 10% across every category we measure. Vulnerability management sits below the overall share for this criterion.
Back to Notice before subprocessors change across all categories, or to Vulnerability management.
Published
The vendor commits publicly to giving notice before the list changes.
None of the vendors we measured here published this.
No commitment to give notice before subprocessors change 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 |
|---|---|
| Acunetix | 8 addresses checked |
| Aqua Security | 8 addresses checked |
| Black Duck | 8 addresses checked |
| Bright Security | 8 addresses checked |
| Brinqa | 8 addresses checked |
| Checkmarx | 8 addresses checked |
| Greenbone | 8 addresses checked |
| JFrog | 8 addresses checked |
| Mend | 8 addresses checked |
| StackHawk | 8 addresses checked |
| Wiz | 8 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 |
|---|---|
| Balbix | The vendor’s server blocked or rate-limited our crawler, so this was not measured. |
Found something we missed? Tell us and the next run picks it up.