SaaS Ranking
Menu

Huntress

huntress.com · SIEM and security operations · checked 2026-09-03

57/100CBand C

Rank 1 of 17 in SIEM and security operations, where the median is 30.

We measured 12 of 12 criteria for Huntress on 2026-09-03. We found 7 with a source and did not find 5 at the addresses we checked. That is a transparency score of 57 out of 100, band C.

Overview

Transparency labelsaas-ranking.com

Huntress

huntress.com · SIEM and security operations

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
C 57of 100 Rank 1 of 17

Published commitments6 of 9 found

Measured behaviour1 of 3 found

Checked 2026-09-03. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Huntress has no such document.

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://trust.huntress.com/?itemUid=c4223a81-5840-4e11-ac9f-2b812794a67e&source=click · checked 2026-09-03

Show the 8 addresses we checked
  1. https://huntress.com/legal/dpa – reached, no match (HTTP 404)
  2. https://huntress.com/dpa – reached, no match (HTTP 404)
  3. https://huntress.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://huntress.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://huntress.com/legal/data-processing-addendum – found, but behind a sign-in
  6. https://huntress.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://huntress.com/trust/dpa – reached, no match (HTTP 404)
  8. https://huntress.com/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://trust.huntress.com/?itemUid=e3fae2ca-94a9-416b-b577-5c90e382df57&source=click · checked 2026-09-03

Show the 7 addresses we checked
  1. https://huntress.com/legal/subprocessors – found, but behind a sign-in
  2. https://huntress.com/subprocessors – reached, no match (HTTP 404)
  3. https://huntress.com/sub-processors – reached, no match (HTTP 404)
  4. https://huntress.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://huntress.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://huntress.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://huntress.com/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-03.

Show the 1 address we checked
  1. https://huntress.com/ – third-party requests before any interaction: a5179843176824832.cdn.optimizely.com, app.qualified.com, cdn.builder.io, cdn.optimizely.com, js.qualified.com, logx.optimizely.com, www.googletagmanager.com

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-03.

Show the 6 addresses we checked
  1. https://huntress.com/legal/sla – reached, no match (HTTP 404)
  2. https://huntress.com/sla – reached, no match (HTTP 404)
  3. https://huntress.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://huntress.com/trust/sla – reached, no match (HTTP 404)
  5. https://huntress.com/uptime – reached, no match (HTTP 404)
  6. https://huntress.com/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-03.

Show the 1 address we checked
  1. https://huntress.com/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 7
✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://www.huntress.com/privacy-policy · checked 2026-09-03

✓

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.huntress.com/ · checked 2026-09-03

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.huntress.com/pricing · checked 2026-09-03

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://huntress.com/ · checked 2026-09-03

✓

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://trust.huntress.com/?itemUid=e3fae2ca-94a9-416b-b577-5c90e382df57&source=click · checked 2026-09-03

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://trust.huntress.com/ · checked 2026-09-03

✓

Named privacy contact

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://www.huntress.com/privacy-policy · checked 2026-09-03

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare