StrongDM
strongdm.com · Privileged access management · checked 2026-09-03
Rank 4 of 21 in Privileged access management, where the median is 22.
- 8 found
- 4 not found
- 0 not measured
We measured 12 of 12 criteria for StrongDM on 2026-09-03. We found 8 with a source and did not find 4 at the addresses we checked. That is a transparency score of 65 out of 100, band C.
Overview
Transparency labelsaas-ranking.com
StrongDM
- A
- B
- C
- D
- E
- F
Published commitments7 of 9 found
- foundData processing agreement×3
- not foundSubprocessor list×3
- foundData location stated×3
- foundStatus page with history×2
- not foundPublic pricing×2
- foundNotice before subprocessors change×2
- foundCertifications named×1
- foundUptime SLA with a figure×1
- foundNamed privacy contact×1
Measured behaviour1 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
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 StrongDM has no such document.
Gaps, heaviest first
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://strongdm.com/legal/subprocessors– reached, no match (HTTP 404)https://strongdm.com/subprocessors– reached, no match (HTTP 404)https://strongdm.com/sub-processors– reached, no match (HTTP 404)https://strongdm.com/legal/sub-processors– reached, no match (HTTP 404)https://strongdm.com/trust/subprocessors– reached, no match (HTTP 404)https://strongdm.com/privacy/subprocessors– reached, no match (HTTP 404)https://strongdm.com/legal/subprocessor-list– reached, no match (HTTP 404)
Public pricing
weight 2 of 3No public pricing with figures found.
Checked 5 addresses on 2026-09-03.
Show the 5 addresses we checked
https://strongdm.com/pricing– reached and rendered, no matchhttps://strongdm.com/pricing/– reached, no match (HTTP 200)https://strongdm.com/plans– reached, no match (HTTP 404)https://strongdm.com/en/pricing– reached, no match (HTTP 404)https://strongdm.com/pricing-plans– reached, no match (HTTP 404)
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://strongdm.com/– third-party requests before any interaction: 7052064.fs1.hubspotusercontent-na1.net, a.burly.io, api.cr-relay.com, api.hubapi.com, api.vector.co, app.hubspot.com, cdn.cookielaw.org, cdn.cr-relay.com, cdn.vector.co, cta-service-cms2.hubspot.com, f.vimeocdn.com, fonts.googleapis.com, fonts.gstatic.com, forms.hscollectedforms.net, g.clarity.ms, geolocation.onetrust.com, i.vimeocdn.com, ibc-flow.techtarget.com, js.hs-analytics.net, js.hs-banner.com, js.hsadspixel.net, js.hscollectedforms.net, js.hubspot.com, perf-na1.hsforms.com, player.vimeo.com, px.ads.linkedin.com, scripts.clarity.ms, snap.licdn.com, static.hsappstatic.net, static.hubspot.com, strongdm-21126185.hs-sites.com, trk.techtarget.com, ws.zoominfo.com, www.clarity.ms, www.google-analytics.com, www.googletagmanager.com
security.txt (RFC 9116)
weight 1 of 3No security.txt found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://strongdm.com/.well-known/security.txt– reached, no match (HTTP 404)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 8
Data processing agreement
weight 3 of 3Published and readable without a login.
Source: https://www.strongdm.com/legal/data-processing-agreement · checked 2026-09-03
Data location stated
weight 3 of 3The hosting location is stated on a public page.
Source: https://www.strongdm.com/privacy · checked 2026-09-03
Status page with history
weight 2 of 3A public status page with incident history.
Source: https://status.strongdm.com/ · checked 2026-09-03
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://strongdm.com/ · checked 2026-09-03
Notice before subprocessors change
weight 2 of 3The vendor commits publicly to giving notice before the list changes.
Source: https://www.strongdm.com/legal/data-processing-agreement · checked 2026-09-03
Certifications named
weight 1 of 3SOC 2 or ISO 27001 named on a public page.
Source: https://www.strongdm.com/ · checked 2026-09-03
Uptime SLA with a figure
weight 1 of 3An availability commitment with a figure.
Source: https://www.strongdm.com/legal/service-level-agreement · checked 2026-09-03
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://www.strongdm.com/privacy · checked 2026-09-03
History
Not enough completed runs yet to draw a line. The next runs fill this in.