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