Introduction
Cisco Duo policies allow administrators to define granular access controls across applications, user groups, and endpoint devices. Configuring these settings properly is crucial for protecting organizational data from unauthorized access, neutralizing remote threats, and ensuring that only secure devices can authenticate, all while balancing user friction.
Prerequisite
- Access to the Cisco Duo Admin Panel.
- An administrator account with the Owner, Administrator, or Application Manager role.
- Basic understanding of your organization’s security and compliance requirements.
Step-by-step Guide
Step 1: Access the Policy Builder
-
- Log in to the Duo Admin Panel.
- In the left sidebar, navigate to Policies > Policies.
- Click Add Policy.
Step 2: Configure Policy Features
Review and configure the following settings based on your security needs.
Name & details - Defines the internal name and description of the policy within the Duo Admin Panel.
- Policy name: Must be configured to save the policy. It applies a clear label (e.g., “Strict VPN Access”) to help administrators identify the policy’s purpose during audits and management.
New user policy - Controls application access for users who exist in your directory but have not yet enrolled a 2FA device.
- Require enrollment: The default secure posture. Forces unenrolled users to go through the setup process and register a 2FA device upon their next login attempt.
- Allow access without MFA: Permits unenrolled users to log in using only their primary credentials (username/password) until they are formally enrolled.
- Block access: Completely denies login attempts for users without a registered 2FA device. Administrators must manually enroll devices for these users.
Authentication policy - Sets the baseline two-factor authentication requirement for the protected application.
- Enforce MFA: The standard setting. Requires users to complete two-factor authentication for every login attempt.
- Skip MFA: Bypasses the 2FA requirement entirely, effectively turning the application into single-factor authentication.
- Block access: Denies all authentication attempts for all users targeted by this policy, overriding all other settings.
User location - Filters authentication attempts based on the geographic location (country or region) of the user's IP address.
- Rules (Select country or countries): Allows you to apply specific behaviors to selected geographic regions.
- Require MFA or passwordless authentication, even if it would normally be skipped: Overrides bypass rules (like trusted networks) to strictly enforce 2FA for logins originating from the selected countries.
- Skip MFA and allow access with only a password: Bypasses 2FA for users logging in from the selected countries.
- Allow access from selected countries and unknown locations: Standard behavior. Permits authentication attempts from the selected countries, applying standard MFA rules.
- Block access: Denies any login attempt originating from the specified countries.
- Rules (All other countries): Defines the default behavior for any country not explicitly selected in the rule set.
- Advanced settings
- Only check access device IP: Ensures Duo only evaluates the client’s direct public IP address, ignoring X-Forwarded-For headers that might be appended by proxies or load balancers.
Trusted endpoints - Restricts application access to known, corporate-managed devices by validating management certificates or integrating with MDM tools.
- Enforce Trusted Endpoints
- Block endpoints that are not trusted: Denies access to any device that cannot prove it is managed by the organization.
- Block endpoints using Cisco Secure Endpoint: Integrates with Cisco’s endpoint security, denies access if the endpoint is flagged as compromised or infected.
- Allow endpoints from these IP addresses: Creates an exception list where devices are granted access regardless of their trust status if they connect from specified safe IPs.
- Allow all endpoints: Disables the trusted endpoint requirement, permitting access from both managed and unmanaged (personal) devices.
- Do not check endpoints for trustworthiness: Skips the trust validation process entirely to speed up authentication when endpoint trust is not a concern.
- Advanced options
- Treat mobile endpoints differently: Allows you to separate policies for laptops/desktops and mobile devices.
- Block mobile endpoints that are not trusted: Strictly enforces MDM enrollment for iOS/Android devices while allowing unmanaged laptops.
- Allow all mobile endpoints: Exempts smartphones and tablets from the trusted endpoint check.
Duo Desktop & device health - Validates the security posture of laptops and desktops (e.g., active firewall, antivirus, password protection, and OS updates) before granting access.
- Duo Desktop (Windows / macOS / Linux)
- Require Duo Desktop
- Don’t require Duo Desktop: Makes the Duo Desktop optional.
- Require Duo Desktop: Forces users to install and run the Duo Desktop application to authenticate.
- Device registration
- Require devices to be registered using Duo Desktop: Binds the physical device to the user in the Duo system.
- Block devices presenting currently registered device identifiers: Prevents attackers from spoofing or cloning a legitimate device’s hardware ID to bypass trust checks.
- Device health (Windows / macOS / Linux / ChromeOS)
- Required device health checks: Activates posture checks for the respective operating system.
- Firewall enabled: Validates that the OS-level firewall (e.g., Windows Defender Firewall) is active.
- BitLocker / FileVault / Disk Encryption: Validates that full-disk encryption is active to protect local data.
- Exclude virtual machines: Bypasses the encryption check for VMs, as they are often encrypted at the host/hypervisor level rather than the guest OS level.
- System password set: Ensures the device requires a local user password or PIN to log in.
Remembered devices - Allows users to check a Remember me box during login to bypass subsequent 2FA prompts on that specific device and browser combination.
- Browser-based
- Remember devices for browser-based applications with risk-based protection: Dynamically evaluates risk (like location changes) before deciding if the “remembered” session is still valid.
- Always remember devices from these networks: Automatically trusts the device session without prompting the user if they are connecting from a defined corporate IP range.
- Remember devices for browser-based applications: Standard toggle to enable the “Remember me” checkbox for web logins.
- Don’t remember devices for browser-based applications: Disables the feature, forcing an MFA prompt on every single login attempt.
- Remember devices for browsers for up to: Defines the expiration period (in hours/days) for the trusted session cookie.
- Windows Logon
- Remember devices for Windows Logon: Enables a trusted session for local Windows desktop or RDP logins.
- Don’t remember devices for Windows Logon: Forces 2FA on every local or RDP Windows authentication.
Operating systems - Controls access based on the user's OS platform (Windows, macOS, iOS, Android) and version.
- Allow Android / Chrome OS / iOS / macOS / Windows Devices
- Warn users to update version: Allows the user to authenticate but displays a prominent warning that their OS is outdated and will be blocked soon.
- Block version: Immediately denies access if the user’s operating system is below the specified version number.
- Schedule: Allows you to set a grace period (e.g., “enforce in 7 days”) giving users time to patch before the block or warning takes effect.
- Summary: A read-only view displaying the active rules configured for that specific OS.
- Other Devices
- Allow Blackberry / Linux / Windows Phone / all other OS devices: Checkboxes to explicitly permit or deny logins from legacy, niche, or unidentified operating systems.
- Advanced settings
- Only check access device operating systems: Ensures Duo evaluates the client’s actual OS, ignoring user-agent strings modified by intermediate proxies.
Browsers - Restricts access based on the web browser type and version.
- Block browsers (Chrome / Chrome Mobile / Edge / Edge Chromium Mobile / Firefox / Firefox Mobile / Internet Explorer / Safari / Mobile Safari / Other Browsers): Explicitly denies access if a user attempts to log in using the selected browser types, useful for deprecating unsupported browsers.
- Out-of-date warning
- Warn if out of date by more than: Displays an alert if the browser is older than the current stable release by a specified time or version gap.
- Block if out of date by more than: Outright denies access if the browser is too outdated, forcing the user to upgrade to patch vulnerabilities.
- Override option
- Allow all browsers: Disables browser checking entirely, allowing access from any web client.
Plugins - Checks for outdated or risky browser plugins during authentication.
- Flash
- Block Flash: Denies access if the plugin is detected in the browser.
- Allow Flash: Permits access regardless of the plugin’s presence or version.
- Java
- Block all versions: Denies access if the plugin is detected in the browser
- Warn users when their Java plugin is out of date: Allows access but prompts the user to update the vulnerable plugin.
- Block if out of date by more than: Escalates the warning to a hard block if the plugin is excessively outdated.
- Allow all versions: Permits access regardless of the plugin’s presence or version.
Authorized networks - Defines trusted IP addresses or CIDR blocks (e.g., a corporate office VPN).
- Skip MFA from these networks (passwordless authentication is not skipped): Bypasses the 2FA requirement when users authenticate from the specified trusted IPs.
- Require enrollment from these networks: Enforces that unenrolled users can only set up their initial 2FA device while physically on the corporate network.
- Require MFA from these networks every time, even if it would normally be skipped: Overrides any other bypass settings (like remembered devices), strictly enforcing 2FA for these specific IPs.
- Block access from these networks
- Block access from any other network not specified above: Acts as a strict allowlist. Users can only log in if they are on the defined authorized networks; all external traffic is blocked.
- Block access from these networks: Acts as a blocklist, denying logins from specified malicious or unauthorized IP ranges.
Anonymous networks - Detects and filters traffic from IP addresses associated with Tor, anonymous proxies, and known VPN providers.
- For users who request access through proxies, Tor, or VPN:
- Require MFA or passwordless authentication every time, even if it would normally be skipped: Steps up security by forcing a 2FA prompt to verify identity when an anonymized connection is detected, ignoring bypass rules.
- Block access: Denies all authentication attempts originating from anonymity networks to thwart automated credential-stuffing attacks.
- Don’t change authentication requirements: Ignores the anonymous network status and applies standard policy rules.
- Advanced settings
- Only check access device IP: Evaluates the direct client IP against anonymous network databases, ignoring downstream routing headers.
Risk-based factor selection - Dynamically analyzes the context of a login attempt (such as a new device, unusual location, or impossible travel).
- Limit authentication methods
- Limit authentication methods based on risk: Automatically restricts the user to highly secure 2FA methods (like Verified Push or WebAuthn) and disables weak methods (like SMS) when anomalous behavior is detected.
- Don’t limit authentication methods based on risk: Disables dynamic risk analysis.
- Set code length for Verified Duo Push
- Digit code: Defines how many numbers (e.g., 3 to 6 digits) the user must type into their phone to approve a high-risk login.
- Add trusted networks: Exempts specified IP ranges from risk-based step-ups, assuming corporate networks are inherently low-risk.
Authentication methods - Specifies exactly which 2FA methods users are allowed to use to verify their identity.
- Second-factor authentication (2FA)
- Platform authenticator (passkey / WebAuthn): Allows native biometrics like Touch ID, Face ID, or Windows Hello.
- Roaming authenticator (passkey / WebAuthn): Allows external hardware security keys (e.g., YubiKey).
- Require user verification with a PIN or biometric: Ensures the security key cannot be used if stolen without knowing the key’s PIN.
- Duo Mobile Push: Allows standard tap-to-approve push notifications.
- Require a Verified Duo Push: Forces the user to type a code displayed on the login screen into their app, preventing accidental approvals (MFA fatigue).
- Verification code length: Sets the required digits.
- Require users to enter a verification code: Enforces manual entry.
- Autofill the verification code with Bluetooth when possible: Streamlines the Verified Push process by securely transmitting the code via Bluetooth if the phone and computer are near each other.
- Require proximity verification with Bluetooth: Strictly enforces that the phone must be physically next to the computer to approve the push.
- Duo Desktop authentication: Allows using the desktop app as an authenticator.
- Duo Mobile passcode: Toggles the availability of offline codes.
- SMS passcode: Toggles the availability of text messages.
- Send new passcodes when delivery fails: Automatically attempts to resend an SMS code if carrier delivery issues are detected.
- Hardware tokens: Toggles the availability of physical OTP tokens.
- Bypass code: Toggles the availability of admin-generated bypass codes.
- Passwordless authentication in SSO
- Platform authenticator (passkey / WebAuthn): Allows users to log in without a password using biometric sensors built into their device, such as Apple Touch ID/Face ID or Windows Hello.
- Roaming authenticator (passkey / WebAuthn): Permits passwordless logins using external, portable security keys (such as YubiKeys) plugged into the device.
- Duo Mobile Push: Allows users to approve a passwordless login request by tapping a push notification on their Duo Mobile app.
- Use browser cookies for verification when Duo Desktop is unavailable: Falls back to secure cookies to verify the endpoint if the Duo Desktop app isn’t running.
- Bluetooth Proximity Verification
- Required only when the endpoint is unverified and no password fallback is available: Forces Bluetooth proximity checks only on untrusted computers.
- Required for every passwordless login, including verified endpoints: Strictly enforces Bluetooth proximity for all passwordless attempts to guarantee physical presence.
- Bypass code: Allows users to enter an admin-generated fallback code to access the SSO portal without a password if their primary authentication method is unavailable.
Duo Mobile app - Mandates a minimum version of the Duo Mobile app installed on the user's smartphone.
- Warn users to update version: Prompts users to update their app via the App Store/Google Play while still allowing them to authenticate.
- Schedule: Applies a delayed enforcement date for the warning.
- Block version: Outright denies push approvals if the app is older than the specified version.
- Schedule: Applies a delayed enforcement date for the block.
- Summary: Displays the active app version requirements.
Tampered devices - Detects if the mobile device used for authentication has its core OS security bypassed.
- Block authentication from tampered devices: Denies push approvals from jailbroken (iOS) or rooted (Android) devices, which are highly susceptible to malware and token theft.
- Allow authentication from tampered devices: Ignores the compromised status of the device’s operating system.
Screen lock - Requires the user's mobile device to have a local security barrier.
- Block authentication from devices without a screen lock: Ensures the user has a PIN, pattern, or biometric lock on their phone. This prevents a thief who steals an unlocked phone from approving 2FA prompts.
- Allow authentication from devices without a screen lock: Permits push approvals even if the phone has no local security.
Full-disk encryption - Validates mobile device storage encryption.
- Block authentication from Android devices without full-disk encryption: Denies use of the Duo app if the device’s native storage is unencrypted, protecting the 2FA token data at rest.
- Allow authentication from Android devices without full-disk encryption: Ignores the encryption status of the mobile device.
Mobile device biometrics - Adds an extra verification layer to the Duo Mobile app.
- Require additional biometric verification: Forces the user to scan their Face ID, Touch ID, or Android fingerprint before the Duo app will authorize a push approval, ensuring the authorized user is holding the phone.
- Block device passcode as a fallback when biometric verification fails: Strictly requires the biometric scan to succeed. The user cannot bypass a failed fingerprint scan by typing their phone PIN.
- Don’t require additional biometric verification: Allows users to approve pushes by simply tapping the screen on an unlocked device.
Step 3: Save and Assign
- Click Save at the bottom of the configuration page.
- Navigate to the Applications or Groups at the left navigation panel to assign this newly created policy to the appropriate targets in your environment.
Conclusion
By following this guide, you can successfully configure Cisco Duo policies to enforce strong security postures, mitigate unauthorized access risks, and ensure compliance across your organization’s endpoints and applications.
For further assistance or inquiries, please contact our support team at support@ipserverone.com.