Configuring Multi-Factor Authentication with Duo
Overview
Deploy Cisco Duo multi-factor authentication across enterprise applications, VPN, RDP, and SSH access points. This skill covers Duo integration methods, adaptive authentication policies, device trust assessment, and phishing-resistant MFA deployment aligned with NIST 800-63B AAL2/AAL3 requirements.
When to Use
- When deploying or configuring configuring multi factor authentication with duo capabilities in your environment
- When establishing security controls aligned to compliance requirements
- When building or improving security architecture for this domain
- When conducting security assessments that require this implementation
Prerequisites
- Familiarity with identity access management concepts and tools
- Access to a test or lab environment for safe execution
- Python 3.8+ with required dependencies installed
- Appropriate authorization for any testing activities
Objectives
- Configure Duo MFA for VPN, RDP, SSH, and web applications
- Implement adaptive access policies based on user, device, and network context
- Deploy phishing-resistant authentication (Duo Verified Push, WebAuthn)
- Configure device health policies (trusted endpoints, OS version enforcement)
- Set up Duo Admin Panel monitoring and reporting
- Implement MFA bypass and emergency access procedures
Key Concepts
Duo Authentication Methods (by security strength)
- Security Keys (WebAuthn/FIDO2): Phishing-resistant, AAL3 capable
- Duo Verified Push: Requires code entry, resistant to MFA fatigue attacks
- Duo Push: Push notification to Duo Mobile app
- TOTP (Duo Mobile Passcode): Time-based one-time password
- Hardware Tokens: OTP from physical token
- SMS/Phone Call: Least secure, use only as fallback
Duo Integration Architecture
- Duo Authentication Proxy: On-premises proxy for RADIUS/LDAP integration
- Duo Web SDK: Embed Duo MFA in web applications
- Duo OIDC/SAML: SSO integration for cloud applications
- Duo for RDP: Windows Logon MFA
- Duo Unix: PAM-based MFA for SSH
Adaptive Access Policies
- Trusted Networks: Reduce MFA friction for corporate networks
- Remembered Devices: Skip MFA for trusted devices (configurable duration)
- Device Health: Block or require MFA based on OS patch level, encryption, firewall
- Risk-Based Authentication: Step-up MFA for anomalous login patterns
Workflow
Step 1: Duo Authentication Proxy Setup
- Deploy Duo Authentication Proxy on Windows/Linux server
- Configure primary authentication (AD/LDAP or RADIUS)
- Configure Duo API credentials (Integration Key, Secret Key, API Hostname)
- Set failmode (safe=deny if Duo unreachable, secure=allow)
- Test proxy connectivity to Duo cloud and AD
Step 2: VPN MFA Integration
- Configure VPN concentrator for RADIUS authentication
- Point RADIUS to Duo Authentication Proxy
- Configure Duo proxy with [radius_server_auto] section
- Test VPN login with Duo Push
- Deploy to all VPN users with enrollment period
Step 3: RDP/Windows Logon MFA
- Install Duo Authentication for Windows Logon on target servers
- Configure Duo application in Admin Panel
- Set offline access options (allow N offline logins)
- Configure bypass for service accounts
- Test RDP login with Duo MFA
Step 4: Adaptive Policy Configuration
- Create user groups (Standard, Privileged, Contractors)
- Configure per-group authentication policies:
- Standard: Duo Push allowed, remembered device 7 days
- Privileged: Verified Push required, no remembered device
- Contractors: WebAuthn required, no remembered device
- Configure device health policies:
- Require encrypted disk
- Block outdated OS versions
- Require firewall enabled
- Set trusted network exceptions for corporate IPs
Step 5: Phishing-Resistant MFA Deployment
- Enable Verified Push (requires entering 3-digit code from login screen)
- Register WebAuthn/FIDO2 security keys for privileged users
- Disable SMS and phone call for high-risk groups
- Configure Duo Risk-Based Factor Selection
- Monitor for MFA fatigue attack patterns
Step 6: Monitoring and Response
- Configure Duo Admin Panel alerts
- Set up authentication log forwarding to SIEM
- Monitor for: MFA denial patterns, bypass usage, new device enrollments
- Create incident response playbook for MFA compromise
- Regular review of bypass and exception policies
Security Controls
| Control |
NIST 800-53 |
Description |
| MFA |
IA-2(1) |
Multi-factor authentication for network access |
| MFA for Privileged |
IA-2(2) |
MFA for privileged account access |
| Replay Resistance |
IA-2(8) |
Replay-resistant authentication |
| Device Identification |
IA-3 |
Device identity and trust |
| Authenticator Management |
IA-5 |
MFA enrollment and lifecycle |
Common Pitfalls
- Not deploying phishing-resistant MFA (Verified Push/FIDO2) for privileged accounts
- Setting failmode to "safe" (allow access when Duo is down) in production
- Not disabling SMS/phone call for users with app-capable devices
- Forgetting to configure offline access for laptops
- Not monitoring for MFA fatigue/prompt bombing attacks
Verification
1---2name: configuring-multi-factor-authentication-with-duo3description: Deploys Cisco Duo multi-factor authentication across enterprise applications,4 VPN, RDP, and SSH access points, covering Duo Authentication Proxy setup, adaptive5 authentication policies, device trust assessment, and phishing-resistant WebAuthn/FIDO26 deployment aligned with NIST 800-63B AAL2/AAL3. Use when adding or hardening MFA7 for remote access, VPN, or privileged logins with Duo.8domain: cybersecurity9subdomain: identity-access-management10tags:11- iam12- identity13- access-control14- authentication15- mfa16- duo17- multi-factor18version: '1.0'19author: mahipal20license: Apache-2.021nist_csf:22- PR.AA-0123- PR.AA-0224- PR.AA-0525- PR.AA-0626mitre_attack:27- T162128- T1110.00429- T1110.00330- T107831- T1556.00632metadata:33 source: https://skillmd.com/skills/26zl/configuring-multi-factor-authentication-with-duo34---3536# Configuring Multi-Factor Authentication with Duo3738## Overview39Deploy Cisco Duo multi-factor authentication across enterprise applications, VPN, RDP, and SSH access points. This skill covers Duo integration methods, adaptive authentication policies, device trust assessment, and phishing-resistant MFA deployment aligned with NIST 800-63B AAL2/AAL3 requirements.404142## When to Use4344- When deploying or configuring configuring multi factor authentication with duo capabilities in your environment45- When establishing security controls aligned to compliance requirements46- When building or improving security architecture for this domain47- When conducting security assessments that require this implementation4849## Prerequisites5051- Familiarity with identity access management concepts and tools52- Access to a test or lab environment for safe execution53- Python 3.8+ with required dependencies installed54- Appropriate authorization for any testing activities5556## Objectives57- Configure Duo MFA for VPN, RDP, SSH, and web applications58- Implement adaptive access policies based on user, device, and network context59- Deploy phishing-resistant authentication (Duo Verified Push, WebAuthn)60- Configure device health policies (trusted endpoints, OS version enforcement)61- Set up Duo Admin Panel monitoring and reporting62- Implement MFA bypass and emergency access procedures6364## Key Concepts6566### Duo Authentication Methods (by security strength)671. **Security Keys (WebAuthn/FIDO2)**: Phishing-resistant, AAL3 capable682. **Duo Verified Push**: Requires code entry, resistant to MFA fatigue attacks693. **Duo Push**: Push notification to Duo Mobile app704. **TOTP (Duo Mobile Passcode)**: Time-based one-time password715. **Hardware Tokens**: OTP from physical token726. **SMS/Phone Call**: Least secure, use only as fallback7374### Duo Integration Architecture75- **Duo Authentication Proxy**: On-premises proxy for RADIUS/LDAP integration76- **Duo Web SDK**: Embed Duo MFA in web applications77- **Duo OIDC/SAML**: SSO integration for cloud applications78- **Duo for RDP**: Windows Logon MFA79- **Duo Unix**: PAM-based MFA for SSH8081### Adaptive Access Policies82- **Trusted Networks**: Reduce MFA friction for corporate networks83- **Remembered Devices**: Skip MFA for trusted devices (configurable duration)84- **Device Health**: Block or require MFA based on OS patch level, encryption, firewall85- **Risk-Based Authentication**: Step-up MFA for anomalous login patterns8687## Workflow8889### Step 1: Duo Authentication Proxy Setup901. Deploy Duo Authentication Proxy on Windows/Linux server912. Configure primary authentication (AD/LDAP or RADIUS)923. Configure Duo API credentials (Integration Key, Secret Key, API Hostname)934. Set failmode (safe=deny if Duo unreachable, secure=allow)945. Test proxy connectivity to Duo cloud and AD9596### Step 2: VPN MFA Integration971. Configure VPN concentrator for RADIUS authentication982. Point RADIUS to Duo Authentication Proxy993. Configure Duo proxy with [radius_server_auto] section1004. Test VPN login with Duo Push1015. Deploy to all VPN users with enrollment period102103### Step 3: RDP/Windows Logon MFA1041. Install Duo Authentication for Windows Logon on target servers1052. Configure Duo application in Admin Panel1063. Set offline access options (allow N offline logins)1074. Configure bypass for service accounts1085. Test RDP login with Duo MFA109110### Step 4: Adaptive Policy Configuration1111. Create user groups (Standard, Privileged, Contractors)1122. Configure per-group authentication policies:113 - Standard: Duo Push allowed, remembered device 7 days114 - Privileged: Verified Push required, no remembered device115 - Contractors: WebAuthn required, no remembered device1163. Configure device health policies:117 - Require encrypted disk118 - Block outdated OS versions119 - Require firewall enabled1204. Set trusted network exceptions for corporate IPs121122### Step 5: Phishing-Resistant MFA Deployment1231. Enable Verified Push (requires entering 3-digit code from login screen)1242. Register WebAuthn/FIDO2 security keys for privileged users1253. Disable SMS and phone call for high-risk groups1264. Configure Duo Risk-Based Factor Selection1275. Monitor for MFA fatigue attack patterns128129### Step 6: Monitoring and Response1301. Configure Duo Admin Panel alerts1312. Set up authentication log forwarding to SIEM1323. Monitor for: MFA denial patterns, bypass usage, new device enrollments1334. Create incident response playbook for MFA compromise1345. Regular review of bypass and exception policies135136## Security Controls137| Control | NIST 800-53 | Description |138|---------|-------------|-------------|139| MFA | IA-2(1) | Multi-factor authentication for network access |140| MFA for Privileged | IA-2(2) | MFA for privileged account access |141| Replay Resistance | IA-2(8) | Replay-resistant authentication |142| Device Identification | IA-3 | Device identity and trust |143| Authenticator Management | IA-5 | MFA enrollment and lifecycle |144145## Common Pitfalls146- Not deploying phishing-resistant MFA (Verified Push/FIDO2) for privileged accounts147- Setting failmode to "safe" (allow access when Duo is down) in production148- Not disabling SMS/phone call for users with app-capable devices149- Forgetting to configure offline access for laptops150- Not monitoring for MFA fatigue/prompt bombing attacks151152## Verification153- [ ] VPN login requires Duo MFA154- [ ] RDP to servers requires Duo MFA155- [ ] SSH access requires Duo MFA156- [ ] Verified Push enabled for privileged users157- [ ] Device health policy blocks non-compliant devices158- [ ] Authentication logs forwarded to SIEM159- [ ] Bypass/emergency access procedures tested160- [ ] MFA fatigue detection alerts configured