Transparency alternatives to Rapid7
Other Vulnerability management vendors we measure, sorted by how much we found at them and not at Rapid7. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Rapid7 on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Rapid7 has 4 gaps in what we could measure: Data location stated, Certifications named, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Rapid7” is the one that closes them.
| Vendor | Score | Found there, not found at Rapid7 | Found at Rapid7, not found there | |
|---|---|---|---|---|
| Invictiinvicti.comSee also Transparency alternatives to Invicti | 83/100 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | 1 Status page with history | Compare |
| Snyksnyk.ioSee also Transparency alternatives to Snyk | 74/100 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | 2 Subprocessor list, Uptime SLA with a figure | Compare |
| Semgrepsemgrep.devSee also Transparency alternatives to Semgrep | 48/100 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +2 | Compare |
| Intruderintruder.ioSee also Transparency alternatives to Intruder | 57/100 | 2 Data location stated, Certifications named | 4 Subprocessor list, Status page with history, Uptime SLA with a figure, +1 | Compare |
| Holm Securityholmsecurity.comSee also Transparency alternatives to Holm Security | 52/100 | 2 Data location stated, Certifications named | 4 Data processing agreement, Public pricing, Uptime SLA with a figure, +1 | Compare |
| Detectifydetectify.comSee also Transparency alternatives to Detectify | 43/100 | 2 Certifications named, security.txt (RFC 9116) | 4 Subprocessor list, Status page with history, Uptime SLA with a figure, +1 | Compare |
| Patchstackpatchstack.comSee also Transparency alternatives to Patchstack | 43/100 | 2 Data location stated, Certifications named | 5 Data processing agreement, Status page with history, Uptime SLA with a figure, +2 | Compare |
| Wizwiz.ioSee also Transparency alternatives to Wiz | 43/100 | 2 Certifications named, security.txt (RFC 9116) | 4 Subprocessor list, Public pricing, Uptime SLA with a figure, +1 | Compare |
| Acunetixacunetix.comSee also Transparency alternatives to Acunetix | 39/100 | 2 Data location stated, security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| StackHawkstackhawk.comSee also Transparency alternatives to StackHawk | 39/100 | 2 Certifications named, security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | Compare |
| Probelyprobely.comSee also Transparency alternatives to Probely | 35/100 | 2 Certifications named, security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +2 | Compare |
| Ox Securityox.securitySee also Transparency alternatives to Ox Security | 27/100 | 2 Data location stated, Certifications named | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | 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.