Transparency alternatives to Nucleus Security
Other Vulnerability management vendors we measure, sorted by how much we found at them and not at Nucleus Security. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Nucleus Security on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Nucleus Security has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Nucleus Security” is the one that closes them.
| Vendor | Score | Found there, not found at Nucleus Security | Found at Nucleus Security, not found there | |
|---|---|---|---|---|
| Invictiinvicti.comSee also Transparency alternatives to Invicti | 83/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 1 Status page with history | Compare |
| Rapid7rapid7.comSee also Transparency alternatives to Rapid7 | 70/100 | 6 Data processing agreement, Subprocessor list, Public pricing, +3 | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Snyksnyk.ioSee also Transparency alternatives to Snyk | 61/100 | 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 | nothing | Compare |
| Intruderintruder.ioSee also Transparency alternatives to Intruder | 57/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Sucurisucuri.netSee also Transparency alternatives to Sucuri | 52/100 | 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Arnicaarnica.ioSee also Transparency alternatives to Arnica | 48/100 | 4 Subprocessor list, Data location stated, Public pricing, +1 | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Patchstackpatchstack.comSee also Transparency alternatives to Patchstack | 43/100 | 4 Subprocessor list, Data location stated, Public pricing, +1 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Holm Securityholmsecurity.comSee also Transparency alternatives to Holm Security | 52/100 | 3 Subprocessor list, Data location stated, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| SonarSourcesonarsource.comSee also Transparency alternatives to SonarSource | 48/100 | 3 Data processing agreement, Subprocessor list, Public pricing | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Detectifydetectify.comSee also Transparency alternatives to Detectify | 43/100 | 3 Data processing agreement, Public pricing, Named privacy contact | 1 Status page with history | Compare |
| Acunetixacunetix.comSee also Transparency alternatives to Acunetix | 39/100 | 3 Data location stated, Public pricing, Named privacy contact | 2 Status page with history, Certifications named | Compare |
| Semgrepsemgrep.devSee also Transparency alternatives to Semgrep | 48/100 | 2 Data location stated, Public pricing | nothing | 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.