Alternatives to Securepoint
Other Network monitoring vendors we measure, sorted by how much they publish that Securepoint does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 36 that differ from Securepoint on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Securepoint has 9 gaps in what we could measure: 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, Notice before subprocessors change. The column “publishes and Securepoint does not” is the one that closes them.
| Vendor | Score | Publishes, and Securepoint does not | Securepoint publishes, and they do not | |
|---|---|---|---|---|
| Kentikkentik.com | 65/100 | 6 Subprocessor list, Data location stated, Status page with history, +3 | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| LogicMonitorlogicmonitor.com | 52/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | 3 No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact | Compare |
| Auvikauvik.com | 57/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| SonicWallsonicwall.com | 48/100 | 5 Subprocessor list, Data location stated, Certifications named, +2 | 3 No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact | Compare |
| Paesslerpaessler.com | 43/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 1 No third-party tracking before consent | Compare |
| Zscalerzscaler.com | 43/100 | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | 3 No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact | Compare |
| Netgear Insightnetgear.com | 39/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| WatchGuardwatchguard.com | 39/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Ubiquitiui.com | 35/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 2 No third-party tracking before consent, Named privacy contact | Compare |
| Catchpointcatchpoint.com | 26/100 | 3 Status page with history, Public pricing, Certifications named | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| TP-Link Omadatp-link.com | 35/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Cambiumcambiumnetworks.com | 26/100 | 2 Data location stated, Certifications named | 1 No third-party tracking before consent | 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.