Duo lets you reduce risks by enforcing precise policies and controls. Enable your team to define and enforce rules on who can access what applications — under what conditions. Define access policies by user group and per application to increase security without compromising end-user experience.
Duo Beyond, Duo Access, and Duo MFA plans customers gain granular control with the Policy & Control feature.
Policies are centrally-managed and can be applied... - globally or shared between applications, so you don’t have to specify the same setting in multiple places. - to specific user groups accessing an application. This lets you set different rules depending on who is authenticating and their context.
Duo Free plan customers have limited access to Duo policies. Free plans may only control the New User Policy via a global or per-application policy. All other available application settings are configured at the individual application.
Create and manage your policies from the top-level Policies tab in the Duo Admin Panel.
Only admins with the Owner or Administrator roles can create or edit policies. Admins with the Application Manager role may assign existing policies to applications, but may not edit or create policies.
When creating policies that restrict access for users, keep in mind that users with bypass status are not subject to these restrictions, as they bypass Duo authentication entirely.
The Global Policy is built-in and cannot be deleted. It always applies to all applications, so you should edit this policy if there are settings you'd like to control for all users and all applications. A summary of the Global Policy settings is shown on the Policies page. Settings at the Duo defaults are greyed out.
Your Duo subscription level determines which policy options show up in the editor. For example, Duo MFA receives a subset of the policy settings available to Duo Access and Duo Beyond customers.
As you review the various policy settings in this document, note the Duo plans listed in the Available in information to determine if a setting applies to your subscription or not.
Role required: Owner or Administrator
To edit the Global Policy from the Policies page:
Click Edit Global Policy in the upper right of the Global Policy summary.
Once in the Global Policy editor, click the policy settings listed on the left side of the editor that you want to modify, then update the setting configuration on the right side of the editor.
Click Save Policy when your edits to the Global Policy are complete.
The Global Policy summary reflects your new policy settings (with your configured settings flagged as "Enabled").
If you'd like to restore the original Global Policy settings, open the Global Policy editor again and click the Revert to default link at the top of the "Edit Policy" window. Click Save Policy to apply the Global Policy defaults.
Changes to existing policy settings take immediate effect.
If certain applications require policy and controls that differ from the Global Policy, you can create a Custom Policy and assign it to those applications. Custom policies for an application can also be limited to specific groups. Custom Policies only need to specify the settings they wish to enforce.
Create custom policies for groups or applications from either the main Policies page or from the properties page of any application. Policies may be shared between multiple groups and applications.
When you view an application, the Global Policy settings are shown because these settings apply to all applications unless they are superseded by a custom application or group policy.
Settings configured and assigned by group policy can override settings assigned by an application policy, which in turn overrides settings in the Global policy. If an application policy or group policy setting supersedes a Global Policy setting, the superseded setting is crossed out in the Global Policy view shown when viewing an application. In the example below, the "HIPAA Policy" application policy settings (New User Policy, User Location, etc.) override those same settings in the Global Policy for that specific application.
Role required: Owner or Administrator
Admins with the Owner and Administrator role can create and assign a new custom policy right from an application's properties page. To do this:
Navigate to an application's properties page in the Duo Admin Panel.
Click the Apply a policy to all users link to assign the policy to all users of that application.
Click the Or, create a new Policy link instead of selecting a policy to apply from the drop-down list.
The policy editor launches with an empty policy.
Enter a descriptive Policy Name at the top of the left column, and then click each policy item's name to add it to your new custom policy. Each item you click is added to the policy customization area on the right, where you can adjust the settings. Click the X on the right to remove a setting from the customization area.
When you are done adding and configuring policy settings, click Create Policy to save the settings and return to the "Apply a Policy" prompt.
Click Apply Policy. The application page shows the new policy assignment.
Role required: Owner or Administrator
Admins with the Owner or Administrator role can create a new custom policy and assign it to one or more Duo groups right from an application's properties page. To do this:
Navigate to an application's properties page in the Duo Admin Panel.
Click the Apply a policy to groups of users link to assign the policy to only certain users of that application
Click the Or, create a new Policy link instead of selecting a policy to apply from the drop-down list.
The policy editor launches with an empty policy.
Enter a descriptive Policy Name at the top of the left column, and then click each policy item's name to add it to your new custom policy. Each item you click is added to the to the policy customization area on the right, where you can adjust the settings. Click the X on the right to remove a setting from the customization area.
When you are done adding and configuring policy settings, click Create Policy to save the settings and return to the "Apply a Policy" prompt, with your newly created policy selected. Start typing in a group's name in the Groups field and select the policy target group(s) from the suggested names.
Click Apply Policy. The application page shows the new group policy assignment.
Role required: Owner or Administrator
To create a custom policy from the main Policies page:
Click New Policy.
The policy editor starts with an empty policy.
Enter a descriptive Policy Name at the top of the left column, and then click each policy item's name to add it to your new custom policy. Each item you click is added to the to the policy customization area on the right, where you can adjust the settings. Click the X on the right to remove a setting from the customization area.
When you are done adding and configuring policy settings, click Create Policy.
The Policies page lists the newly created policy. From the policies page you can edit or delete the custom policy by clicking the appropriate action.
Role required: Owner, Administrator, or Application Manager
To assign an existing custom policy to an application:
Navigate to an application's properties page in the Duo Admin Panel.
Click the Apply a policy to all users link to assign the policy to all users of that application.
Select the policy to apply from the drop-down list.
Note that admins with the Application Manager role do not see the "Or, create a new Policy" link visible to Owner and Administrator roles.
Click Apply Policy. The application page shows the new policy assignment.
Role required: Owner, Administrator, or Application Manager
To assign an existing custom policy to a group:
Navigate to an application's properties page in the Duo Admin Panel.
Click the Apply a policy to groups of users link to assign the policy to a specific group of users who access that application.
Select the policy to apply from the drop-down list. Then start typing in a group's name in the Groups field and select the policy target group(s) from the suggested names.
Note that admins with the Application Manager role do not see the "Or, create a new Policy" link visible to Owner and Administrator roles.
Click Apply Policy. The application page shows the new group policy assignment. Clicking the name of the policy group target displays the properties and members of the group.
Modify an existing custom policy's settings by clicking the Edit link shown to the right of the custom policy name on the main Policies page in the Admin Panel, or from the Policy section of an individual Duo application's details page. Make your desired changes in the policy editor, and then click Save Policy.
Changes to existing policy settings take immediate effect.
The policy framework applies custom group policy settings in the order they are listed in an application's Policy properties. When group policy settings conflict, the first policy listed has the highest precedence.
You can reorder group custom policies on an application by clicking Move to Top in the actions to the right of the group policy's name. This will move that policy one spot up in the list of group policies.
In the example below, the effective policy setting is that a member of both the "CorpHQ_Users" and "ITAdmins" groups may authenticate from a device without a screen lock enabled. Reordering the policies so that the "Require Screen Lock" group policy is listed first enforces that "ITAdmin" group members always need screen lock enabled to authenticate to this application.
Clicking the Replace link next to any of an application's currently assigned custom policies brings up the Apply a Policy window. From this window you can pick a different custom policy to apply, or pick different groups to associate with a group policy.
The Applications page of the Duo Admin Panel lists all of your applications. The Application Policy and Group Policies columns display current policy assignments for each application.
Clicking any policy name shown on the Applications page takes you to the Policy section of the properties page for that application.
To remove a custom policy from an application, click Unassign near that policy's name in the Policy section of an application's properties page.
To delete a custom policy from Duo, navigate to the Policies page and click Delete to the right of that policy's name. Deleting the policy also removes it from any applications. The alert shows how many applications (if any) the policy currently affects.
Duo captures policy related events -- such as custom policy creation and edits to the Global Policy -- in the Administrator Actions log.
Available in: Duo Free, Duo MFA, Duo Access, and Duo Beyond
The new user policy controls authentication for unknown users, in other words, users not yet enrolled in Duo. In Duo, an enrolled user is someone who exists in the service and has at least one authentication device attached, which can be a phone, hardware token, etc. The new user policy can be one of the following:
To change the new user policy, click the radio button next to the desired setting.
Available in: Duo MFA, Duo Access, and Duo Beyond
Configure this policy to change how both existing Duo users and unenrolled/new users access a Duo-protected application or to change access to selected applications. This overrides less-restrictive authentication policy settings configured at the global, application, or group level. More restrictive policy settings, such as a user location policy denying access to a specific country, still apply.
Changing the authentication policy setting from the default prevents new users from completing inline self-enrollment while authenticating to applications. When set to "Bypass 2FA", users not enrolled in Duo bypass the frame entirely when accessing the application so there is no opportunity for self-enrollment. If authentication to the application is blocked with the "Deny Access" setting, new users cannot self-enroll in that scenario either.
End users who receive enrollment links via email (like those sent by the directory sync process) may complete the Duo enrollment process via the emailed link regardless of the authentication policy setting.
As you deploy Duo throughout your organization you may need to let designated users access a certain application without Duo authentication, while requiring that they complete Duo 2FA when accessing any other protected application.
Accomplish this by first creating a Duo group (manually or via Directory Sync) containing those users.
Next, view the application which you want those group members to bypass Duo authentication in the Admin Panel. Click on Apply a policy to groups of users to create a new policy with the authentication policy set to Bypass 2FA, and then attach that new policy to your bypass group.
When the users in that Duo group access that application, they'll pass through to the application after successful verification of primary credentials. All other users accessing that application are subject to any other access policy settings applied to that application or in the global policy.
You can use the same process with the authentication policy set to Deny access to block users from accessing a selected application while still permitting them access to other Duo applications.
If you apply the authentication policy to an application as an application policy (instead of a group policy), then the configured bypass or deny access setting applies to all users of that application. Again, this overrides any other access policy set at the global level, and access to other Duo applications is unchanged.
Configuring the authentication policy within Duo's global policy affects all Duo application and all users — whether the user is enrolled in Duo or not. If you set the authentication policy to deny in the global policy then no users can access any of your Duo-protected applications (unless another policy setting permits access). Conversely, if you set the authentication policy to allow access in the global policy, then all users can access any application without completing Duo two-factor authentication (unless another policy requires 2FA).
Available in: Duo Access and Duo Beyond
The user location looks up the geographical origin of a user's access device IP address, and can then enforce policy based on that location. You can deny all access from certain countries, or always require two-factor authentication for access requests from a country.
This policy setting overrides other access policies, like Authentication Policy Authorized Networks and Remembered Devices, when the setting applied here is more restrictive than the setting applied by those other policy options.
To change the user location policy, start typing in a country name to select it from the list, then change the drop-down to the desired setting for that country. The available settings are:
Available in: Duo Beyond
Duo's trusted endpoints feature determines whether an access device is managed by your organization or is an unmanaged BYOD or unknown device. When an application loads the Duo Prompt it checks for the presence of a Duo device certificate or verification information from your MDM software or Duo Mobile app on that endpoint. You can use this policy to gain information about the devices used to access your Duo-protected web applications, and optionally restrict access from unmanaged endpoints.
The primary endpoint policy options are:
It's possible to apply different trusted endpoint policies to mobile devices than to computers. If you'd like to enable this functionality then click on Advanced Options for Mobile Endpoints to expose these additional selections:
Enabling the trusted mobile endpoint option could potentially make your overall trusted endpoints deployment less secure. Learn more about the security implications of enabling mobile endpoint options in your trusted endpoints policy.
See our full Trusted Endpoints guide for more information and step-by-step deployment instructions.
Available in: Duo Access and Duo Beyond
The Duo Device Health application gives organizations more control over which laptop and desktop devices can access corporate applications based on the security posture of the device. The first time users log in to an application protected by the web-based Duo Prompt with the Device Health Application policy enabled, they are prompted to download and install the Duo Device Health application. Once the Device Health application is installed, Duo blocks access if the device is unhealthy based on the Duo policy definition and informs the user of the reason the authentication was denied.
The Device Health Application policy can be configured for either macOS endpoints, Windows endpoints, or both, and has three operating modes:
Don’t require users to have the app: When this option is selected, the policy is not in effect and has no impact on end user access. End users are not prompted to install the Duo Device Health application when accessing a Duo-protected application. Data will be collected from the Duo Device Health application if present and running on the machine.
Require users to have the app only: When this option is selected, but none of the "Block access" options are selected, the Device Health application must be installed and reporting information to Duo for access.
End users running devices that can install the app (Windows 10+ and macOS 10.13+) are prompted to download the app from the Duo prompt when attempting to access a Duo-protected application associated with the policy if they do not already have the app installed. Devices that are capable of running the app but do not have it installed and running will be blocked.
The app will collect health information from the device, but Duo will not block the user from getting access if it does not pass the specific firewall, encryption, and password health checks. This means that the device will be able to access the application even if the device would not pass each health check.
Devices that cannot run the app, including older versions of Windows, Linux, etc., will not be prompted to install the app and are effectively allowed to bypass the Device Health Application policy.
Require users to have the app and any blocking options: When this option is selected and one or more of the "Block access" options are selected, the Device Health application must be installed and reporting information to Duo, and the device must satisfy the specified health requirements for access.
End users running devices that can install the app (Windows 10 and macOS 10.13+) are prompted to download the app from the Duo prompt when attempting to access a Duo-protected application associated with the policy if they do not already have the application installed. Devices that are capable of running the app but do not have it installed and running will be blocked.
The app collects health information from the device, and Duo will allow or block access to the protected application based on the device health options selected.
Devices that cannot run the app, including older versions of Windows, Linux etc. will not be prompted to install the app and are effectively allowed to bypass the Device Health Application policy.
Note that the default “fail-open” Device Health Application policy allows you to enforce health checks for supported macOS and Windows devices, while not blocking users who need to access an application using a non-supported device. You can optionally use Duo's Operating Systems policy to restrict other device types from accessing the application.
Duo Beyond plan customers have additional antivirus and anti-malware agent check and policy options to verify that endpoints have a supported security solution in place before accessing an application.
See our full Device Health guide for more information and step-by-step deployment instructions.
If you configure operating system version policy settings for Windows and macOS, consider deploying the Device Health app to clients to enhance OS version detection for those systems, even if you don't use the Device Health policy options to verify security posture during authentication. Reliable detection and policy enforcement against Windows 11 requires the Duo Device Health application.
Available in: Duo MFA, Duo Access, and Duo Beyond
Duo's remembered devices feature is similar to the "remember my computer" or "keep me logged in" options users familiar to users from primary authentication to websites and applications. With the remembered devices feature enabled, users of the Duo traditional prompt and Duo Authentication for Windows Logon see a “Remember me” option, and users of Duo Universal Prompt see a "Trust this browser". When users select this option during Duo authentication, they will not be challenged for Duo authentication when they log in again from that device for a set period of time.
You can enable remembered devices separately for web applications or Duo Authentication for Windows Logon, or for both in a single policy with distinct session lengths.
The Remember devices for browser-based applications setting works with applications that show the Duo Prompt in a browser. When configuring it, enter the desired number of days or hours — up to 365 days — for the Users may choose to remember their device for setting and then choose one of these options:
This is especially helpful for users of Duo Single Sign-On and Duo Access Gateway. In this scenario, you would create a policy with remembered devices for all applications and then apply that same policy to each Duo-protected SAML application for which you don't want additional 2FA prompts. When a user logs into one of the protected SAML apps with that policy, like Google G Suite, and chooses to remember that device, the user isn't prompted for Duo access again when accessing other SAML apps via the Duo Access Gateway or Duo Single Sign-On with the same linked remembered devices policy.
In practice, we recommend configuring your remembered devices policy for web applications at the global policy level, and then creating application and group level policies without remembered devices to override an existing trusted login session for those sensitive or restricted-access web applications where you want your users to perform Duo authentication again.
The Remember devices for Windows Logon setting works with Duo Authentication for Windows Logon version 4.2.0 and later. When enabling remembered devices for local Windows logons, enter the desired number of days or hours — up to 365 days — for the Users may choose to remember their device for setting.
This policy setting only affects "Microsoft RDP" Duo applications. If you configure this setting in your global policy, or assign it to any application types other than Microsoft RDP, it has no effect on those other application types and users will not see the remembered device option during Duo authentication from those other applications. Additionally, remembered devices settings do not apply to remote access Windows logins over RDP; the "Remember me" option shown for local console logins won't be present at RDP login. If you want to bypass Duo authentication for RDP connections, consider applying an Authorized Networks policy to the application.
When a user logs into Windows at the local workstation or server console and checks the "Remember me" box during Duo authentication, it creates a trusted session for that user on that host with that IP address after successful Duo authentication. Duo won't prompt for authentication again when the user locks and unlocks the workstation, or for credentialed UAC elevation by that user, for the duration specified in the policy setting.
Duo Authentication for Windows Logon invalidates the local trusted session on that Windows system before it expires if the user logs out of Windows or reboots, if the user cancels a remembered authentication in process, if the user authenticates with offline access for Windows logon, or if the network location of the system changes from the network in use at session creation. Administrators may revoke use of trusted Duo sessions by disabling or unassigning a remembered devices policy for Windows Logon from a Microsoft RDP application, or by deleting the registry entry for the user session from the Windows client. Learn more about this in the Windows Logon FAQ.
Available in: Duo Access and Duo Beyond
The operating systems policy settings allow you to control which operating systems and versions are allowed to access your applications when protected by Duo's browser-based authentication prompt, while also encouraging users running older operating systems to update to the latest version.
These policy settings also can be used to restrict what mobile OS platforms and versions may be used with Duo Mobile to approve two-factor authentication requests or generate passcodes for authentication. When you block a given mobile operating system, then that restriction applies to all Duo applications, not just those that use Duo's browser prompt.
The default settings allow access, authentication, and enrollment from browsers on all Duo supported operating systems, mobile platforms, and versions with no warnings. You may block access from all versions of any of the OS platforms listed in the policy editor: Android, BlackBerry, Chrome OS, iOS, Linux, macOS, Windows, and Windows Phone. Duo offers more granular options for the Android, iOS, macOS, and Windows operating systems, like warning on or blocking access below a certain version, warning the user that they need to update to an approved version instead of blocking access outright, and setting a grace period for warning or blocking a user after a version becomes outdated.
Scroll down in the policy editor to see all OS options.
Enable the Encourage users to update option by picking your minimum allowable OS version from the drop-down selector. You can choose to select a specific version, or let Duo determine the most recent available up-to-date or end-of-life version. Duo defines the "latest" version as the most recently released available OS version or build, and defines "up-to-date" as the most recent patch release for a given OS version or build. "End-of-life" indicates that the software vendor no longer releases security updates for that version.
After choosing the OS version, select a grace period from the When a version becomes out of date or end of life, encourage to update choices. Setting this to "Immediately" means users see the warning as soon as their current version is lower than the version you selected. You can delay the Duo warning for up to 365 days. Look to the right of your selection to see a summary of your new policy setting.
Once configured, Duo shows a notification during authentication or enrollment to your users informing them that they should update when accessing your Duo-protected resource from a device running an operating system version older than your selection.
The user may disregard the warning and continue with authentication. For example, you may choose to encourage Windows users to update version "below 8.1" and to start warning them "Immediately". A user accessing your application from a Windows 8 PC sees a warning at the bottom of the Duo prompt. Clicking "Let's update it" provides the user with information on how to update the operating system. Users can proceed past the warning by clicking "Skip".
Restrict application access to only the versions you've allowed by making a selection in the Block versions option for an OS, along with a corresponding grace period for blocking. Blocking any operating system version(s) prevents users from completing authentication or new user enrollment from that disallowed OS (or OS version).
To continue the previous example, choosing to block users with Windows versions "below 8.1" disallows authentication or enrollment for any user trying to access your application from a Windows 8 computer. Users can't proceed past the out-of-date software notification.
Uncheck the "Allow" option for an OS to prevent access entirely, i.e. if you uncheck Allow Windows Devices in the policy editor, then users accessing your application from any version of Windows are blocked.
The Android and iOS mobile platforms can also be restricted to a minimum allowed version or blocked entirely. Blocking any version of a mobile OS platform, e.g. iOS or Android, not only restricts access to resources from browsers on those OS platforms or versions, but also prevents use of Duo Mobile to approve Duo Push requests or generate usable passcodes on devices running the restricted OS.
If you were to block iOS versions "below 9.0" then any users with Apple devices running iOS 8.0 or lower can no longer use access Duo-protected applications from mobile Safari, nor can they use Duo Push or app generated passcodes to authenticate to any Duo-protected application, whether it's accessed via browser or not. If a user has other additional activated devices running a different mobile platform, the functionality of the other devices is not affected.
When a mobile device operating system or version is restricted users see a message in the browser-based Duo Prompt.
Duo Mobile also notifies the user that the mobile platform or version is not allowed when attempting to approve the Duo Push request.
Passcodes from a hardware token or received via SMS are allowed, as are phone call authentications, but entering a passcode generated by Duo Mobile on any device running the restricted platform results in an error stating that platform is not permitted.
As an example scenario, if you disallow Android devices then your iOS users continue to receive and approve Duo Push requests, and can also authenticate with SMS passcodes, application passcodes, hardware tokens, or over the phone. Your Android users can only use SMS passcodes to authenticate, approve a login via phone call, or use a hardware token passcode. If you wanted to completely prevent any use of Android phones to approve authentications, you'd also need to disable the "Phone callback" and "SMS passcodes" options in the Authentication Methods policy setting. Keep in mind that disabling phone and SMS authentication affects authentication for all users, no matter what mobile OS they use.
These operating system sections and tables detail the state of our version data for the four major OS platforms as of June 9th, 2021. This data maps to the operating system policy options as follows:
The current version for an OS platform whose status in the tables below is "Current" satisfies the If less than the latest policy option. All other versions are considered out of date.
The current version for an OS platform whose status in the tables below is "Current" or "Supported" satisfies the If not up to date policy option for macOS and Android, and all other versions are considered out of date.
All versions for an OS platform whose status in the tables below is "End of Life" (EOL) fall in scope for the If end of life policy option. Note that out-of-date versions for "Current" or "Supported" status products pass this policy as they aren't considered end of life.
| Release Name | Base Version | Current Version | Status | Date Marked EOL |
|---|---|---|---|---|
| Big Sur | 11 | 11.6 | Current | n/a |
| Catalina | 10.15 | 10.15.7 | Supported | n/a |
| Mojave | 10.14 | 10.14.6 | Supported | n/a |
| High Sierra | 10.13 | 10.13.6 | End of Life | 2020-12-14 |
| Older Mac Releases | < 10.13 | n/a | End of Life | n/a |
As of macOS 11, up-to-date versions of major browsers (Safari, Chrome, Firefox, and Edge) have frozen the OS version reported via the browser user agent string as 10.15.6, 10.15.7, or 10.16, impacting the ability to detect whether macOS 11 is truly up to date when relying only on information reported to Duo by the browser.
The Duo Device Health app detects and reports the actual macOS version, enabling reliable OS version verification during Duo authentication. Duo recommends using the Device Health app on macOS 11 or newer clients to enable accurate checking and reporting, especially if you choose to apply a Duo operating systems policy with the "If less than the latest" option selected, or pick a static version of 11.0 or greater.
Learn more about how the Device Health app enables granular operating system policy for macOS in the Device Health documentation.
| Build Name | Base Version | Current Version | Status | Date Marked EOL |
|---|---|---|---|---|
| Windows 10 21H1 | 10.0.19043 | 10.0.19043.1237 | Current | n/a |
| Windows 10 20H2 | 10.0.19042 | 10.0.19042.1237 | Current | n/a |
| Windows 10 2004 | 10.0.19041 | 10.0.19041.1237 | Current | n/a |
| Windows 10 1909 | 10.0.18363 | 10.0.18363.1621 | End of Life | 2021-06-08 |
| Older Windows 10 Builds | < 10.0.18363 | n/a | End of Life | n/a |
| Windows 8.1 | 6.3.9200 | 6.3.9600 | Current | n/a |
| Windows 8 | 6.2 | n/a | End of Life | 2016-01-12 |
| Windows 7 | 6.1 | n/a | End of Life | 2020-02-11 |
Duo's end-of-life determination for Windows 10 builds relies on the date that Microsoft marks that build as end of life for Windows 10 Home and Professional editions, even when Windows 10 Enterprise and Education editions have not yet been marked end of life my Microsoft.
For Windows operating systems before Windows 10, the Duo end-of-life determination matches Microsoft's stated "Extended End Date" for that version.
Refer to the Lifecycle FAQ for Windows for more details.
A browser user agent provides a limited amount of information about the Windows 10 version. The Duo Device Health application is able to retrieve the Windows 10 build version and the security patch version. This allows you to make policy decisions on specific Windows 10 versions to keep users up to date.
Major browsers (Chrome, Firefox, and Edge) will not accurately report the OS version in the browser user agent string in the upcoming Windows 11 release, so the detection of and policy enforcement against Windows 11 will require the Duo Device Health app.
Learn more about how the Device Health app enables granular operating system policy for Windows in the Device Health documentation.
| Release Name | Base Version | Current Version | Status | Date Marked EOL |
|---|---|---|---|---|
| Android 11 | 11 | 11.0.0 | Current | n/a |
| Android 10 | 10 | 10.0.0 | Supported | n/a |
| Pie | 9 | 9.0.0 | Supported | n/a |
| Oreo | 8 | 8.1.0 | Supported | n/a |
| Nougat | 7 | 7.1.2 | End of Life | 2020-09-28 |
| < 7 | n/a | n/a | End of Life | n/a |
Duo's end-of-life determination for Android is that versions that still receive security patches are considered supported. Versions no longer receiving security patches are considered end of life.
| Release Name | Base Version | Current Version | Status | Date Marked EOL |
|---|---|---|---|---|
| iOS 15 | 15 | 15.0 | Current | n/a |
| iOS 14 | 14 | 14.8 | Supported | n/a |
| iOS 13 | 13 | 13.7 | End of Life | 2020-09-25 |
| Older iOS Releases | < 12 | n/a | End of Life | n/a |
Duo bases the end-of-life determination for iOS on Apple's historical update patterns. Historically, only the most recent iOS version has been considered supported, but this will likely change with Apple announcing support for iOS 14 and iOS 15 with security patches.
Available in: Duo Access and Duo Beyond
Enable this feature to inform your users when their web browser is out of date and optionally block access to your Duo-protected resources from clients with older browser versions or an entire browser family. This policy supports Chrome, Chrome Mobile, Edge, Firefox, Internet Explorer, Mobile Safari, Safari, and other browsers (which includes Firefox Mobile). The default setting is to allow all versions of all browsers without any notifications.
When the "Warn users if their browser is out of date" option is enabled, users authenticating via the Duo Prompt see a notification when the web browser version used is older than the current release version. Instructions for updating or a link to the browser vendor's website are provided if applicable. If you have only opted to warn users, they may skip the software update and complete authentication. The out of date notification continues appearing during authentication attempts until the end user updates to the current version.
You may also choose to block user access when web browsers are out of date and specify a grace period during which users may continue to authenticate with older versions (0 days to one year after the current release).
If you set your policy to block access from out of date browsers, users can skip past the software update warning up until the end of the grace period you specified in the policy. After that, users may not continue to Duo new user enrollment and authentication. Only updating the browser to a current version permits a user to complete Duo authentication or enrollment.
Restrict user access from certain web browsers completely by selecting the browser under "Always block".
See Software Update in the user guide for more information.
Available in: Duo Access and Duo Beyond
Enable this feature to inform your users when selected plugins are out of date or block access to your Duo-protected resources from clients with outdated plugins (or block a plugin entirely). The default setting is to allow all versions of Flash and Java plugins without any notifications.
When the “Warn users" option is enabled, users authenticating via the Duo Prompt see a notification when the selected plugins are older than the current release version. If you have only selected to notify users of the outdated software, they may skip the software update and complete authentication. The software update notification continues appearing during authentication attempts until the end user updates the affected plugin.
You may also choose to block user access when plugins are out of date and specify a grace period during which users may continue to authenticate with older versions (0 days to one year after the current release).
If you set your policy to block access from out of date plugins, users can skip past the software update warning up until the end of the grace period you specified in the policy. After that, users may not continue to Duo new user enrollment and authentication. Only updating the affected plugins permits a user to complete Duo authentication or enrollment.
Restrict user access with certain plugins completely by selecting "Block all versions".
Configure software notifications for either or all of the following plugins:
Flash - Checks whether or not the browser uses the Flash plugin. Adobe ended support for Flash on December 31, 2020, and began blocking Flash content from running in Flash Player on January 12, 2021. With Flash at its end-of-life (EOL), version updates are no longer possible. Therefore, the Duo policy options no longer check for the latest version, and only offer the options to allow or block all versions of Flash.
Customers who configured a Flash plugin policy that checks for out-of-date versions prior to the Flash EOL still see those settings when viewing or editing those existing policies, but should be aware that the end of update availability means that all versions are considered out of date.
Duo recommends that all customers set the Flash plugin policy to Block all versions.
Java - Checks the version of the Java plugin used by the current browser and notifies the user if it is out of date. A link is provided to the Oracle Java download site.
See Software Update in the user guide for more information.
Available in: Duo MFA, Duo Access, and Duo Beyond
Define global or application 2FA policies for different networks with Duo's authorized networks policy. MFA customers can minimize Duo prompts for specific networks, while Access and Beyond customers have additional options to require Duo authentication or block access entirely on a per network basis.
The authorized policy options are:
Allow access without 2FA from these networks - Users accessing Duo-protected resources from these networks skip Duo secondary authentication. Specify a block of IP addresses, IP ranges, or CIDRs as a comma-separated list.
By default, Duo prompts users to enroll when logging in from an authorized network when the new user policy is set to require enrollment. To prevent unenrolled users from receiving the Duo enrollment prompt when connecting from an authorized network, uncheck the Require enrollment from these networks setting.
Enabling the deny access option blocks access from Duo applications that don't report client IP! This prevents connections for any Duo application that shows the client IP as 0.0.0.0. Before configuring the setting please review your authentication logs in the Admin Panel to verify your Duo-protected applications report the client IP.
If there is any overlap between the network segments or IP addresses defined in the "allow access" and "require 2FA" options, then the more restrictive policy setting applies and access requires Duo authentication.
The Duo MFA plan authorized networks policy only permits specifying a network to bypass Duo MFA, and does not include the require or deny options.
Available in: Duo Access and Duo Beyond
Duo can help you monitor and optionally prevent authentication attempts originated from known anonymous IP addresses, such as those provided by TOR and I2P, HTTP/HTTPS proxies, or anonymous VPNs.
Available in: Duo MFA, Duo Access, and Duo Beyond
Duo offers a variety of ways that users can receive their second authentication factor: one-tap authentication with Duo Push, a passcode sent via SMS, an automated voice call, and so on (see our detailed explanation of all authentication methods).
If you choose to enable phone calls as an authentication method, consider applying some additional policy controls (such as restricting User Location to your expected countries) or reducing your max credits per action telephony setting to only the credit amount needed for phone calls to your users' expected locations to avoid telephony misuse, especially if you've enabled the self-service portal for any of your applications.
WebAuthn security keys can be used with the browser-based Duo Prompt when accessing applications with Chrome 70 and later, Edge 79 and later, or Firefox 60 and later on macOS and Windows, and Safari 13 and later on macOS. WebAuthn Touch ID support is available only in Chrome 70 or later on a Touch ID compatible MacBook.
To restrict authentication methods, just deselect the methods you don't want used.
For example, you can uncheck the "Phone callback" authentication method. Phone call no longer appears as an option in Duo Prompt.
The default setting allows all of Duo's authentication methods. If all methods are deselected, then only bypass codes may be used to authenticate.
Note: Even if Duo Push is disabled, users will still be able to use Duo Mobile to generate a one-time passcode (much as they might with a hardware token). You can prevent users from using the app to generate one-time passcodes by unchecking the Duo Mobile passcodes authentication method.
If you permit use of U2F and WebAuthn authentication methods, Duo recommends configuring allowed hostnames for your protected applications before onboarding your end-users.
Available in: Duo Access and Duo Beyond
The Duo Mobile smartphone app is an essential part of most organizations' two-factor deployment. We may need to issue app updates to address security vulnerabilities should any be discovered. The Require up-to-date security patches for Duo Mobile policy setting allows Android and iOS authentication from devices running the minimum secure Duo Mobile version (currently version 3.8.0 for both iOS and Android) or later while preventing authentication from Duo Mobile versions prior to the minimum secure version. Enable this setting to ensure that users can't authenticate from older Duo Mobile versions with security issues corrected by a later Duo Mobile version.
The default setting allows authentication from Android and iOS devices running any version of Duo Mobile.
Available in: Duo Access and Duo Beyond
It is possible to gain privileged access to the operating system of a mobile device. This is known as "rooting" on Android, and "jailbreaking" on iOS. Tampered, rooted, and jailbroken devices may be considered a security risk because they are more vulnerable to exploit by malware and malicious apps.
Duo can verify whether a device is rooted or jailbroken and prevent authentication from those devices. Duo performs jailbreak detection on iOS and, in addition to checking for rooted access on Android, also utilizes Google's SafetyNet device attestation to identify tampered-with Android devices.
You can prevent Duo authentication approvals from tampered-with or rooted Android and jailbroken iOS devices by enabling the Don't allow authentication from tampered devices policy setting. This setting has no effect on other mobile platforms.
The default setting allows authentications from all iOS and Android devices.
Available in: Duo Access and Duo Beyond
Enabling screen lock with passcode on iOS or with PIN on Android secures devices by requiring input of a numeric code when turning on your device or unlocking the screen. If the screen is locked when a Duo Mobile push authentication request is received, then the screen must be unlocked before approving the authentication request.
Require your users to set a PIN or passcode on their devices by enabling the Don't allow authentication from devices without a screen lock option in the "Screen Lock" policy. With this option enabled, users must have screen lock enabled on their devices to approve Duo Push authentication requests or log in with a passcode generated by the Duo Mobile app. Users may still approve phone call login requests and use SMS passcodes texted to a device without screen lock. If you wanted to completely prevent authentications from phones without screen lock configured, you'd also need to disable the "Phone callback" and "SMS passcodes" options in the Authentication Methods policy setting.
This setting applies to all supported Android versions (2.2 and up). For iOS devices, this setting is only enforced on version 8 and higher. Devices running iOS 7 and lower can still authenticate without enabling screen lock. To ensure that Apple devices used to authenticate comply with the screen lock requirement, you may change the Operating Systems policy for iOS to "Block users if their version is below 8.0".
The default setting does not require screen lock enabled to approve a Duo authentication request received via push or use a Duo Mobile generated passcode.
Available in: Duo Access and Duo Beyond
Disk encryption protects device data from unauthorized access. Booting an encrypted device requires entering a passcode or PIN at device boot. Apple devices automatically encrypt the filesystem, but on Android devices encryption is enabled by the end user separately after enabling screen lock.
Prevent Duo authentication from Android devices without disk encryption by enabling the Don't allow authentication from devices without full-disk encryption option in the "Full-Disk Encryption" settings. Note that a PIN is required at startup in order for a device's status to show as encrypted.
The default setting does not require full-disk encryption to approve a Duo authentication request from an Android device. This setting has no effect on iOS.
Available in: Duo Access and Duo Beyond
Biometric identity verification, like Apple's Touch ID and Face ID or Android Fingerprint, makes two-factor authentication even more secure.
In the policy editor, select the Require additional biometric verification option to require biometric approval for Duo Push from supported devices. Use of Duo Mobile generated or SMS passcodes remains unaffected, as well as authentication via phone call.
Fingerprint and Touch ID authentication requires Duo Mobile app versions 3.7 or above for iOS and version 3.10 or above for Android and minimum OS versions iOS 8 or Android 5.0 Lollipop. Face ID requires iOS 11 and Duo Mobile 3.19. Devices running earlier versions of Duo Mobile, iOS, and Android can not authenticate without biometric verification when you enable this policy setting.
Requiring biometric verification changes the Duo Push workflow. Users may no longer approve an authentication request from the app notification. Tapping the Duo notification opens the Duo Mobile app. After you tap "Approve" on the authentication request, scan your enrolled finger at the Touch ID or Android PIN prompt or perform Face ID verification to confirm the authentication approval. If you are unable to authenticate with a biometric factor you can fall back to your device's passcode.
The default setting does not require any biometric verification to approve a Duo Push authentication request from any device. All Duo Mobile, Android, and iOS versions may authenticate (subject to any other version restriction policy settings you may configure).
Please refer to the Duo Policy Guide for supplemental information about constructing effective custom policies and assigning them to your Duo applications and users.
Need some help? Try searching our Knowledge Base articles or Community discussions. For further assistance, contact Support.
All Duo customers have access to Level Up, our online learning platform offering courses on a variety of Duo administration topics. To access Level Up content, sign in with the same email address you use to sign in to the Duo Admin Panel.