[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFB21CJSZMFVYKTWRY7VGK":3,"skill-same:01M6AFB21CJSZMFVYKTWRY7VGK":146},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":87,"commitSha":88,"skillDirectory":89,"forksCount":90,"repositoryHtmlUrl":91,"repositoryHomepageUrl":92,"ownerHtmlUrl":93,"ownerBlogUrl":94,"ownerDescription":95,"updatedAt":96,"install":97,"resources":110},"01M6AFB21CJSZMFVYKTWRY7VGK","implementing-privileged-access-management-with-cyberark",null,"Deploy CyberArk Privileged Access Management to discover, vault, rotate, and monitor privileged credentials across enterprise infrastructure, covering vault architecture, session isolation, credential rotation policies, and integration with NIST 800-53 access control requirements. Use when standing up CyberArk PAM, vaulting privileged credentials, or designing credential rotation policies.","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\u002Fimplementing-privileged-access-management-with-cyberark\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,42,43],"implementing privileged access management with cyberark","iam","cyberark","privileged-access","PAM","t1098","initial-access","t1078","t1003","NIST","cybersecurity","access-control","Enterprise","integration","development","monitor","infrastructure","pr","identity","architecture","2026-11-10 10:12:30",false,"---\nname: implementing-privileged-access-management-with-cyberark\ndescription: Deploy CyberArk Privileged Access Management to discover, vault, rotate,\n  and monitor privileged credentials across enterprise infrastructure, covering\n  vault architecture, session isolation, credential rotation policies, and integration\n  with NIST 800-53 access control requirements. Use when standing up CyberArk PAM,\n  vaulting privileged credentials, or designing credential rotation policies.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- iam\n- identity\n- access-control\n- privileged-access\n- pam\n- cyberark\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- T1078\n- T1110\n- T1556\n- T1098\n- T1003\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - positioning\n  - resource-development\n  techniques:\n  - id: T1586\n    name: Compromise Accounts\n    tactic: resource-development\n    source: attack\n  - id: T1110\n    name: Brute Force\n    tactic: initial-access\n    source: attack\n  - id: F1033\n    name: Insider Access Abuse\n    tactic: initial-access\n    source: f3\n  - id: F1005.002\n    name: 'Account Manipulation: Add Authorized User'\n    tactic: positioning\n    source: f3\n  - id: F1006.002\n    name: 'Account Takeover: Exposed Login Credential'\n    tactic: initial-access\n    source: f3\n---\n# Implementing Privileged Access Management with CyberArk\n\n## Overview\nDeploy CyberArk Privileged Access Management to discover, vault, rotate, and monitor privileged credentials across enterprise infrastructure. This skill covers vault architecture, session isolation, credential rotation policies, and integration with NIST 800-53 access control requirements.\n\n\n## When to Use\n\n- When deploying or configuring implementing privileged access management with cyberark 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- Design CyberArk vault architecture with high availability\n- Implement automated privileged credential discovery and onboarding\n- Configure credential rotation policies for different account types\n- Deploy Privileged Session Manager (PSM) for session isolation and recording\n- Integrate CyberArk with SIEM for privileged access monitoring\n- Implement just-in-time (JIT) privileged access workflows\n\n## Key Concepts\n\n### CyberArk Architecture Components\n1. **Digital Vault**: Encrypted credential storage with FIPS 140-2 validated encryption\n2. **Central Policy Manager (CPM)**: Automated password rotation and verification\n3. **Privileged Session Manager (PSM)**: Session isolation, recording, and keystroke logging\n4. **Password Vault Web Access (PVWA)**: Web interface for credential management\n5. **Privileged Threat Analytics (PTA)**: Behavioral analytics for privileged accounts\n6. **Conjur Secrets Manager**: Application identity and secrets management\n\n### Vault Security Model\n- **Master Policy**: Global security settings (dual control, exclusive access, one-time passwords)\n- **Safes**: Logical containers for credentials with granular permissions\n- **Platforms**: Configuration profiles defining rotation, verification, and reconciliation\n- **Account Groups**: Link accounts sharing rotation dependencies\n\n### Credential Lifecycle\n1. **Discovery**: Scan infrastructure for privileged accounts\n2. **Onboarding**: Import accounts into vault with platform assignment\n3. **Rotation**: Automated password changes per policy schedule\n4. **Verification**: Periodic validation that vaulted credentials work\n5. **Reconciliation**: Re-sync credentials when vault and target are out of sync\n6. **Decommissioning**: Remove accounts no longer needed\n\n## Workflow\n\n### Step 1: Vault Architecture Design\n1. Deploy primary vault server in secured network segment\n2. Configure vault high availability with DR vault\n3. Harden vault server OS (remove unnecessary services, disable RDP)\n4. Configure firewall rules (only port 1858 from authorized components)\n5. Set up vault backup with encryption\n\n### Step 2: Safe and Policy Configuration\n1. Create safe hierarchy aligned with business units\n2. Define safe members with least-privilege roles:\n   - Safe Admins: manage safe membership\n   - Credential Managers: add\u002Fmodify accounts\n   - Auditors: view audit logs only\n   - Users: retrieve\u002Fuse credentials\n3. Configure Master Policy settings:\n   - Require dual control for credential retrieval\n   - Enable exclusive access (one user per credential at a time)\n   - Set one-time password mode for sensitive accounts\n\n### Step 3: Platform Configuration\n- Windows Domain Admin: Rotate every 24 hours, verify every 4 hours\n- Linux Root: Rotate every 72 hours with SSH key rotation\n- Database Admin (Oracle, SQL Server): Rotate every 24 hours\n- Network Devices: Rotate every 7 days\n- Service Accounts: Rotate on schedule with dependency management\n- Cloud IAM Keys: Rotate every 90 days with dual-key strategy\n\n### Step 4: Privileged Session Management\n1. Deploy PSM servers behind load balancer\n2. Configure session recording (video, keystroke, command logs)\n3. Set up session isolation (users connect through PSM, never directly)\n4. Define connection components for RDP, SSH, databases, web apps\n5. Configure live session monitoring and termination capabilities\n6. Set session recording retention (minimum 1 year for compliance)\n\n### Step 5: Integration and Monitoring\n1. Forward CyberArk audit logs to SIEM (CEF\u002FSyslog format)\n2. Configure PTA for behavioral analytics:\n   - Detect credential theft indicators\n   - Alert on suspicious privileged session activity\n   - Monitor unmanaged privileged account usage\n3. Integrate with ticketing system for access request workflows\n4. Set up alerts for failed rotation, verification failures, policy violations\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| Privileged Access | AC-6(7) | Privileged account controls |\n| Credential Management | IA-5 | Automated credential rotation |\n| Session Recording | AU-14 | Session audit capability |\n| Access Enforcement | AC-3 | Vault-enforced access policies |\n| Separation of Duties | AC-5 | Dual control for sensitive operations |\n\n## Common Pitfalls\n- Not configuring reconciliation accounts leading to lockouts after rotation\n- Setting rotation schedules too aggressive for service accounts with dependencies\n- Failing to test PSM connection components before production deployment\n- Not establishing break-glass procedures for vault unavailability\n- Overlooking network device credential management\n\n## Verification\n- [ ] Vault accessible only from authorized components\n- [ ] Credential rotation succeeds for all onboarded accounts\n- [ ] PSM sessions recorded and searchable\n- [ ] Dual control enforced for sensitive credential checkout\n- [ ] SIEM receives CyberArk audit events\n- [ ] Break-glass procedure tested and documented\n- [ ] DR vault failover tested successfully\n","# Implementing Privileged Access Management with CyberArk\n\n## Overview\nDeploy CyberArk Privileged Access Management to discover, vault, rotate, and monitor privileged credentials across enterprise infrastructure. This skill covers vault architecture, session isolation, credential rotation policies, and integration with NIST 800-53 access control requirements.\n\n\n## When to Use\n\n- When deploying or configuring implementing privileged access management with cyberark 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- Design CyberArk vault architecture with high availability\n- Implement automated privileged credential discovery and onboarding\n- Configure credential rotation policies for different account types\n- Deploy Privileged Session Manager (PSM) for session isolation and recording\n- Integrate CyberArk with SIEM for privileged access monitoring\n- Implement just-in-time (JIT) privileged access workflows\n\n## Key Concepts\n\n### CyberArk Architecture Components\n1. **Digital Vault**: Encrypted credential storage with FIPS 140-2 validated encryption\n2. **Central Policy Manager (CPM)**: Automated password rotation and verification\n3. **Privileged Session Manager (PSM)**: Session isolation, recording, and keystroke logging\n4. **Password Vault Web Access (PVWA)**: Web interface for credential management\n5. **Privileged Threat Analytics (PTA)**: Behavioral analytics for privileged accounts\n6. **Conjur Secrets Manager**: Application identity and secrets management\n\n### Vault Security Model\n- **Master Policy**: Global security settings (dual control, exclusive access, one-time passwords)\n- **Safes**: Logical containers for credentials with granular permissions\n- **Platforms**: Configuration profiles defining rotation, verification, and reconciliation\n- **Account Groups**: Link accounts sharing rotation dependencies\n\n### Credential Lifecycle\n1. **Discovery**: Scan infrastructure for privileged accounts\n2. **Onboarding**: Import accounts into vault with platform assignment\n3. **Rotation**: Automated password changes per policy schedule\n4. **Verification**: Periodic validation that vaulted credentials work\n5. **Reconciliation**: Re-sync credentials when vault and target are out of sync\n6. **Decommissioning**: Remove accounts no longer needed\n\n## Workflow\n\n### Step 1: Vault Architecture Design\n1. Deploy primary vault server in secured network segment\n2. Configure vault high availability with DR vault\n3. Harden vault server OS (remove unnecessary services, disable RDP)\n4. Configure firewall rules (only port 1858 from authorized components)\n5. Set up vault backup with encryption\n\n### Step 2: Safe and Policy Configuration\n1. Create safe hierarchy aligned with business units\n2. Define safe members with least-privilege roles:\n   - Safe Admins: manage safe membership\n   - Credential Managers: add\u002Fmodify accounts\n   - Auditors: view audit logs only\n   - Users: retrieve\u002Fuse credentials\n3. Configure Master Policy settings:\n   - Require dual control for credential retrieval\n   - Enable exclusive access (one user per credential at a time)\n   - Set one-time password mode for sensitive accounts\n\n### Step 3: Platform Configuration\n- Windows Domain Admin: Rotate every 24 hours, verify every 4 hours\n- Linux Root: Rotate every 72 hours with SSH key rotation\n- Database Admin (Oracle, SQL Server): Rotate every 24 hours\n- Network Devices: Rotate every 7 days\n- Service Accounts: Rotate on schedule with dependency management\n- Cloud IAM Keys: Rotate every 90 days with dual-key strategy\n\n### Step 4: Privileged Session Management\n1. Deploy PSM servers behind load balancer\n2. Configure session recording (video, keystroke, command logs)\n3. Set up session isolation (users connect through PSM, never directly)\n4. Define connection components for RDP, SSH, databases, web apps\n5. Configure live session monitoring and termination capabilities\n6. Set session recording retention (minimum 1 year for compliance)\n\n### Step 5: Integration and Monitoring\n1. Forward CyberArk audit logs to SIEM (CEF\u002FSyslog format)\n2. Configure PTA for behavioral analytics:\n   - Detect credential theft indicators\n   - Alert on suspicious privileged session activity\n   - Monitor unmanaged privileged account usage\n3. Integrate with ticketing system for access request workflows\n4. Set up alerts for failed rotation, verification failures, policy violations\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| Privileged Access | AC-6(7) | Privileged account controls |\n| Credential Management | IA-5 | Automated credential rotation |\n| Session Recording | AU-14 | Session audit capability |\n| Access Enforcement | AC-3 | Vault-enforced access policies |\n| Separation of Duties | AC-5 | Dual control for sensitive operations |\n\n## Common Pitfalls\n- Not configuring reconciliation accounts leading to lockouts after rotation\n- Setting rotation schedules too aggressive for service accounts with dependencies\n- Failing to test PSM connection components before production deployment\n- Not establishing break-glass procedures for vault unavailability\n- Overlooking network device credential management\n\n## Verification\n- [ ] Vault accessible only from authorized components\n- [ ] Credential rotation succeeds for all onboarded accounts\n- [ ] PSM sessions recorded and searchable\n- [ ] Dual control enforced for sensitive credential checkout\n- [ ] SIEM receives CyberArk audit events\n- [ ] Break-glass procedure tested and documented\n- [ ] DR vault failover tested successfully\n",{"name":5,"tags":49,"author":51,"domain":34,"license":15,"version":52,"mitre_f3":53,"nist_csf":76,"subdomain":81,"description":7,"mitre_attack":82},[25,42,35,27,50,26],"pam","mahipal","1.0",{"tactics":54,"version":57,"techniques":58},[30,55,56],"positioning","resource-development","1.1",[59,63,66,70,73],{"id":60,"name":61,"source":62,"tactic":56},"T1586","Compromise Accounts","attack",{"id":64,"name":65,"source":62,"tactic":30},"T1110","Brute Force",{"id":67,"name":68,"source":69,"tactic":30},"F1033","Insider Access Abuse","f3",{"id":71,"name":72,"source":69,"tactic":55},"F1005.002","Account Manipulation: Add Authorized User",{"id":74,"name":75,"source":69,"tactic":30},"F1006.002","Account Takeover: Exposed Login Credential",[77,78,79,80],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[83,64,84,85,86],"T1078","T1556","T1098","T1003","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-privileged-access-management-with-cyberark",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":98,"prompt":108,"zipAvailable":109},[99,102,105],{"tool":100,"command":101},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-privileged-access-management-with-cyberark",{"tool":103,"command":104},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-privileged-access-management-with-cyberark",{"tool":106,"command":107},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-privileged-access-management-with-cyberark","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-privileged-access-management-with-cyberark\u002FSKILL.md",true,[111,117,122,128,132,136,142],{"path":112,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":115,"sourceHtmlUrl":116},"assets\u002Ftemplate.md","ASSET","资产文件",2510,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-privileged-access-management-with-cyberark\u002Fassets\u002Ftemplate.md",{"path":118,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":120,"sourceHtmlUrl":121},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-privileged-access-management-with-cyberark\u002FLICENSE",{"path":123,"resourceType":124,"resourceTypeDesc":125,"sizeBytes":126,"sourceHtmlUrl":127},"references\u002Fapi-reference.md","REFERENCE","参考文档",4591,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-privileged-access-management-with-cyberark\u002Freferences\u002Fapi-reference.md",{"path":129,"resourceType":124,"resourceTypeDesc":125,"sizeBytes":130,"sourceHtmlUrl":131},"references\u002Fstandards.md",1542,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-privileged-access-management-with-cyberark\u002Freferences\u002Fstandards.md",{"path":133,"resourceType":124,"resourceTypeDesc":125,"sizeBytes":134,"sourceHtmlUrl":135},"references\u002Fworkflows.md",3063,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-privileged-access-management-with-cyberark\u002Freferences\u002Fworkflows.md",{"path":137,"resourceType":138,"resourceTypeDesc":139,"sizeBytes":140,"sourceHtmlUrl":141},"scripts\u002Fagent.py","SCRIPT","脚本",9803,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-privileged-access-management-with-cyberark\u002Fscripts\u002Fagent.py",{"path":143,"resourceType":138,"resourceTypeDesc":139,"sizeBytes":144,"sourceHtmlUrl":145},"scripts\u002Fprocess.py",16859,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-privileged-access-management-with-cyberark\u002Fscripts\u002Fprocess.py",[147,172,196,222,248,275],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":44},"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",[153],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[155,156,157,158,159,34,160,42,41,161,162,163,164,165,166,167,168,169,170,171],"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":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":179,"publishedAt":44},"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",[178],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[180,168,181,182,159,183,34,41,184,185,186,187,188,189,190,191,192,193,194,195],"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":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":206,"publishedAt":44},"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",[202,205],{"categoryNo":203,"categoryName":204,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[190,207,208,209,210,34,40,211,184,212,213,214,215,216,217,31,218,219,220,221],"backup","recovery","validating backup integrity for recovery","testing","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":229,"publishedAt":44},"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",[228],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[230,231,232,34,233,234,235,236,237,238,239,240,241,242,243,244,187,245,246,247],"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":249,"name":250,"nameZh":6,"description":251,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":252,"categories":253,"keywords":255,"publishedAt":44},"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",[254],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[256,257,258,34,259,260,261,262,263,264,265,266,267,268,269,270,271,272,273,274],"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":276,"name":277,"nameZh":6,"description":278,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":279,"categories":280,"keywords":282,"publishedAt":44},"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",[281],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[159,283,34,284,285,286,287,288,33,289,290,31,291,218,292,293,294,295,296,297],"triaging security incident","siem","file","ioc","soc","NIST-800-61","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]