Duo Security
duo.com · Password and identity · checked 2026-09-03
Rank 7 of 21 in Password and identity, where the median is 40.
- 6 found
- 6 not found
- 0 not measured
We measured 12 of 12 criteria for Duo Security on 2026-09-03. We found 6 with a source and did not find 6 at the addresses we checked. That is a transparency score of 48 out of 100, band D.
Overview
Transparency labelsaas-ranking.com
Duo Security
- A
- B
- C
- D
- E
- F
Published commitments4 of 9 found
- not foundData processing agreement×3
- not foundSubprocessor list×3
- foundData location stated×3
- foundStatus page with history×2
- foundPublic pricing×2
- not foundNotice before subprocessors change×2
- foundCertifications named×1
- not foundUptime SLA with a figure×1
- not foundNamed privacy contact×1
Measured behaviour2 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- 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 Duo Security has no such document.
Gaps, heaviest first
Data processing agreement
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://duo.com/legal/dpa– reached, no match (HTTP 404)https://duo.com/dpa– reached, no match (HTTP 404)https://duo.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://duo.com/data-processing-agreement– reached, no match (HTTP 404)https://duo.com/legal/data-processing-addendum– reached, no match (HTTP 404)https://duo.com/legal/gdpr– reached, no match (HTTP 404)https://duo.com/trust/dpa– reached, no match (HTTP 404)https://duo.com/privacy/dpa– reached, no match (HTTP 404)
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://duo.com/legal/subprocessors– reached, no match (HTTP 404)https://duo.com/subprocessors– reached, no match (HTTP 404)https://duo.com/sub-processors– reached, no match (HTTP 404)https://duo.com/legal/sub-processors– reached, no match (HTTP 404)https://duo.com/trust/subprocessors– reached, no match (HTTP 404)https://duo.com/privacy/subprocessors– reached, no match (HTTP 404)https://duo.com/legal/subprocessor-list– 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://duo.com/– third-party requests before any interaction: browser.sentry-cdn.com, cdn.cookielaw.org, distillery.wistia.com, embed-cloudfront.wistia.com, fast.wistia.com, fast.wistia.net, forums-tags.cisco.com, geolocation.onetrust.com, pipedream.wistia.com, tags.tiqcdn.com, www.cisco.com
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://duo.com/legal/subprocessors– reached, no match (HTTP 404)https://duo.com/subprocessors– reached, no match (HTTP 404)https://duo.com/sub-processors– reached, no match (HTTP 404)https://duo.com/legal/dpa– reached, no match (HTTP 404)https://duo.com/dpa– reached, no match (HTTP 404)https://duo.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://duo.com/trust/subprocessors– reached, no match (HTTP 404)https://duo.com/legal/sub-processors– reached, no match (HTTP 404)
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://duo.com/legal/sla– reached, no match (HTTP 200)https://duo.com/sla– reached, no match (HTTP 200)https://duo.com/legal/service-level-agreement– reached, no match (HTTP 404)https://duo.com/trust/sla– reached, no match (HTTP 404)https://duo.com/uptime– reached, no match (HTTP 404)https://duo.com/legal/uptime-sla– reached, no match (HTTP 404)
Named privacy contact
weight 1 of 3No named privacy contact found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://duo.com/legal/privacy– reached, no match (HTTP 200)https://duo.com/privacy– reached, no match (HTTP 200)https://duo.com/privacy-policy– reached, no match (HTTP 404)https://duo.com/legal/privacy-policy– reached, no match (HTTP 404)https://duo.com/legal/privacy-notice– reached, no match (HTTP 404)https://duo.com/trust/privacy– reached, no match (HTTP 404)https://duo.com/datenschutz– 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 6
Data location stated
weight 3 of 3The hosting location is stated on a public page.
Source: https://duo.com/support/security-and-reliability · checked 2026-09-03
Status page with history
weight 2 of 3A public status page with incident history.
Source: https://status.duo.com/ · checked 2026-09-03
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://duo.com/editions-and-pricing · checked 2026-09-03
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://duo.com/ · checked 2026-09-03
Certifications named
weight 1 of 3SOC 2 or ISO 27001 named on a public page.
Source: https://duo.com/support/security-and-reliability · checked 2026-09-03
security.txt (RFC 9116)
weight 1 of 3Served at /.well-known/security.txt.
Source: https://duo.com/.well-known/security.txt · checked 2026-09-03
History
Not enough completed runs yet to draw a line. The next runs fill this in.