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.
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
Implementation Steps
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: none-313description: 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 4domain: cybersecurity5subdomain: identity-access-management6tags: [iam, identity, access-control, authentication, mfa, duo, multi-factor]7version: "1.0"8author: mahipal9license: MIT10metadata:11 source: https://skillmd.com/skills/njones17/none-3112---1314# Configuring Multi-Factor Authentication with Duo1516## Overview17Deploy 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.1819## Objectives20- Configure Duo MFA for VPN, RDP, SSH, and web applications21- Implement adaptive access policies based on user, device, and network context22- Deploy phishing-resistant authentication (Duo Verified Push, WebAuthn)23- Configure device health policies (trusted endpoints, OS version enforcement)24- Set up Duo Admin Panel monitoring and reporting25- Implement MFA bypass and emergency access procedures2627## Key Concepts2829### Duo Authentication Methods (by security strength)301. **Security Keys (WebAuthn/FIDO2)**: Phishing-resistant, AAL3 capable312. **Duo Verified Push**: Requires code entry, resistant to MFA fatigue attacks323. **Duo Push**: Push notification to Duo Mobile app334. **TOTP (Duo Mobile Passcode)**: Time-based one-time password345. **Hardware Tokens**: OTP from physical token356. **SMS/Phone Call**: Least secure, use only as fallback3637### Duo Integration Architecture38- **Duo Authentication Proxy**: On-premises proxy for RADIUS/LDAP integration39- **Duo Web SDK**: Embed Duo MFA in web applications40- **Duo OIDC/SAML**: SSO integration for cloud applications41- **Duo for RDP**: Windows Logon MFA42- **Duo Unix**: PAM-based MFA for SSH4344### Adaptive Access Policies45- **Trusted Networks**: Reduce MFA friction for corporate networks46- **Remembered Devices**: Skip MFA for trusted devices (configurable duration)47- **Device Health**: Block or require MFA based on OS patch level, encryption, firewall48- **Risk-Based Authentication**: Step-up MFA for anomalous login patterns4950## Implementation Steps5152### Step 1: Duo Authentication Proxy Setup531. Deploy Duo Authentication Proxy on Windows/Linux server542. Configure primary authentication (AD/LDAP or RADIUS)553. Configure Duo API credentials (Integration Key, Secret Key, API Hostname)564. Set failmode (safe=deny if Duo unreachable, secure=allow)575. Test proxy connectivity to Duo cloud and AD5859### Step 2: VPN MFA Integration601. Configure VPN concentrator for RADIUS authentication612. Point RADIUS to Duo Authentication Proxy623. Configure Duo proxy with [radius_server_auto] section634. Test VPN login with Duo Push645. Deploy to all VPN users with enrollment period6566### Step 3: RDP/Windows Logon MFA671. Install Duo Authentication for Windows Logon on target servers682. Configure Duo application in Admin Panel693. Set offline access options (allow N offline logins)704. Configure bypass for service accounts715. Test RDP login with Duo MFA7273### Step 4: Adaptive Policy Configuration741. Create user groups (Standard, Privileged, Contractors)752. Configure per-group authentication policies:76 - Standard: Duo Push allowed, remembered device 7 days77 - Privileged: Verified Push required, no remembered device78 - Contractors: WebAuthn required, no remembered device793. Configure device health policies:80 - Require encrypted disk81 - Block outdated OS versions82 - Require firewall enabled834. Set trusted network exceptions for corporate IPs8485### Step 5: Phishing-Resistant MFA Deployment861. Enable Verified Push (requires entering 3-digit code from login screen)872. Register WebAuthn/FIDO2 security keys for privileged users883. Disable SMS and phone call for high-risk groups894. Configure Duo Risk-Based Factor Selection905. Monitor for MFA fatigue attack patterns9192### Step 6: Monitoring and Response931. Configure Duo Admin Panel alerts942. Set up authentication log forwarding to SIEM953. Monitor for: MFA denial patterns, bypass usage, new device enrollments964. Create incident response playbook for MFA compromise975. Regular review of bypass and exception policies9899## Security Controls100| Control | NIST 800-53 | Description |101|---------|-------------|-------------|102| MFA | IA-2(1) | Multi-factor authentication for network access |103| MFA for Privileged | IA-2(2) | MFA for privileged account access |104| Replay Resistance | IA-2(8) | Replay-resistant authentication |105| Device Identification | IA-3 | Device identity and trust |106| Authenticator Management | IA-5 | MFA enrollment and lifecycle |107108## Common Pitfalls109- Not deploying phishing-resistant MFA (Verified Push/FIDO2) for privileged accounts110- Setting failmode to "safe" (allow access when Duo is down) in production111- Not disabling SMS/phone call for users with app-capable devices112- Forgetting to configure offline access for laptops113- Not monitoring for MFA fatigue/prompt bombing attacks114115## Verification116- [ ] VPN login requires Duo MFA117- [ ] RDP to servers requires Duo MFA118- [ ] SSH access requires Duo MFA119- [ ] Verified Push enabled for privileged users120- [ ] Device health policy blocks non-compliant devices121- [ ] Authentication logs forwarded to SIEM122- [ ] Bypass/emergency access procedures tested123- [ ] MFA fatigue detection alerts configured