[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFRMX4K5MDKD3XZS7MCZRG":3,"skill-same:01M6AFRMX4K5MDKD3XZS7MCZRG":120},{"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":26,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6AFRMX4K5MDKD3XZS7MCZRG","performing-docker-bench-security-assessment",null,"Runs Docker Bench for Security, the open-source CIS Docker Benchmark audit script, across host configuration, daemon settings, images, and runtime configuration, then interprets pass\u002Ffail\u002Fwarn output and remediates the common failures. Use when auditing Docker hosts for CIS compliance, scheduling recurring container assessments, or validating runtime hardening controls after a change. Keywords: docker-bench-security, CIS Docker Benchmark, audit script, pass fail warn, host configuration, remediation. Do not use for applying the daemon hardening itself - use hardening-docker-daemon-configuration.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35990,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-docker-bench-security-assessment\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"docker","security","assessment","performing docker bench security assessment","containers","cybersecurity","change","pr","benchmark","audit","compliance","container-security","cis-benchmark","hardening","remediation","2026-11-10 10:12:30",false,"---\nname: performing-docker-bench-security-assessment\ndescription: >-\n  Runs Docker Bench for Security, the open-source CIS Docker Benchmark audit script, across\n  host configuration, daemon settings, images, and runtime configuration, then interprets\n  pass\u002Ffail\u002Fwarn output and remediates the common failures. Use when auditing Docker hosts for\n  CIS compliance, scheduling recurring container assessments, or validating runtime hardening\n  controls after a change. Keywords: docker-bench-security, CIS Docker Benchmark, audit\n  script, pass fail warn, host configuration, remediation. Do not use for applying the daemon\n  hardening itself - use hardening-docker-daemon-configuration.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- containers\n- docker\n- security\n- CIS-benchmark\n- assessment\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.IR-01\n- ID.AM-08\n- DE.CM-01\nmitre_attack:\n- T1610\n- T1611\n- T1609\n- T1525\n---\n# Performing Docker Bench Security Assessment\n\n## Overview\n\nDocker Bench for Security is an open-source script that checks dozens of common best practices around deploying Docker containers in production. Based on the CIS Docker Benchmark, it audits host configuration, Docker daemon settings, container images, runtime configurations, and security operations to generate a compliance report with pass\u002Ffail\u002Fwarn results.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing docker bench security assessment\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Docker Engine installed and running\n- Root or sudo access on Docker host\n- Docker Bench Security script or container image\n\n## Workflow\n\n### Step 1: Run Docker Bench Security\n\n```bash\n# Run as a container (recommended)\ndocker run --rm --net host --pid host --userns host --cap-add audit_control \\\n  -e DOCKER_CONTENT_TRUST=$DOCKER_CONTENT_TRUST \\\n  -v \u002Fetc:\u002Fetc:ro \\\n  -v \u002Fusr\u002Fbin\u002Fcontainerd:\u002Fusr\u002Fbin\u002Fcontainerd:ro \\\n  -v \u002Fusr\u002Fbin\u002Frunc:\u002Fusr\u002Fbin\u002Frunc:ro \\\n  -v \u002Fusr\u002Flib\u002Fsystemd:\u002Fusr\u002Flib\u002Fsystemd:ro \\\n  -v \u002Fvar\u002Flib:\u002Fvar\u002Flib:ro \\\n  -v \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro \\\n  --label docker_bench_security \\\n  docker\u002Fdocker-bench-security\n\n# Run with JSON output\ndocker run --rm --net host --pid host --userns host --cap-add audit_control \\\n  -v \u002Fetc:\u002Fetc:ro \\\n  -v \u002Fvar\u002Flib:\u002Fvar\u002Flib:ro \\\n  -v \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro \\\n  docker\u002Fdocker-bench-security -l \u002Fdev\u002Fstdout 2>\u002Fdev\u002Fnull | tee docker-bench-results.json\n\n# Run specific sections only\ndocker run --rm --net host --pid host --userns host \\\n  -v \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro \\\n  docker\u002Fdocker-bench-security -c container_images,container_runtime\n```\n\n### Step 2: Interpret Results\n\n```\n[INFO] 1 - Host Configuration\n[PASS] 1.1.1 - Ensure a separate partition for containers has been created\n[WARN] 1.1.2 - Ensure only trusted users are allowed to control Docker daemon\n[PASS] 1.1.3 - Ensure auditing is configured for the Docker daemon\n\n[INFO] 2 - Docker daemon configuration\n[FAIL] 2.1 - Run the Docker daemon as a non-root user\n[PASS] 2.2 - Ensure network traffic is restricted between containers on the default bridge\n```\n\n### Step 3: Remediate Common Failures\n\n```bash\n# Fix 2.2: Restrict inter-container communication\necho '{\"icc\": false}' | sudo tee \u002Fetc\u002Fdocker\u002Fdaemon.json\n\n# Fix 2.17: Restrict containers from acquiring new privileges\necho '{\"no-new-privileges\": true}' | sudo tee -a \u002Fetc\u002Fdocker\u002Fdaemon.json\n\n# Fix 5.3: Restrict Linux kernel capabilities\n# Use --cap-drop ALL in docker run commands\n\n# Fix 5.12: Mount container's root filesystem as read only\n# Use --read-only flag in docker run commands\n\n# Restart Docker daemon after configuration changes\nsudo systemctl restart docker\n```\n\n### Step 4: Automate Scheduled Assessments\n\n```yaml\n# docker-compose for scheduled assessment\nversion: '3.8'\nservices:\n  bench-security:\n    image: docker\u002Fdocker-bench-security\n    network_mode: host\n    pid: host\n    userns_mode: host\n    cap_add:\n      - audit_control\n    volumes:\n      - \u002Fetc:\u002Fetc:ro\n      - \u002Fvar\u002Flib:\u002Fvar\u002Flib:ro\n      - \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro\n      - .\u002Fresults:\u002Fresults\n    command: -l \u002Fresults\u002Fbench-$(date +%Y%m%d).log\n    deploy:\n      restart_policy:\n        condition: none\n```\n\n## Validation Commands\n\n```bash\n# Verify remediation\ndocker run --rm docker\u002Fdocker-bench-security 2>&1 | grep -E \"(PASS|FAIL|WARN)\" | sort | uniq -c\n\n# Count results by type\ndocker run --rm docker\u002Fdocker-bench-security 2>&1 | grep -c \"PASS\"\ndocker run --rm docker\u002Fdocker-bench-security 2>&1 | grep -c \"FAIL\"\ndocker run --rm docker\u002Fdocker-bench-security 2>&1 | grep -c \"WARN\"\n```\n\n## References\n\n- [Docker Bench Security](https:\u002F\u002Fgithub.com\u002Fdocker\u002Fdocker-bench-security)\n- [CIS Docker Benchmark](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fdocker)\n- [Docker Security Best Practices](https:\u002F\u002Fdocs.docker.com\u002Fengine\u002Fsecurity\u002F)\n","# Performing Docker Bench Security Assessment\n\n## Overview\n\nDocker Bench for Security is an open-source script that checks dozens of common best practices around deploying Docker containers in production. Based on the CIS Docker Benchmark, it audits host configuration, Docker daemon settings, container images, runtime configurations, and security operations to generate a compliance report with pass\u002Ffail\u002Fwarn results.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing docker bench security assessment\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Docker Engine installed and running\n- Root or sudo access on Docker host\n- Docker Bench Security script or container image\n\n## Workflow\n\n### Step 1: Run Docker Bench Security\n\n```bash\n# Run as a container (recommended)\ndocker run --rm --net host --pid host --userns host --cap-add audit_control \\\n  -e DOCKER_CONTENT_TRUST=$DOCKER_CONTENT_TRUST \\\n  -v \u002Fetc:\u002Fetc:ro \\\n  -v \u002Fusr\u002Fbin\u002Fcontainerd:\u002Fusr\u002Fbin\u002Fcontainerd:ro \\\n  -v \u002Fusr\u002Fbin\u002Frunc:\u002Fusr\u002Fbin\u002Frunc:ro \\\n  -v \u002Fusr\u002Flib\u002Fsystemd:\u002Fusr\u002Flib\u002Fsystemd:ro \\\n  -v \u002Fvar\u002Flib:\u002Fvar\u002Flib:ro \\\n  -v \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro \\\n  --label docker_bench_security \\\n  docker\u002Fdocker-bench-security\n\n# Run with JSON output\ndocker run --rm --net host --pid host --userns host --cap-add audit_control \\\n  -v \u002Fetc:\u002Fetc:ro \\\n  -v \u002Fvar\u002Flib:\u002Fvar\u002Flib:ro \\\n  -v \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro \\\n  docker\u002Fdocker-bench-security -l \u002Fdev\u002Fstdout 2>\u002Fdev\u002Fnull | tee docker-bench-results.json\n\n# Run specific sections only\ndocker run --rm --net host --pid host --userns host \\\n  -v \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro \\\n  docker\u002Fdocker-bench-security -c container_images,container_runtime\n```\n\n### Step 2: Interpret Results\n\n```\n[INFO] 1 - Host Configuration\n[PASS] 1.1.1 - Ensure a separate partition for containers has been created\n[WARN] 1.1.2 - Ensure only trusted users are allowed to control Docker daemon\n[PASS] 1.1.3 - Ensure auditing is configured for the Docker daemon\n\n[INFO] 2 - Docker daemon configuration\n[FAIL] 2.1 - Run the Docker daemon as a non-root user\n[PASS] 2.2 - Ensure network traffic is restricted between containers on the default bridge\n```\n\n### Step 3: Remediate Common Failures\n\n```bash\n# Fix 2.2: Restrict inter-container communication\necho '{\"icc\": false}' | sudo tee \u002Fetc\u002Fdocker\u002Fdaemon.json\n\n# Fix 2.17: Restrict containers from acquiring new privileges\necho '{\"no-new-privileges\": true}' | sudo tee -a \u002Fetc\u002Fdocker\u002Fdaemon.json\n\n# Fix 5.3: Restrict Linux kernel capabilities\n# Use --cap-drop ALL in docker run commands\n\n# Fix 5.12: Mount container's root filesystem as read only\n# Use --read-only flag in docker run commands\n\n# Restart Docker daemon after configuration changes\nsudo systemctl restart docker\n```\n\n### Step 4: Automate Scheduled Assessments\n\n```yaml\n# docker-compose for scheduled assessment\nversion: '3.8'\nservices:\n  bench-security:\n    image: docker\u002Fdocker-bench-security\n    network_mode: host\n    pid: host\n    userns_mode: host\n    cap_add:\n      - audit_control\n    volumes:\n      - \u002Fetc:\u002Fetc:ro\n      - \u002Fvar\u002Flib:\u002Fvar\u002Flib:ro\n      - \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro\n      - .\u002Fresults:\u002Fresults\n    command: -l \u002Fresults\u002Fbench-$(date +%Y%m%d).log\n    deploy:\n      restart_policy:\n        condition: none\n```\n\n## Validation Commands\n\n```bash\n# Verify remediation\ndocker run --rm docker\u002Fdocker-bench-security 2>&1 | grep -E \"(PASS|FAIL|WARN)\" | sort | uniq -c\n\n# Count results by type\ndocker run --rm docker\u002Fdocker-bench-security 2>&1 | grep -c \"PASS\"\ndocker run --rm docker\u002Fdocker-bench-security 2>&1 | grep -c \"FAIL\"\ndocker run --rm docker\u002Fdocker-bench-security 2>&1 | grep -c \"WARN\"\n```\n\n## References\n\n- [Docker Bench Security](https:\u002F\u002Fgithub.com\u002Fdocker\u002Fdocker-bench-security)\n- [CIS Docker Benchmark](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fdocker)\n- [Docker Security Best Practices](https:\u002F\u002Fdocs.docker.com\u002Fengine\u002Fsecurity\u002F)\n",{"name":5,"tags":47,"author":49,"domain":32,"license":15,"version":50,"nist_csf":51,"subdomain":38,"description":7,"mitre_attack":56},[31,27,28,48,29],"CIS-benchmark","mahipal","1.0",[52,53,54,55],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01",[57,58,59,60],"T1610","T1611","T1609","T1525","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fperforming-docker-bench-security-assessment",4395,"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":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-docker-bench-security-assessment",{"tool":77,"command":78},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-docker-bench-security-assessment",{"tool":80,"command":81},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-docker-bench-security-assessment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-docker-bench-security-assessment\u002FSKILL.md",true,[85,91,96,102,106,110,116],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Ftemplate.md","ASSET","资产文件",431,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-docker-bench-security-assessment\u002Fassets\u002Ftemplate.md",{"path":92,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-docker-bench-security-assessment\u002FLICENSE",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fapi-reference.md","REFERENCE","参考文档",1148,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-docker-bench-security-assessment\u002Freferences\u002Fapi-reference.md",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fstandards.md",736,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-docker-bench-security-assessment\u002Freferences\u002Fstandards.md",{"path":107,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fworkflows.md",724,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-docker-bench-security-assessment\u002Freferences\u002Fworkflows.md",{"path":111,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":114,"sourceHtmlUrl":115},"scripts\u002Fagent.py","SCRIPT","脚本",5847,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-docker-bench-security-assessment\u002Fscripts\u002Fagent.py",{"path":117,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fprocess.py",1855,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-docker-bench-security-assessment\u002Fscripts\u002Fprocess.py",[121,146,170,197,223,249],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":128,"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",[127],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[129,130,131,132,28,32,133,134,34,135,136,137,138,139,140,141,142,143,144,145],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"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",[152],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[154,142,155,156,28,157,32,34,158,159,160,161,162,163,164,165,166,167,168,169],"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":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":180,"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",[176,179],{"categoryNo":177,"categoryName":178,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[164,181,182,183,184,32,185,186,158,37,187,188,189,190,191,192,193,194,195,196],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":204,"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",[203],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[205,206,207,32,208,209,210,211,212,213,214,215,216,217,218,219,161,220,221,222],"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":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":230,"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",[229],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[231,232,233,32,234,235,236,237,238,239,240,241,242,41,243,244,245,246,247,248],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":250,"name":251,"nameZh":6,"description":252,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":253,"categories":254,"keywords":256,"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",[255],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[28,257,32,258,259,260,261,262,263,264,265,192,266,193,267,268,269,270,271,272],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]