Cisco Duo Desktop
snapshot-20260917 commercialThe section your link pointed to isn't on Cisco Duo Desktop's page any more, so we've brought you to the top.
Cisco Duo Desktop is a native client application that checks the security posture of laptops and desktops to control access to corporate applications.
mkdir -p /Library/Application\ Support/Duo/Duo\ Device\ Health/ mkdir -p /Library/Application\ Support/Duo/Duo\ Device\ Health/
Summary
Cisco Duo Desktop is a commercial secure-access application that checks a laptop or desktop's security posture before letting it reach corporate applications. It runs as a native client on Linux, macOS, and Windows, working alongside Duo's browser-based authentication prompt to enforce access policies set by an administrator, with results and endpoint details surfacing in the Duo Admin Panel; using it requires a Duo Essentials, Advantage, or Premier subscription. It's built for IT and security administrators who manage device-based access policies rather than end users configuring their own machines. It sits in the secure-access and endpoint-posture space alongside device-trust and conditional-access controls from broader identity platforms. Originating in 2010, it remains actively maintained, with ten tracked releases and the latest shipped 34 days ago.
Cisco Duo Desktop is a native client application that checks the security posture of laptops and desktops to control access to corporate applications.
How Cisco Duo Desktop helps
Will this device be let through when it tries to reach a protected application?
checks the device's security posture against the administrator's policy at the moment of authentication in the browser-based prompt, and blocks the login if the device fails the requirement
What is actually wrong with a device that just got denied access?
shows the user the specific reason the policy check failed and lists the remediation steps needed to bring the device back into compliance
Which endpoint security agents are actually running on a given laptop?
detects installed security agents such as antivirus, EDR, and management tools on macOS and Windows and surfaces that inventory in the Duo Admin Panel
Is a login coming from a real physical machine or a virtual one impersonating it?
flags Google Compute Engine and Microsoft Azure virtual environments so a cloud instance authenticating as a laptop stands out from genuine hardware
Are a user's devices actually keeping themselves updated?
reports the operating system's automatic update status and whether a management agent is present, giving administrators visibility beyond the pass/fail policy result
Could someone else's device information be forged to pass as this user's?
notes that transmitted posture data isn't uniquely tied to a device, so a bad actor could intercept and fabricate a response, a risk narrowed by enabling device registration
Languages
Command line
1 command for Cisco Duo Desktop, each with where it came from. This tool has no source analysis yet, so there is no option reference and no captured run beside them.
No command matches.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Cisco Duo Desktop, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Cisco Duo Desktop puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
duo.com, every changeCisco (Duo)'s home page and 40 more pages as they looked each month from September 2021 to October 2026: 52 renders, 6 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Coverage
Missing something? Tell us
What Cisco Duo Desktop connects to, runs on and detects, read from its release notes and docs. So far: 1 new integration.
1 change, tracked since Oct 14, 2026.
-
Oct 142026
new Duo SSO and SCIM lifecycle management integration with AWS IAM Account Access Manager (AAM)
With AWS IAM Identity Center
Cisco Duo's identity and access management platform closes both gaps at once: Duo SSO enforces risk-based access policies and strong, consistent MFA when users sign in to AWS, and Duo's SCIM-based lifecycle management keeps the groups behind those entitlements current automatically.
Identity & access 2
Nothing first seen in this window. That doesn't mean Cisco Duo Desktop shipped nothing, only that we found no record of it.
How we count
Read from 1 of 14 release notes and docs updates we hold for Cisco Duo Desktop. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Cisco Duo Desktop's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
14 entries
No entries match these filters.
- October 20261
- September 20268
- August 20262
- July 20263
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →