Transparency alternatives to LogicMonitor
Other Network monitoring vendors we measure, sorted by how much we found at them and not at LogicMonitor. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 that differ from LogicMonitor on at least one criterion we measured for both. Public transparency score, not a product or security rating.
LogicMonitor has 7 gaps in what we could measure: Subprocessor list, Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at LogicMonitor” is the one that closes them.
| Vendor | Score | Found there, not found at LogicMonitor | Found at LogicMonitor, not found there | |
|---|---|---|---|---|
| Kentikkentik.comSee also Transparency alternatives to Kentik | 70/100 | 5 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +2 | 2 Data processing agreement, Certifications named | Compare |
| Auvikauvik.comSee also Transparency alternatives to Auvik | 52/100 | 4 Subprocessor list, Data location stated, Notice before subprocessors change, +1 | 3 Data processing agreement, Public pricing, Uptime SLA with a figure | Compare |
| Paesslerpaessler.comSee also Transparency alternatives to Paessler | 43/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 3 Data processing agreement, Status page with history, Uptime SLA with a figure | Compare |
| WatchGuardwatchguard.comSee also Transparency alternatives to WatchGuard | 39/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| Zscalerzscaler.comSee also Transparency alternatives to Zscaler | 43/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 4 Status page with history, Public pricing, Certifications named, +1 | Compare |
| Ubiquitiui.comSee also Transparency alternatives to Ubiquiti | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| Cambiumcambiumnetworks.comSee also Transparency alternatives to Cambium | 26/100 | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | 4 Data processing agreement, Status page with history, Public pricing, +1 | Compare |
| Eleven Softwareelevensoftware.comSee also Transparency alternatives to Eleven Software | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| Netgear Insightnetgear.comSee also Transparency alternatives to Netgear Insight | 26/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| Icingaicinga.comSee also Transparency alternatives to Icinga | 22/100 | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| TP-Link Omadatp-link.comSee also Transparency alternatives to TP-Link Omada | 22/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| Securepointsecurepoint.deSee also Transparency alternatives to Securepoint | 17/100 | 3 No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | 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.