SaaS Ranking

Transparency alternatives to Hunters

Other SIEM and security operations vendors we measure, sorted by how much we found at them and not at Hunters. This is a comparison of disclosure, not of features or fitness.

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

Hunters has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Hunters” is the one that closes them.

VendorScoreFound there, not found at HuntersFound at Hunters, not found there
Expelexpel.comSee also Transparency alternatives to Expel 61/100 5 Data processing agreement, Certifications named, Uptime SLA with a figure, +2 nothing Compare
Trend Microtrendmicro.comSee also Transparency alternatives to Trend Micro 48/100 5 Data processing agreement, Subprocessor list, Public pricing, +2 2 Data location stated, HTTPS enforced with HSTS Compare
Huntresshuntress.comSee also Transparency alternatives to Huntress 57/100 4 Status page with history, Public pricing, Certifications named, +1 nothing Compare
Pantherpanther.comSee also Transparency alternatives to Panther 43/100 4 Data processing agreement, Subprocessor list, Certifications named, +1 2 Data location stated, Named privacy contact Compare
Ontinueontinue.comSee also Transparency alternatives to Ontinue 43/100 3 Subprocessor list, security.txt (RFC 9116), Notice before subprocessors change 1 HTTPS enforced with HSTS Compare
WithSecurewithsecure.comSee also Transparency alternatives to WithSecure 35/100 3 Data processing agreement, Status page with history, Certifications named 2 Data location stated, Named privacy contact Compare
Blumirablumira.comSee also Transparency alternatives to Blumira 30/100 3 Public pricing, Certifications named, Uptime SLA with a figure 1 Data location stated Compare
Corocoro.netSee also Transparency alternatives to Coro 30/100 3 Data processing agreement, Certifications named, Notice before subprocessors change 2 Data location stated, HTTPS enforced with HSTS Compare
Arctic Wolfarcticwolf.comSee also Transparency alternatives to Arctic Wolf 26/100 3 Status page with history, Certifications named, security.txt (RFC 9116) 2 Data location stated, Named privacy contact Compare
Atomicorp Atomic OSSECatomicorp.comSee also Transparency alternatives to Atomicorp Atomic OSSEC 26/100 3 Public pricing, Certifications named, security.txt (RFC 9116) 2 Data location stated, Named privacy contact Compare
Gigamongigamon.comSee also Transparency alternatives to Gigamon 35/100 2 Certifications named, security.txt (RFC 9116) nothing Compare
Corelightcorelight.comSee also Transparency alternatives to Corelight 30/100 2 Status page with history, Notice before subprocessors change 1 Data location stated 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.