| name | configuring-multi-factor-authentication-with-duo |
| description | 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 |
| domain | cybersecurity |
| subdomain | identity-access-management |
| tags | ["iam","identity","access-control","authentication","mfa","duo","multi-factor"] |
| version | 1.0 |
| author | mahipal |
| license | Apache-2.0 |
| nist_csf | ["PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06"] |
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
Common Misconfigurations & Verification
- Legacy-auth bypass: Duo protects the interactive logon but IMAP/POP/SMTP, basic-auth, and older RADIUS clients skip the second factor entirely. Verify there is no auth path that reaches the directory without traversing the Duo proxy, and block legacy protocols at the IdP — an MFA control that any protocol can sidestep is not enforced.
- Failmode set to "safe" (fail-open):
failmode=safe lets users in when Duo cloud is unreachable, so an attacker who blocks Duo connectivity defeats MFA. Confirm failmode=secure for privileged and internet-facing apps; grep the authproxy.cfg and test by blocking outbound 443 to Duo.
- MFA fatigue / push bombing: plain Duo Push lets attackers spam approvals. Verify Verified Push (code entry) or FIDO2 is required for privileged groups and that SMS/phone fallback is disabled for app-capable users.
- Bypass and remembered-device sprawl:
bypass status accounts and long "remembered device" windows silently exempt users. Confirm bypass is limited to monitored break-glass accounts and remembered-device duration is short (or off) for privileged groups.
- Verification: in the Duo Admin Panel pull the Authentication Log and confirm every privileged logon shows a second factor; list users with
status=bypass; attempt an IMAP/basic-auth login and confirm it is blocked, not silently allowed.
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
