Alternatives to Nucleus Security
Other Vulnerability management vendors we measure, sorted by how much they publish that Nucleus Security does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 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 “publishes and Nucleus Security does not” is the one that closes them.
| Vendor | Score | Publishes, and Nucleus Security does not | Nucleus Security publishes, and they do not | |
|---|---|---|---|---|
| Invictiinvicti.com | 83/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 1 Status page with history | Compare |
| Snyksnyk.io | 61/100 | 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 | nothing | Compare |
| Intruderintruder.io | 57/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Wizwiz.io | 57/100 | 3 Data processing agreement, Data location stated, Named privacy contact | nothing | Compare |
| Holm Securityholmsecurity.com | 52/100 | 3 Subprocessor list, Data location stated, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Mendmend.io | 50/100 | 3 Data location stated, Public pricing, Named privacy contact | nothing | Compare |
| SonarSourcesonarsource.com | 48/100 | 3 Data processing agreement, Subprocessor list, Public pricing | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Detectifydetectify.com | 43/100 | 3 Data processing agreement, Public pricing, Named privacy contact | 1 Status page with history | Compare |
| Acunetixacunetix.com | 39/100 | 3 Data location stated, Public pricing, Named privacy contact | 2 Status page with history, Certifications named | Compare |
| JFrogjfrog.com | 39/100 | 3 Data location stated, Public pricing, Named privacy contact | 2 Status page with history, Certifications named | Compare |
| Semgrepsemgrep.dev | 48/100 | 2 Data location stated, Public pricing | nothing | Compare |
| Aqua Securityaquasec.com | 39/100 | 2 Subprocessor list, Named privacy contact | 1 security.txt (RFC 9116) | 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.