Alternatives to StackHawk
Other Vulnerability management vendors we measure, sorted by how much they publish that StackHawk does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 that differ from StackHawk on at least one criterion we measured for both. Public transparency score, not a product or security rating.
StackHawk has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and StackHawk does not” is the one that closes them.
| Vendor | Score | Publishes, and StackHawk does not | StackHawk publishes, and they do not | |
|---|---|---|---|---|
| Invictiinvicti.com | 83/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 1 Status page with history | Compare |
| Intruderintruder.io | 57/100 | 4 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +1 | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | Compare |
| Snyksnyk.io | 61/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | nothing | Compare |
| Wizwiz.io | 57/100 | 3 Data processing agreement, Data location stated, HTTPS enforced with HSTS | 1 Public pricing | Compare |
| Holm Securityholmsecurity.com | 52/100 | 3 Subprocessor list, Data location stated, HTTPS enforced with HSTS | 2 Public pricing, security.txt (RFC 9116) | Compare |
| SonarSourcesonarsource.com | 48/100 | 3 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | Compare |
| Mendmend.io | 50/100 | 2 Data location stated, HTTPS enforced with HSTS | nothing | Compare |
| Semgrepsemgrep.dev | 48/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Detectifydetectify.com | 43/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| Acunetixacunetix.com | 39/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Status page with history, Certifications named | Compare |
| Aqua Securityaquasec.com | 39/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 2 Public pricing, security.txt (RFC 9116) | Compare |
| JFrogjfrog.com | 39/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Status page with history, Certifications named | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.