SaaS Ranking

Alternatives to Palo Alto Networks

Other Network monitoring vendors we measure, sorted by how much they publish that Palo Alto Networks does not. This is a comparison of disclosure, not of features or fitness.

12 shown of 30 that differ from Palo Alto Networks on at least one criterion we measured for both. Public transparency score, not a product or security rating.

Palo Alto Networks has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Palo Alto Networks does not” is the one that closes them.

VendorScorePublishes, and Palo Alto Networks does notPalo Alto Networks publishes, and they do not
Kentikkentik.com 65/100 5 Subprocessor list, Data location stated, Status page with history, +2 1 Certifications named Compare
LogicMonitorlogicmonitor.com 52/100 5 Data processing agreement, Data location stated, Status page with history, +2 2 HTTPS enforced with HSTS, Named privacy contact Compare
Auvikauvik.com 52/100 4 Subprocessor list, Data location stated, Status page with history, +1 1 HTTPS enforced with HSTS Compare
SonicWallsonicwall.com 48/100 3 Subprocessor list, Data location stated, Notice before subprocessors change 1 Named privacy contact Compare
Paesslerpaessler.com 43/100 3 Data location stated, Public pricing, security.txt (RFC 9116) nothing Compare
Netgear Insightnetgear.com 39/100 3 Data location stated, Status page with history, security.txt (RFC 9116) 1 Certifications named Compare
Ubiquitiui.com 35/100 3 Data location stated, Status page with history, security.txt (RFC 9116) 2 Certifications named, Named privacy contact Compare
TP-Link Omadatp-link.com 35/100 2 Data location stated, No third-party tracking before consent 1 Certifications named Compare
Cambiumcambiumnetworks.com 26/100 2 Data location stated, security.txt (RFC 9116) 1 HTTPS enforced with HSTS Compare
Catchpointcatchpoint.com 26/100 2 Status page with history, Public pricing 1 HTTPS enforced with HSTS Compare
Netskopenetskope.com 26/100 2 Data location stated, security.txt (RFC 9116) 2 Certifications named, Named privacy contact Compare
Domotzdomotz.com 22/100 2 Status page with history, security.txt (RFC 9116) 2 Certifications named, Named privacy contact 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.