Transparency alternatives to Security Onion
Other SIEM and security operations vendors we measure, sorted by how much we found at them and not at Security Onion. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 that differ from Security Onion on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Security Onion has 12 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, 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 Security Onion” is the one that closes them.
| Vendor | Score | Found there, not found at Security Onion | Found at Security Onion, not found there | |
|---|---|---|---|---|
| Expelexpel.comSee also Transparency alternatives to Expel | 70/100 | 9 Data processing agreement, Data location stated, Public pricing, +6 | nothing | Compare |
| Huntresshuntress.comSee also Transparency alternatives to Huntress | 57/100 | 7 Data location stated, Status page with history, Public pricing, +4 | nothing | Compare |
| Pantherpanther.comSee also Transparency alternatives to Panther | 52/100 | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | nothing | Compare |
| Ontinueontinue.comSee also Transparency alternatives to Ontinue | 43/100 | 5 Subprocessor list, Data location stated, security.txt (RFC 9116), +2 | nothing | Compare |
| Gigamongigamon.comSee also Transparency alternatives to Gigamon | 35/100 | 5 Data location stated, Certifications named, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Trend Microtrendmicro.comSee also Transparency alternatives to Trend Micro | 35/100 | 5 Data processing agreement, Public pricing, Certifications named, +2 | nothing | Compare |
| Blumirablumira.comSee also Transparency alternatives to Blumira | 30/100 | 5 Public pricing, Certifications named, Uptime SLA with a figure, +2 | nothing | Compare |
| WithSecurewithsecure.comSee also Transparency alternatives to WithSecure | 35/100 | 4 Data processing agreement, Status page with history, Certifications named, +1 | nothing | Compare |
| Corelightcorelight.comSee also Transparency alternatives to Corelight | 30/100 | 4 Status page with history, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | nothing | Compare |
| Corocoro.netSee also Transparency alternatives to Coro | 30/100 | 4 Data processing agreement, Certifications named, Notice before subprocessors change, +1 | nothing | Compare |
| Cynetcynet.comSee also Transparency alternatives to Cynet | 30/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Exabeamexabeam.comSee also Transparency alternatives to Exabeam | 30/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | nothing | 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.