Named privacy contact in Vulnerability management
"Contact us" is not a privacy contact. A named officer or a dedicated address is.
18 of 41 companies we measured here publish it, that is 44%. Last checked 2026-10-17.
44% here against 36% across every category we measure. Vulnerability management 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 Named privacy contact across all categories, or to Vulnerability management.
- Found18
- Not found at checked addresses23
- Not measured2
43 companies in total. Unmeasured companies are excluded from the published share.
Published
A data protection officer or a dedicated privacy address is named.
No named privacy contact 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 |
|---|---|
| Black Duck | 7 addresses checkedChecked |
| Bright Security | 7 addresses checkedChecked |
| Brinqa | 7 addresses checkedChecked |
| Bugcrowd | 7 addresses checkedChecked |
| Checkmarx | 7 addresses checkedChecked |
| Cobalt | 7 addresses checkedChecked |
| Cycode | 7 addresses checkedChecked |
| Edgescan | 7 addresses checkedChecked |
| Greenbone | 7 addresses checkedChecked |
| Intigriti | 7 addresses checkedChecked |
| Intruder | 7 addresses checkedChecked |
| Legit Security | 7 addresses checkedChecked |
| Nucleus Security | 7 addresses checkedChecked |
| Ox Security | 7 addresses checkedChecked |
| Pentera | 7 addresses checkedChecked |
| Probely | 7 addresses checkedChecked |
| Qualys | 7 addresses checkedChecked |
| Reflectiz | 7 addresses checkedChecked |
| Semgrep | 7 addresses checkedChecked |
| SonarSource | 7 addresses checkedChecked |
| Tenable | 7 addresses checkedChecked |
| Veracode | 7 addresses checkedChecked |
| YesWeHack | 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.
Other criteria in Vulnerability management
- Data processing agreement
- Subprocessor list
- Data location stated
- Status page with history
- Public pricing
- Certifications named
- Uptime SLA with a figure
- HTTPS enforced with HSTS
- security.txt (RFC 9116)
- Notice before subprocessors change
Named privacy contact 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.