SaaS Ranking
Menu

Upstream Security

upstream.auto · SIEM and security operations · checked 2026-09-18

17/100FBand F

Rank 30 of 39 in SIEM and security operations, where the median is 26.

We measured 12 of 12 criteria for Upstream Security on 2026-09-18. We found 3 with a source and did not find 9 at the addresses we checked. That is a transparency score of 17 out of 100, band F.

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

Upstream Security

upstream.auto · SIEM and security operations

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

Published commitments2 of 9 found

Measured behaviour1 of 3 found

Checked 2026-09-18. 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 Upstream Security has no such document.

Where Upstream Security sits in SIEM and security operations

  1. A0 0%
  2. B0 0%
  3. C2 5%
  4. D2 5%
  5. E16 41%
  6. F19 49%
39 vendors with a score; 3 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Upstream Security 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 they state

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

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-18.

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

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-18.

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

Is this wrong? Send us the URL

✗

Data location stated

weight 3 of 3

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

Seen at https://upstream.auto/privacy-policy/ · checked 2026-09-18

Show the 7 addresses we checked
  1. https://upstream.auto/security – reached, no match (HTTP 200)
  2. https://upstream.auto/trust – reached, no match (HTTP 404)
  3. https://upstream.auto/legal/privacy – reached, no match (HTTP 404)
  4. https://upstream.auto/privacy – found, but behind a sign-in
  5. https://upstream.auto/privacy-policy – found, but behind a sign-in
  6. https://upstream.auto/compliance – reached, no match (HTTP 200)
  7. https://upstream.auto/legal/privacy-policy – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-18.

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

Is this wrong? Send us the URL

✗

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-18.

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

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

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

Checked 1 address on 2026-09-18.

Show the 1 address we checked
  1. https://upstream.auto/ – third-party requests before any interaction: cdn.jsdelivr.net, consent.cookiebot.com, consentcdn.cookiebot.com, fonts.googleapis.com, fonts.gstatic.com, js.hs-scripts.com, public.rive.app, rive.app, static.cloudflareinsights.com, unpkg.com

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-18.

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

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-18.

Show the 6 addresses we checked
  1. https://upstream.auto/legal/sla – reached, no match (HTTP 404)
  2. https://upstream.auto/sla – reached, no match (HTTP 404)
  3. https://upstream.auto/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://upstream.auto/trust/sla – reached, no match (HTTP 404)
  5. https://upstream.auto/uptime – reached, no match (HTTP 404)
  6. https://upstream.auto/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-18.

Show the 1 address we checked
  1. https://upstream.auto/.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 3
✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000; includeSubDomains; preload

    Read at https://upstream.auto/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=31536000; includeSubDomains; preload

    Read at https://upstream.auto/

    max-age=31536000; includeSubDomains; preload

    Read at https://upstream.auto/

Source: https://upstream.auto/ · checked 2026-09-18

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page ISO 9001 (not counted: the sentence does not carry it), ISO/IEC 27001 (not counted: the sentence does not carry it), SOC 2 Type II, TISAX (unclear from the sentence). The sentence we kept does not carry this finding on its own, so it counts in no list and no figure.
    Show the 4 exact wordings

    ISO 9001:2015 ISO 9001 serves as the global standard outlining requirements for a quality management system

    Read at https://upstream.auto/security-compliance/

    ISO/IEC 27001:2022 ISO 27001 is a specification for an information security management system (ISMS), which is a

    Read at https://upstream.auto/security-compliance/

    ecurity LTD Upstream's Assessment ID: AZ67V0-1 Upstream's Assessment Level 3 (AL3) scope ID: SMN155 SOC 2 Type 2 A SOC 2 Type 2 report is an internal control report capturing how Upstream Security saf...

    Read at https://upstream.auto/security-compliance/

    ighest standards of security, reliability, privacy and compliance in the industry Disclosure Policy TISAX Used by European automotive companies to provide a common information security assessment for....

    Read at https://upstream.auto/security-compliance/

Source: https://upstream.auto/security-compliance/ · checked 2026-09-18

✓

Named privacy contact

weight 1 of 3

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

Source: https://upstream.auto/privacy-policy/ · checked 2026-09-18

History

100 0 2026-09-16: 17 of 1002026-09-18: 17 of 100 2026-09-16 2026-09-18
Score over the last 2 runs we measured Upstream Security in: 17 (2026-09-16), 17 (2026-09-18).

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.