[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EGETC37TTYYWB15ZP65F79":3,"skill-same:01M7EGETC37TTYYWB15ZP65F79":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M7EGETC37TTYYWB15ZP65F79","configuring-multi-factor-authentication-with-duo",null,"Deploys Cisco Duo multi-factor authentication across enterprise applications, VPN, RDP, and SSH access points, covering Duo Authentication Proxy setup, adaptive authentication policies, device trust assessment, and phishing-resistant WebAuthn\u002FFIDO2 deployment aligned with NIST 800-63B AAL2\u002FAAL3. Use when adding or hardening MFA for remote access, VPN, or privileged logins with Duo.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fconfiguring-multi-factor-authentication-with-duo\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: configuring-multi-factor-authentication-with-duo\ndescription: Deploys Cisco Duo multi-factor authentication across enterprise applications,\n  VPN, RDP, and SSH access points, covering Duo Authentication Proxy setup, adaptive\n  authentication policies, device trust assessment, and phishing-resistant WebAuthn\u002FFIDO2\n  deployment aligned with NIST 800-63B AAL2\u002FAAL3. Use when adding or hardening MFA\n  for remote access, VPN, or privileged logins with Duo.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- iam\n- identity\n- access-control\n- authentication\n- mfa\n- duo\n- multi-factor\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AA-01\n- PR.AA-02\n- PR.AA-05\n- PR.AA-06\nmitre_attack:\n- T1621\n- T1110.004\n- T1110.003\n- T1078\n- T1556.006\n---\n# Configuring Multi-Factor Authentication with Duo\n\n## Overview\nDeploy 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\u002FAAL3 requirements.\n\n\n## When to Use\n\n- When deploying or configuring configuring multi factor authentication with duo capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with identity access management concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n- Configure Duo MFA for VPN, RDP, SSH, and web applications\n- Implement adaptive access policies based on user, device, and network context\n- Deploy phishing-resistant authentication (Duo Verified Push, WebAuthn)\n- Configure device health policies (trusted endpoints, OS version enforcement)\n- Set up Duo Admin Panel monitoring and reporting\n- Implement MFA bypass and emergency access procedures\n\n## Key Concepts\n\n### Duo Authentication Methods (by security strength)\n1. **Security Keys (WebAuthn\u002FFIDO2)**: Phishing-resistant, AAL3 capable\n2. **Duo Verified Push**: Requires code entry, resistant to MFA fatigue attacks\n3. **Duo Push**: Push notification to Duo Mobile app\n4. **TOTP (Duo Mobile Passcode)**: Time-based one-time password\n5. **Hardware Tokens**: OTP from physical token\n6. **SMS\u002FPhone Call**: Least secure, use only as fallback\n\n### Duo Integration Architecture\n- **Duo Authentication Proxy**: On-premises proxy for RADIUS\u002FLDAP integration\n- **Duo Web SDK**: Embed Duo MFA in web applications\n- **Duo OIDC\u002FSAML**: SSO integration for cloud applications\n- **Duo for RDP**: Windows Logon MFA\n- **Duo Unix**: PAM-based MFA for SSH\n\n### Adaptive Access Policies\n- **Trusted Networks**: Reduce MFA friction for corporate networks\n- **Remembered Devices**: Skip MFA for trusted devices (configurable duration)\n- **Device Health**: Block or require MFA based on OS patch level, encryption, firewall\n- **Risk-Based Authentication**: Step-up MFA for anomalous login patterns\n\n## Workflow\n\n### Step 1: Duo Authentication Proxy Setup\n1. Deploy Duo Authentication Proxy on Windows\u002FLinux server\n2. Configure primary authentication (AD\u002FLDAP or RADIUS)\n3. Configure Duo API credentials (Integration Key, Secret Key, API Hostname)\n4. Set failmode (safe=deny if Duo unreachable, secure=allow)\n5. Test proxy connectivity to Duo cloud and AD\n\n### Step 2: VPN MFA Integration\n1. Configure VPN concentrator for RADIUS authentication\n2. Point RADIUS to Duo Authentication Proxy\n3. Configure Duo proxy with [radius_server_auto] section\n4. Test VPN login with Duo Push\n5. Deploy to all VPN users with enrollment period\n\n### Step 3: RDP\u002FWindows Logon MFA\n1. Install Duo Authentication for Windows Logon on target servers\n2. Configure Duo application in Admin Panel\n3. Set offline access options (allow N offline logins)\n4. Configure bypass for service accounts\n5. Test RDP login with Duo MFA\n\n### Step 4: Adaptive Policy Configuration\n1. Create user groups (Standard, Privileged, Contractors)\n2. Configure per-group authentication policies:\n   - Standard: Duo Push allowed, remembered device 7 days\n   - Privileged: Verified Push required, no remembered device\n   - Contractors: WebAuthn required, no remembered device\n3. Configure device health policies:\n   - Require encrypted disk\n   - Block outdated OS versions\n   - Require firewall enabled\n4. Set trusted network exceptions for corporate IPs\n\n### Step 5: Phishing-Resistant MFA Deployment\n1. Enable Verified Push (requires entering 3-digit code from login screen)\n2. Register WebAuthn\u002FFIDO2 security keys for privileged users\n3. Disable SMS and phone call for high-risk groups\n4. Configure Duo Risk-Based Factor Selection\n5. Monitor for MFA fatigue attack patterns\n\n### Step 6: Monitoring and Response\n1. Configure Duo Admin Panel alerts\n2. Set up authentication log forwarding to SIEM\n3. Monitor for: MFA denial patterns, bypass usage, new device enrollments\n4. Create incident response playbook for MFA compromise\n5. Regular review of bypass and exception policies\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| MFA | IA-2(1) | Multi-factor authentication for network access |\n| MFA for Privileged | IA-2(2) | MFA for privileged account access |\n| Replay Resistance | IA-2(8) | Replay-resistant authentication |\n| Device Identification | IA-3 | Device identity and trust |\n| Authenticator Management | IA-5 | MFA enrollment and lifecycle |\n\n## Common Pitfalls\n- Not deploying phishing-resistant MFA (Verified Push\u002FFIDO2) for privileged accounts\n- Setting failmode to \"safe\" (allow access when Duo is down) in production\n- Not disabling SMS\u002Fphone call for users with app-capable devices\n- Forgetting to configure offline access for laptops\n- Not monitoring for MFA fatigue\u002Fprompt bombing attacks\n\n## Verification\n- [ ] VPN login requires Duo MFA\n- [ ] RDP to servers requires Duo MFA\n- [ ] SSH access requires Duo MFA\n- [ ] Verified Push enabled for privileged users\n- [ ] Device health policy blocks non-compliant devices\n- [ ] Authentication logs forwarded to SIEM\n- [ ] Bypass\u002Femergency access procedures tested\n- [ ] MFA fatigue detection alerts configured\n","# Configuring Multi-Factor Authentication with Duo\n\n## Overview\nDeploy 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\u002FAAL3 requirements.\n\n\n## When to Use\n\n- When deploying or configuring configuring multi factor authentication with duo capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with identity access management concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n- Configure Duo MFA for VPN, RDP, SSH, and web applications\n- Implement adaptive access policies based on user, device, and network context\n- Deploy phishing-resistant authentication (Duo Verified Push, WebAuthn)\n- Configure device health policies (trusted endpoints, OS version enforcement)\n- Set up Duo Admin Panel monitoring and reporting\n- Implement MFA bypass and emergency access procedures\n\n## Key Concepts\n\n### Duo Authentication Methods (by security strength)\n1. **Security Keys (WebAuthn\u002FFIDO2)**: Phishing-resistant, AAL3 capable\n2. **Duo Verified Push**: Requires code entry, resistant to MFA fatigue attacks\n3. **Duo Push**: Push notification to Duo Mobile app\n4. **TOTP (Duo Mobile Passcode)**: Time-based one-time password\n5. **Hardware Tokens**: OTP from physical token\n6. **SMS\u002FPhone Call**: Least secure, use only as fallback\n\n### Duo Integration Architecture\n- **Duo Authentication Proxy**: On-premises proxy for RADIUS\u002FLDAP integration\n- **Duo Web SDK**: Embed Duo MFA in web applications\n- **Duo OIDC\u002FSAML**: SSO integration for cloud applications\n- **Duo for RDP**: Windows Logon MFA\n- **Duo Unix**: PAM-based MFA for SSH\n\n### Adaptive Access Policies\n- **Trusted Networks**: Reduce MFA friction for corporate networks\n- **Remembered Devices**: Skip MFA for trusted devices (configurable duration)\n- **Device Health**: Block or require MFA based on OS patch level, encryption, firewall\n- **Risk-Based Authentication**: Step-up MFA for anomalous login patterns\n\n## Workflow\n\n### Step 1: Duo Authentication Proxy Setup\n1. Deploy Duo Authentication Proxy on Windows\u002FLinux server\n2. Configure primary authentication (AD\u002FLDAP or RADIUS)\n3. Configure Duo API credentials (Integration Key, Secret Key, API Hostname)\n4. Set failmode (safe=deny if Duo unreachable, secure=allow)\n5. Test proxy connectivity to Duo cloud and AD\n\n### Step 2: VPN MFA Integration\n1. Configure VPN concentrator for RADIUS authentication\n2. Point RADIUS to Duo Authentication Proxy\n3. Configure Duo proxy with [radius_server_auto] section\n4. Test VPN login with Duo Push\n5. Deploy to all VPN users with enrollment period\n\n### Step 3: RDP\u002FWindows Logon MFA\n1. Install Duo Authentication for Windows Logon on target servers\n2. Configure Duo application in Admin Panel\n3. Set offline access options (allow N offline logins)\n4. Configure bypass for service accounts\n5. Test RDP login with Duo MFA\n\n### Step 4: Adaptive Policy Configuration\n1. Create user groups (Standard, Privileged, Contractors)\n2. Configure per-group authentication policies:\n   - Standard: Duo Push allowed, remembered device 7 days\n   - Privileged: Verified Push required, no remembered device\n   - Contractors: WebAuthn required, no remembered device\n3. Configure device health policies:\n   - Require encrypted disk\n   - Block outdated OS versions\n   - Require firewall enabled\n4. Set trusted network exceptions for corporate IPs\n\n### Step 5: Phishing-Resistant MFA Deployment\n1. Enable Verified Push (requires entering 3-digit code from login screen)\n2. Register WebAuthn\u002FFIDO2 security keys for privileged users\n3. Disable SMS and phone call for high-risk groups\n4. Configure Duo Risk-Based Factor Selection\n5. Monitor for MFA fatigue attack patterns\n\n### Step 6: Monitoring and Response\n1. Configure Duo Admin Panel alerts\n2. Set up authentication log forwarding to SIEM\n3. Monitor for: MFA denial patterns, bypass usage, new device enrollments\n4. Create incident response playbook for MFA compromise\n5. Regular review of bypass and exception policies\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| MFA | IA-2(1) | Multi-factor authentication for network access |\n| MFA for Privileged | IA-2(2) | MFA for privileged account access |\n| Replay Resistance | IA-2(8) | Replay-resistant authentication |\n| Device Identification | IA-3 | Device identity and trust |\n| Authenticator Management | IA-5 | MFA enrollment and lifecycle |\n\n## Common Pitfalls\n- Not deploying phishing-resistant MFA (Verified Push\u002FFIDO2) for privileged accounts\n- Setting failmode to \"safe\" (allow access when Duo is down) in production\n- Not disabling SMS\u002Fphone call for users with app-capable devices\n- Forgetting to configure offline access for laptops\n- Not monitoring for MFA fatigue\u002Fprompt bombing attacks\n\n## Verification\n- [ ] VPN login requires Duo MFA\n- [ ] RDP to servers requires Duo MFA\n- [ ] SSH access requires Duo MFA\n- [ ] Verified Push enabled for privileged users\n- [ ] Device health policy blocks non-compliant devices\n- [ ] Authentication logs forwarded to SIEM\n- [ ] Bypass\u002Femergency access procedures tested\n- [ ] MFA fatigue detection alerts configured\n",{"name":5,"tags":24,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":40,"description":7,"mitre_attack":41},[25,26,27,28,29,30,31],"iam","identity","access-control","authentication","mfa","duo","multi-factor","mahipal","cybersecurity","1.0",[36,37,38,39],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[42,43,44,45,46],"T1621","T1110.004","T1110.003","T1078","T1556.006","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fconfiguring-multi-factor-authentication-with-duo",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill configuring-multi-factor-authentication-with-duo",{"tool":61,"command":62},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill configuring-multi-factor-authentication-with-duo",{"tool":64,"command":65},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill configuring-multi-factor-authentication-with-duo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fconfiguring-multi-factor-authentication-with-duo\u002FSKILL.md",true,[69,75,79],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fapi-reference.md","REFERENCE","参考文档",1488,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fconfiguring-multi-factor-authentication-with-duo\u002Freferences\u002Fapi-reference.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fstandards.md",1240,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fconfiguring-multi-factor-authentication-with-duo\u002Freferences\u002Fstandards.md",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fworkflows.md",1588,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fconfiguring-multi-factor-authentication-with-duo\u002Freferences\u002Fworkflows.md",[84,93,98,105,112,119],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":94,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":92},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":92},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":92},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":92},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":92},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]