[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE5D0GYRRB89Y5CS8ZP4HF":3,"skill-same:01M6AE5D0GYRRB89Y5CS8ZP4HF":133},{"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":23,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6AE5D0GYRRB89Y5CS8ZP4HF","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.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35884,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-multi-factor-authentication-with-duo\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"configuring multi factor authentication with duo","authentication","Enterprise","multi-factor","duo","mfa","NIST","hardening","iam","access-control","cybersecurity","phishing","proxy","deployment","assessment","pr","setup","identity","2026-11-10 10:12:30",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":47,"author":48,"domain":34,"license":15,"version":49,"nist_csf":50,"subdomain":55,"description":7,"mitre_attack":56},[32,41,33,25,29,28,27],"mahipal","1.0",[51,52,53,54],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[57,58,59,60,61],"T1621","T1110.004","T1110.003","T1078","T1556.006","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fconfiguring-multi-factor-authentication-with-duo",4379,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill configuring-multi-factor-authentication-with-duo",{"tool":78,"command":79},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill configuring-multi-factor-authentication-with-duo",{"tool":81,"command":82},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill configuring-multi-factor-authentication-with-duo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-multi-factor-authentication-with-duo\u002FSKILL.md",true,[86,92,96,102,107,111,115,119,123,129],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"AGENT-BRIEF.md","REFERENCE","参考文档",7942,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Ftriage\u002FAGENT-BRIEF.md",{"path":93,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":94,"sourceHtmlUrl":95},"agents\u002Fopenai.yaml",135,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Ftriage\u002Fagents\u002Fopenai.yaml",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"assets\u002Ftemplate.md","ASSET","资产文件",1452,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-multi-factor-authentication-with-duo\u002Fassets\u002Ftemplate.md",{"path":103,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-multi-factor-authentication-with-duo\u002FLICENSE",{"path":108,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":109,"sourceHtmlUrl":110},"OUT-OF-SCOPE.md",4667,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Ftriage\u002FOUT-OF-SCOPE.md",{"path":112,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fapi-reference.md",1488,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-multi-factor-authentication-with-duo\u002Freferences\u002Fapi-reference.md",{"path":116,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fstandards.md",1240,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-multi-factor-authentication-with-duo\u002Freferences\u002Fstandards.md",{"path":120,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Fworkflows.md",1588,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-multi-factor-authentication-with-duo\u002Freferences\u002Fworkflows.md",{"path":124,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":127,"sourceHtmlUrl":128},"scripts\u002Fagent.py","SCRIPT","脚本",4816,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-multi-factor-authentication-with-duo\u002Fscripts\u002Fagent.py",{"path":130,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":131,"sourceHtmlUrl":132},"scripts\u002Fprocess.py",11693,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-multi-factor-authentication-with-duo\u002Fscripts\u002Fprocess.py",[134,159,183,211,237,264],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":42},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[140],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[142,143,144,145,146,34,147,41,39,148,149,150,151,152,153,154,155,156,157,158],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","security","incident response","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":166,"publishedAt":42},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[165],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[167,155,168,169,146,170,34,39,171,172,173,174,175,176,177,178,179,180,181,182],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":193,"publishedAt":42},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[189,192],{"categoryNo":190,"categoryName":191,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[177,194,195,196,197,34,198,199,171,200,201,202,203,204,205,206,207,208,209,210],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":218,"publishedAt":42},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[217],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[219,220,221,34,222,223,224,225,226,227,228,229,230,231,232,233,174,234,235,236],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":238,"name":239,"nameZh":6,"description":240,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":241,"categories":242,"keywords":244,"publishedAt":42},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[243],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[245,246,247,34,248,249,250,251,252,253,254,255,256,257,258,259,260,261,262,263],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":265,"name":266,"nameZh":6,"description":267,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":268,"categories":269,"keywords":271,"publishedAt":42},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[270],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[146,272,34,273,274,275,276,277,30,278,279,206,280,207,281,282,283,284,285,286],"triaging security incident","siem","file","ioc","soc","NIST-800-61","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]