Alternatives to CrowdStrike
Other Endpoint management and security vendors we measure, sorted by how much they publish that CrowdStrike does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 that differ from CrowdStrike on at least one criterion we measured for both. Public transparency score, not a product or security rating.
CrowdStrike has 6 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and CrowdStrike does not” is the one that closes them.
| Vendor | Score | Publishes, and CrowdStrike does not | CrowdStrike publishes, and they do not | |
|---|---|---|---|---|
| Addigyaddigy.com | 85/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 1 security.txt (RFC 9116) | Compare |
| Malwarebytesmalwarebytes.com | 83/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 1 Certifications named | Compare |
| Automoxautomox.com | 60/100 | 2 Data processing agreement, Uptime SLA with a figure | 1 security.txt (RFC 9116) | Compare |
| Kaseyakaseya.com | 35/100 | 2 Subprocessor list, Status page with history | 4 Data location stated, Public pricing, Certifications named, +1 | Compare |
| SentinelOnesentinelone.com | 55/100 | 1 Status page with history | nothing | Compare |
| NinjaOneninjaone.com | 52/100 | 1 Status page with history | nothing | Compare |
| Fleetfleetdm.com | 48/100 | 1 Status page with history | 1 security.txt (RFC 9116) | Compare |
| Iruiru.com | 43/100 | 1 Data processing agreement | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Miradoremiradore.com | 39/100 | 1 Data processing agreement | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| Jamfjamf.com | 35/100 | 1 Status page with history | 2 Data location stated, Named privacy contact | Compare |
| Syncrosyncromsp.com | 35/100 | 1 Status page with history | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| Action1action1.com | 30/100 | 1 Data processing agreement | 3 Data location stated, Public pricing, 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.