Decentralization of device management and the rise of BYOD (Bring Your Own Device) can leave administrators wondering how users are accessing resources. The Mobile Devices and Laptops & Desktops dashboards show which platforms, devices, and browsers connect to your Duo protected applications and services.
Track the mobile 2FA devices and computer endpoints used through your organization to access Duo protected applications and approve two-factor authentication requests from the top-level Device Insight tab in the Duo Admin Panel.
In Duo's Admin Panel, the "Endpoints" and "Laptops & Desktops" pages list the systems used to access resources, while the "2FA Devices" and "Mobile Devices" pages show the phones and other authenticators used to approve 2FA requests from Duo.
Duo tracks versions of operating systems, browsers, and plugins like Flash and Java on the devices accessing your protected resources and provides a summary view on the Device Insight overview page. You can easily see how many access devices are out of date throughout your organization.
We've included visualizations of access devices with out of date browsers, plugins, and operating systems over time. Move your cursor over any time period in the graph to see the number of out of date devices as of that day. You can change the graph's scale from 7 to 30 days, and also change the view from all software vendors for that category to a specific one e.g. show only the number of devices with outdated versions of Internet Explorer.
Clicking the Edit your policy link under any of the outdated device counts takes you to the Global Policy editor, where you can choose to warn users about outdated software and prevent access to your applications from devices with older software. See our Policy documentation for more information about implementing device access policies.
The Mobile Devices page breaks out smartphone and tablet 2FA devices by operating system and version and shows the status of various security features on iOS and Android platforms.
The Device Breakdown summarizes the various mobile device types your users have enrolled in Duo, while the rest of the page displays more information about Apple and Android devices in two columns: iOS and Android.
The first table in each column shows the Android and iOS device operating system versions in use across your organization.
Clicking the View Devices link in any row of the table takes you to a filtered list of devices running that OS version.
The iOS and Android Tampered Devices counts show how many devices have elevated privileges enabled on the operating system or fail other safety checks. Tampered-with devices may be considered a security risk because they are more vulnerable to exploit by malware and malicious apps. You can use the Tampered Devices Policy Setting to restrict authentication from tampered-with devices.
Clicking any of the device counts takes you to a filtered list of tampered devices.
Enabling a lock screen that requires a PIN or password elevates the security of a mobile device. The Screen Lock items for iOS and Android show counts of devices with and without lock screen protection. Change the Screen Lock Policy Setting to require lock protection from devices used for Duo authentication.
Clicking any of the device counts takes you to a filtered list of devices with or without screen lock enabled.
Apple's devices with Touch ID and Face ID and newer Android devices with fingerprint scanners can be used to unlock the device. See how many devices in your organization have Touch ID, Face ID, or fingerprint authentication enabled in the Mobile Device Biometrics count. You can require biometric verification for Duo Mobile login approvals with the Mobile Device Biometrics Setting.
Clicking any of the device counts takes you to a filtered list of devices with and without biometric verification enabled.
Android devices typically do not ship with full-disk encryption. A password or PIN must be entered at boot to decrypt and access the data when a device’s disk is encrypted. The Disk Encryption count shows how many Android devices have full-disk encryption. Restrict Duo authentication to only devices with encryption enabled with the Disk Encryption Policy Setting.
Clicking any of the device counts takes you to a filtered list of Android devices with or without encryption. In order for a device's status to show as encrypted the device must require PIN entry at startup.
Disk encryption status does not apply to iOS devices. Apple phones and tablets ship with an encrypted file-system.
The 2FA Devices > Phones list in the Admin Panel now flags less optimal security properties ("Screen unlocked", "Tampered", etc.) in addition to displaying summary information like platform, Duo Mobile app version, and attached user or users. Click any of the column headers to sort on that property.
You can filter the Phones list by Android or iOS operating system version, as well as by security property status. For example, checking the boxes next to "iOS", "8", and "Locked" on the left side of the 2FA Devices > Phones page then displays all Apple phones and tablets running iOS version 8.x with Screen Lock enabled.
Viewing the details of a phone or tablet device shows the status of various security properties e.g. Screen Lock, TouchID, etc.
When a device is secure, the various details are green. A setting shown in red indicates a less secure status.
Laptops & Desktops shows which operating systems and browsers were used to authenticate to your organization's web-based Duo applications over the last seven days. Duo also checks to see if Flash and Java browser plugins are present.
Clicking the View Devices link in any row of the Operating Systems, Browsers, or Plugins tables takes you to the Endpoints page, with the view filtered to show access by the selected OS, browser, or plugin.
The Operating Systems chart summarizes access by operating system. Totals for the most popular operating systems (Mac OS X and Windows) are shown, while less commonly used endpoint operating systems (like Chrome OS and Linux) roll up to the "Other" category.
The tables under the chart detail Mac OS X and Windows platforms recently used when accessing Duo protected resources, also showing device counts for each OS version.
The Browsers chart breaks down recent access by browser vendor.
The tables below present statistics for Chrome, Safari, Internet Explorer (IE), Edge, and Firefox versions recently used for Duo authentication. Duo shows you how many of your users initiated access from devices using an out of date version of that browser, and also informs you just how far behind the current browser version those vulnerable endpoints are. Here's example data for the Chrome browser:
Click the View Devices link on any of the listed plugin versions to go to a filtered view of the Endpoints page showing which endpoints users authenticated from using that browser version.
Help your users navigate the web securely by keeping third-party browser add-ons up to date. Duo captures Java and Flash plugin information whenever your users log in to a Duo protected browser-based application using our inline enrollment or activation prompts.
The Java chart and table shows how many of your users have Oracle's Java plugin enabled in the browsers they use to authenticate to Duo, and which versions in use are out of date and vulnerable. The Flash chart and table shows the same information about Adobe's Flash plugin.
Click the View Devices link on any of the listed plugin versions to go to a filtered view of the Endpoints page showing which users authenticated from an endpoint with that specific plugin enabled.
Use the Operating Systems, Browsers, and Plugins policy settings to restrict access and authentication from certain operating systems and versions, inform your users when their web browser or select plugins are out of date, and optionally block access to applications protected with Duo from devices with outdated software. Users authenticating via the Duo Prompt see a notification when the selected software is older than the current release version. If you choose to block access to users with outdated software or to selected operating systems, users are unable to complete authentication to access your applications.
Self-remediation notifications and access controls are available for the following:
See the Policy & Control documentation for more information.