- Cisco Duo
- New Features
- Now Generally Available: Redesigned Admin Panel Navigation
- Enhancements
- New and Updated Applications
- Five new named applications with Duo Single Sign-On (SSO)
- Duo Network Gateway version 3.2.2 released
- DuoConnect public preview 2.0.5 for Windows released
- DuoConnect public preview 2.0.5 for macOS released
- Bug Fixes
- Identity Security
- New Features
- New Report: Accounts Sharing Access Devices:
- Enhancements
Hello everyone! Here are the release notes for our most recent updates to Duo.
Public release notes are published on the Customer Community every other Friday, the day after the D-release is completely rolled out to commercial deployments. You can subscribe to notifications for new release notes by following the process described here. If you have any questions about these changes, please comment below.
Check out the Guide to Duo End-of-Life and End-of-Support Plans. This guide provides an up-to-date list of current and past end-of-life plans for Duo products.
Cisco Duo
New Features
Now Generally Available: Redesigned Admin Panel Navigation
- The Admin Panel redesign, first introduced in November 2024, is now generally available. The navigation bar can now be collapsed and expanded. The navigation bar and header will now be sticky on the screen when the page scrolls.
- Administrators and Groups are now under Users.
- Device Insight, Trusted Endpoints, Endpoints, and 2FA Devices are now under one Devices section.
- SSO configuration is now under Applications.
Enhancements
During Duo Mobile enrollment, if we detect the user is in China, the prompt will no longer reference the Google Play Store and will instead provide a link to instructions on how to install Duo Mobile without an app store for Android devices.
New and Updated Applications
Five new named applications with Duo Single Sign-On (SSO)
- There are now named SAML applications to protect Cisco Unified Communications Manager, Nifty, Tempo Portfolio Manager, and Zoho Books and a named OIDC application to protect Secured Signing with Duo Single Sign-On (SSO), our cloud identity provider.
Duo Network Gateway version 3.2.2 released
- Fixes a critical bug with Let’s Encrypt certificate generation introduced in version 3.2.1.
- Fixes a bug which caused ssl-cipher-config to not be generated.
- Updated dependencies: certbot to 2.0.0 and acme to 2.0.0.
DuoConnect public preview 2.0.5 for Windows released
- Hotfix to address Windows 11 24H2 bug that breaks DuoConnect’s Application Relay feature.
- Security updates.
DuoConnect public preview 2.0.5 for macOS released
- Security updates.
Bug Fixes
- Fixed an issue preventing push from being activated on the Admin Profile page if SMS and Voice are disabled as Admin Login Factors and push is skipped during initial administrator provisioning.
Identity Security
New Features
New Report: Accounts Sharing Access Devices:
- Navigate to the Reports page to download the csv report which contains information about users in your organization who utilized the same access device within the last 30 days, which could be an indicator of credential sharing and should be cleaned up.
Enhancements
- Identity Intelligence is now collecting Duo Desktop Authenticator data so it is now included as a factor on the Dashboard MFA widget, as a factor on a given user’s factor table, and within the activity logs when the Desktop Authenticator has been enrolled, used, etc.
- Duo bypass codes that have been disabled are now displayed in the Factors table on the Overview page of the User 360 so that if a bypass code is issued and only enabled for use for a short period of time it can still be found during an investigation.
- The threshold for Lifecycle Event Age, which defines how long events remain visible on an account, can now be customized from the default setting of 7 days. Go to the Tenant Settings menu item and select Lifecycle Events to modify the number of days as needed.
- MFA Flood check is now compatible with Entra ID. This check, which was previously only compatible with Duo and Okta, detects when a user receives a sequence of failed push notifications, followed by a successful push acceptance, over a designated window of time.
- External collaborators coming from Github now display the Github Organization name within the user’s Github source card on the Overview tab of the User 360 so that you can more easily identify what the user has access to and where to remove the account.