Alternatives to Cato Networks
Other Network monitoring vendors we measure, sorted by how much they publish that Cato Networks does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 20 that differ from Cato Networks on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cato Networks has 10 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, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Cato Networks does not” is the one that closes them.
| Vendor | Score | Publishes, and Cato Networks does not | Cato Networks publishes, and they do not | |
|---|---|---|---|---|
| Kentikkentik.com | 65/100 | 6 Subprocessor list, Data location stated, Status page with history, +3 | nothing | Compare |
| Auvikauvik.com | 52/100 | 6 Subprocessor list, Data location stated, Status page with history, +3 | 1 HTTPS enforced with HSTS | Compare |
| LogicMonitorlogicmonitor.com | 52/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | 1 HTTPS enforced with HSTS | Compare |
| Paesslerpaessler.com | 43/100 | 5 Data location stated, Public pricing, Certifications named, +2 | nothing | Compare |
| Netgear Insightnetgear.com | 39/100 | 4 Data location stated, Status page with history, security.txt (RFC 9116), +1 | nothing | Compare |
| Cambiumcambiumnetworks.com | 26/100 | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | 1 HTTPS enforced with HSTS | Compare |
| Catchpointcatchpoint.com | 26/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 1 HTTPS enforced with HSTS | Compare |
| Icingaicinga.com | 22/100 | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | 1 HTTPS enforced with HSTS | Compare |
| Netskopenetskope.com | 26/100 | 2 Data location stated, security.txt (RFC 9116) | nothing | Compare |
| Domotzdomotz.com | 22/100 | 2 Status page with history, security.txt (RFC 9116) | nothing | Compare |
| Nile Networksnilesecure.com | 22/100 | 2 Data location stated, Status page with history | 1 HTTPS enforced with HSTS | Compare |
| Obkioobkio.com | 17/100 | 2 Status page with history, Public pricing | 1 HTTPS enforced with HSTS | 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.