SaaS Ranking
Menu

Stackrox: what they publish

stackrox.io · Container and cloud workload security · checked 2026-09-28

0/100FBand F

Rank 25 of 26 in Container and cloud workload security, where the median is 22.

We measured 12 of 12 criteria for Stackrox on 2026-09-28. We found 0 with a source and did not find 12 at the addresses we checked. That is a transparency score of 0 out of 100, band F.

Jump to a criterion 12

Overview

0 days since the newest finding, 0 since the oldest. 12 of 12 criteria measured in the last 30 days.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

Stackrox

stackrox.io · Container and cloud workload security

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
F 0of 100 Rank 25 of 26

Published commitments0 of 9 found

Measured behaviour0 of 3 found

Checked 2026-09-28. 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.

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

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 Stackrox has no such document.

Where Stackrox sits in Container and cloud workload security

  1. A0 0%
  2. B0 0%
  3. C0 0%
  4. D5 19%
  5. E6 23%
  6. F15 58%
26 vendors with a score; 2 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Stackrox is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

What Stackrox states

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Data processing agreement (DPA)

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-28.

Show the 8 addresses we checked
  1. https://stackrox.io/legal/dpa – reached, no match (HTTP 404)
  2. https://stackrox.io/dpa – reached, no match (HTTP 404)
  3. https://stackrox.io/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://stackrox.io/data-processing-agreement – reached, no match (HTTP 404)
  5. https://stackrox.io/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://stackrox.io/legal/gdpr – reached, no match (HTTP 404)
  7. https://stackrox.io/trust/dpa – reached, no match (HTTP 404)
  8. https://stackrox.io/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Data processing agreement in Container and cloud workload security: 3 of 26 companies

✗

Subprocessors: the published list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-28.

Show the 7 addresses we checked
  1. https://stackrox.io/legal/subprocessors – reached, no match (HTTP 404)
  2. https://stackrox.io/subprocessors – reached, no match (HTTP 404)
  3. https://stackrox.io/sub-processors – reached, no match (HTTP 404)
  4. https://stackrox.io/legal/sub-processors – reached, no match (HTTP 404)
  5. https://stackrox.io/trust/subprocessors – reached, no match (HTTP 404)
  6. https://stackrox.io/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://stackrox.io/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Subprocessor list in Container and cloud workload security: 2 of 26 companies

✗

Data location: where they say data is hosted

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-09-28.

Show the 7 addresses we checked
  1. https://stackrox.io/security – reached, no match (HTTP 404)
  2. https://stackrox.io/trust – reached, no match (HTTP 404)
  3. https://stackrox.io/legal/privacy – reached, no match (HTTP 404)
  4. https://stackrox.io/privacy – reached, no match (HTTP 404)
  5. https://stackrox.io/privacy-policy – reached, no match (HTTP 404)
  6. https://stackrox.io/compliance – reached, no match (HTTP 404)
  7. https://stackrox.io/legal/privacy-policy – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Data location stated in Container and cloud workload security: 9 of 26 companies

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-28.

Show the 3 addresses we checked
  1. https://status.stackrox.io/ – The name "status.stackrox.io" could not be resolved.
  2. https://stackrox.io/status – reached, no match (HTTP 404)
  3. https://stackrox.io.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Status page with history in Container and cloud workload security: 4 of 27 companies

✗

Public pricing with figures

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-28.

Show the 5 addresses we checked
  1. https://stackrox.io/pricing – reached, no match (HTTP 404)
  2. https://stackrox.io/pricing/ – reached, no match (HTTP 404)
  3. https://stackrox.io/plans – reached, no match (HTTP 404)
  4. https://stackrox.io/en/pricing – reached, no match (HTTP 404)
  5. https://stackrox.io/pricing-plans – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Public pricing in Container and cloud workload security: 6 of 26 companies

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-28.

Show the 2 addresses we checked
  1. http://stackrox.io/ – redirects to https://stackrox.io/
  2. https://stackrox.io/ – no HSTS header

Is this wrong? Send us the URL

Across the market: HTTPS enforced with HSTS in Container and cloud workload security: 22 of 28 companies

✗weight 2 of 3

Third-party requests seen on the first load, before any interaction.

Checked 1 address on 2026-09-28.

Show the 1 address we checked
  1. https://stackrox.io/ – third-party requests before any interaction: adobedc.demdex.net, analytics.twitter.com, assets.adobedtm.com, cm.everesttech.net, cm.g.doubleclick.net, dpm.demdex.net, match.adsrvr.org, match.prod.bidr.io, ml314.com, smetrics.redhat.com, static.redhat.com, www.redhat.com, www.youtube.com

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Container and cloud workload security: 2 of 28 companies

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-28.

Show the 8 addresses we checked
  1. https://stackrox.io/legal/subprocessors – reached, no match (HTTP 404)
  2. https://stackrox.io/subprocessors – reached, no match (HTTP 404)
  3. https://stackrox.io/sub-processors – reached, no match (HTTP 404)
  4. https://stackrox.io/legal/dpa – reached, no match (HTTP 404)
  5. https://stackrox.io/dpa – reached, no match (HTTP 404)
  6. https://stackrox.io/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://stackrox.io/trust/subprocessors – reached, no match (HTTP 404)
  8. https://stackrox.io/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Notice before subprocessors change in Container and cloud workload security: 3 of 26 companies

✗

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-28.

Show the 6 addresses we checked
  1. https://stackrox.io/security – reached, no match (HTTP 404)
  2. https://stackrox.io/trust – reached, no match (HTTP 404)
  3. https://stackrox.io/trust-center – reached, no match (HTTP 404)
  4. https://stackrox.io/compliance – reached, no match (HTTP 404)
  5. https://stackrox.io/legal/security – reached, no match (HTTP 404)
  6. https://trust.stackrox.io/ – The name "trust.stackrox.io" could not be resolved.

Is this wrong? Send us the URL

Across the market: Certifications named in Container and cloud workload security: 8 of 27 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-28.

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

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in Container and cloud workload security: 2 of 26 companies

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-28.

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

Is this wrong? Send us the URL

Across the market: security.txt (RFC 9116) in Container and cloud workload security: 2 of 26 companies

✗

Named privacy contact (DPO or privacy address)

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-09-28.

Show the 7 addresses we checked
  1. https://stackrox.io/legal/privacy – reached, no match (HTTP 404)
  2. https://stackrox.io/privacy – reached, no match (HTTP 404)
  3. https://stackrox.io/privacy-policy – reached, no match (HTTP 404)
  4. https://stackrox.io/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://stackrox.io/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://stackrox.io/trust/privacy – reached, no match (HTTP 404)
  7. https://stackrox.io/datenschutz – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Named privacy contact in Container and cloud workload security: 10 of 26 companies

Evidence

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

Nothing to show here yet.

History

100 0 2026-09-21: 0 of 1002026-09-28: 0 of 100 2026-09-21 2026-09-28
Score over the last 2 runs we measured Stackrox in: 0 (2026-09-21), 0 (2026-09-28).

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.