[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFW0T53THNSCN57SFRVGK1":3,"skill-same:01M6AFW0T53THNSCN57SFRVGK1":131},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":71,"repositoryHtmlUrl":72,"repositoryHomepageUrl":73,"ownerHtmlUrl":74,"ownerBlogUrl":75,"ownerDescription":76,"updatedAt":77,"install":78,"resources":91},"01M6AFW0T53THNSCN57SFRVGK1","performing-kubernetes-cis-benchmark-with-kube-bench",null,"Turns kube-bench output into a finished CIS Kubernetes Benchmark audit: interpreting PASS\u002FFAIL\u002FWARN per control, judging which failures are genuine on a managed cluster, writing remediation, and packaging evidence for SOC 2 or PCI DSS. Use when conducting a scheduled compliance audit, triaging kube-bench results, deciding which controls are not applicable on EKS, GKE, or AKS, or producing hardening evidence for an auditor. Keywords: CIS Kubernetes Benchmark, control plane, remediation, compliance evidence, SOC 2, PCI DSS, managed cluster exception. Do not use for installing and running the tool - use benchmarking-kubernetes-with-kube-bench.","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\u002Fperforming-kubernetes-cis-benchmark-with-kube-bench\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"kubernetes","performing kubernetes cis benchmark with kube bench","benchmark","container-security","writing","aquasecurity","remediation","cis-benchmark","kube-bench","aks","gke","eks","cybersecurity","soc","compliance","audit","control plane","security","pr","benchmarking","2026-11-10 10:12:30",false,"---\nname: performing-kubernetes-cis-benchmark-with-kube-bench\ndescription: >-\n  Turns kube-bench output into a finished CIS Kubernetes Benchmark audit: interpreting\n  PASS\u002FFAIL\u002FWARN per control, judging which failures are genuine on a managed cluster, writing\n  remediation, and packaging evidence for SOC 2 or PCI DSS. Use when conducting a scheduled\n  compliance audit, triaging kube-bench results, deciding which controls are not applicable on\n  EKS, GKE, or AKS, or producing hardening evidence for an auditor. Keywords: CIS Kubernetes\n  Benchmark, control plane, remediation, compliance evidence, SOC 2, PCI DSS, managed cluster\n  exception. Do not use for installing and running the tool - use\n  benchmarking-kubernetes-with-kube-bench.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- kube-bench\n- cis-benchmark\n- kubernetes\n- compliance\n- hardening\n- aquasecurity\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\n# Performing Kubernetes CIS Benchmark with kube-bench\n\n## Overview\n\nkube-bench is an open-source Go tool by Aqua Security that runs the CIS Kubernetes Benchmark checks. It verifies control plane, etcd, worker node, and policy configurations against security best practices, producing actionable pass\u002Ffail\u002Fwarn reports.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing kubernetes cis benchmark with kube bench\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- Kubernetes cluster (v1.24+)\n- kubectl with cluster-admin access\n- Node access for direct runs or privileged pod access\n\n## Installation\n\n```bash\n# Binary installation\ncurl -L https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-bench\u002Freleases\u002Fdownload\u002Fv0.7.3\u002Fkube-bench_0.7.3_linux_amd64.tar.gz | tar xz\nsudo mv kube-bench \u002Fusr\u002Flocal\u002Fbin\u002F\n\n# Run as Kubernetes Job\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob.yaml\nkubectl logs job\u002Fkube-bench\n\n# Run as a pod with host access\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob-master.yaml\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob-node.yaml\n```\n\n## Running Benchmarks\n\n### Full Benchmark\n\n```bash\n# Run all checks (auto-detects node type)\nkube-bench run\n\n# Run with JSON output\nkube-bench run --json > kube-bench-results.json\n\n# Run with JUnit output for CI\nkube-bench run --junit > kube-bench-results.xml\n```\n\n### Component-Specific Checks\n\n```bash\n# Control plane (master) checks\nkube-bench run --targets master\n\n# Worker node checks\nkube-bench run --targets node\n\n# etcd checks\nkube-bench run --targets etcd\n\n# Policies checks\nkube-bench run --targets policies\n\n# Control plane + etcd\nkube-bench run --targets master,etcd\n```\n\n### Managed Kubernetes\n\n```bash\n# Amazon EKS\nkube-bench run --benchmark eks-1.2.0\n\n# Google GKE\nkube-bench run --benchmark gke-1.4.0\n\n# Azure AKS\nkube-bench run --benchmark aks-1.0\n\n# Red Hat OpenShift\nkube-bench run --benchmark rh-1.0\n```\n\n### Filtering Results\n\n```bash\n# Show only failures\nkube-bench run --targets master | grep \"\\[FAIL\\]\"\n\n# Run specific check\nkube-bench run --check 1.2.1\n\n# Run check group\nkube-bench run --group 1.2\n```\n\n## CIS Benchmark Sections\n\n| Section | Component | Key Checks |\n|---------|-----------|------------|\n| 1.1 | Control Plane - API Server | Anonymous auth, RBAC, audit logging |\n| 1.2 | Control Plane - API Server | Admission controllers, encryption |\n| 1.3 | Control Plane - Controller Manager | Service account tokens, bind address |\n| 1.4 | Control Plane - Scheduler | Profiling, bind address |\n| 2.1 | etcd | Client cert auth, peer encryption |\n| 3.1 | Control Plane - Authentication | OIDC, client certs |\n| 4.1 | Worker - kubelet | Anonymous auth, authorization |\n| 4.2 | Worker - kubelet | TLS, read-only port |\n| 5.1 | Policies - RBAC | Cluster-admin usage, service accounts |\n| 5.2 | Policies - Pod Security | Privileged, host namespaces |\n| 5.3 | Policies - Network | Network policies per namespace |\n| 5.7 | Policies - General | Secrets, security context |\n\n## Output Example\n\n```\n[INFO] 1 Control Plane Security Configuration\n[INFO] 1.1 Control Plane Node Configuration Files\n[PASS] 1.1.1 Ensure that the API server pod specification file permissions are set to 600\n[PASS] 1.1.2 Ensure that the API server pod specification file ownership is set to root:root\n[FAIL] 1.1.3 Ensure that the controller manager pod specification file permissions are set to 600\n[WARN] 1.1.4 Ensure that the scheduler pod specification file permissions are set to 600\n\n== Summary ==\n45 checks PASS\n12 checks FAIL\n8 checks WARN\n0 checks INFO\n```\n\n## CI\u002FCD Integration\n\n### GitHub Actions\n\n```yaml\nname: CIS Benchmark\non:\n  schedule:\n    - cron: '0 6 * * 1'\n\njobs:\n  kube-bench:\n    runs-on: ubuntu-latest\n    steps:\n      - name: Configure kubectl\n        uses: azure\u002Fsetup-kubectl@v3\n\n      - name: Run kube-bench\n        run: |\n          kubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob.yaml\n          kubectl wait --for=condition=complete job\u002Fkube-bench --timeout=120s\n          kubectl logs job\u002Fkube-bench > kube-bench-report.txt\n\n      - name: Check for failures\n        run: |\n          FAILS=$(grep -c \"\\[FAIL\\]\" kube-bench-report.txt || true)\n          echo \"Failed checks: $FAILS\"\n          if [ \"$FAILS\" -gt 0 ]; then\n            echo \"::warning::$FAILS CIS benchmark checks failed\"\n          fi\n\n      - name: Upload report\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: kube-bench-report\n          path: kube-bench-report.txt\n```\n\n## Remediation Examples\n\n### 1.2.1 - Ensure --anonymous-auth is set to false\n```yaml\n# \u002Fetc\u002Fkubernetes\u002Fmanifests\u002Fkube-apiserver.yaml\nspec:\n  containers:\n  - command:\n    - kube-apiserver\n    - --anonymous-auth=false\n```\n\n### 4.2.1 - Ensure --anonymous-auth is set to false on kubelet\n```yaml\n# \u002Fvar\u002Flib\u002Fkubelet\u002Fconfig.yaml\nauthentication:\n  anonymous:\n    enabled: false\n  webhook:\n    enabled: true\n```\n\n### 5.2.1 - Minimize wildcard RBAC\n```bash\n# Find roles with wildcard permissions\nkubectl get clusterroles -o json | jq '.items[] | select(.rules[].resources[] == \"*\") | .metadata.name'\n```\n\n## Best Practices\n\n1. **Run kube-bench before and after** cluster provisioning\n2. **Schedule weekly scans** via CronJob for drift detection\n3. **Export JSON** for SIEM\u002Fcompliance reporting\n4. **Fix FAIL items first**, then address WARN items\n5. **Use benchmark profiles** matching your Kubernetes distribution\n6. **Track score over time** to measure security posture improvement\n7. **Combine with admission controllers** to prevent drift\n","# Performing Kubernetes CIS Benchmark with kube-bench\n\n## Overview\n\nkube-bench is an open-source Go tool by Aqua Security that runs the CIS Kubernetes Benchmark checks. It verifies control plane, etcd, worker node, and policy configurations against security best practices, producing actionable pass\u002Ffail\u002Fwarn reports.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing kubernetes cis benchmark with kube bench\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- Kubernetes cluster (v1.24+)\n- kubectl with cluster-admin access\n- Node access for direct runs or privileged pod access\n\n## Installation\n\n```bash\n# Binary installation\ncurl -L https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-bench\u002Freleases\u002Fdownload\u002Fv0.7.3\u002Fkube-bench_0.7.3_linux_amd64.tar.gz | tar xz\nsudo mv kube-bench \u002Fusr\u002Flocal\u002Fbin\u002F\n\n# Run as Kubernetes Job\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob.yaml\nkubectl logs job\u002Fkube-bench\n\n# Run as a pod with host access\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob-master.yaml\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob-node.yaml\n```\n\n## Running Benchmarks\n\n### Full Benchmark\n\n```bash\n# Run all checks (auto-detects node type)\nkube-bench run\n\n# Run with JSON output\nkube-bench run --json > kube-bench-results.json\n\n# Run with JUnit output for CI\nkube-bench run --junit > kube-bench-results.xml\n```\n\n### Component-Specific Checks\n\n```bash\n# Control plane (master) checks\nkube-bench run --targets master\n\n# Worker node checks\nkube-bench run --targets node\n\n# etcd checks\nkube-bench run --targets etcd\n\n# Policies checks\nkube-bench run --targets policies\n\n# Control plane + etcd\nkube-bench run --targets master,etcd\n```\n\n### Managed Kubernetes\n\n```bash\n# Amazon EKS\nkube-bench run --benchmark eks-1.2.0\n\n# Google GKE\nkube-bench run --benchmark gke-1.4.0\n\n# Azure AKS\nkube-bench run --benchmark aks-1.0\n\n# Red Hat OpenShift\nkube-bench run --benchmark rh-1.0\n```\n\n### Filtering Results\n\n```bash\n# Show only failures\nkube-bench run --targets master | grep \"\\[FAIL\\]\"\n\n# Run specific check\nkube-bench run --check 1.2.1\n\n# Run check group\nkube-bench run --group 1.2\n```\n\n## CIS Benchmark Sections\n\n| Section | Component | Key Checks |\n|---------|-----------|------------|\n| 1.1 | Control Plane - API Server | Anonymous auth, RBAC, audit logging |\n| 1.2 | Control Plane - API Server | Admission controllers, encryption |\n| 1.3 | Control Plane - Controller Manager | Service account tokens, bind address |\n| 1.4 | Control Plane - Scheduler | Profiling, bind address |\n| 2.1 | etcd | Client cert auth, peer encryption |\n| 3.1 | Control Plane - Authentication | OIDC, client certs |\n| 4.1 | Worker - kubelet | Anonymous auth, authorization |\n| 4.2 | Worker - kubelet | TLS, read-only port |\n| 5.1 | Policies - RBAC | Cluster-admin usage, service accounts |\n| 5.2 | Policies - Pod Security | Privileged, host namespaces |\n| 5.3 | Policies - Network | Network policies per namespace |\n| 5.7 | Policies - General | Secrets, security context |\n\n## Output Example\n\n```\n[INFO] 1 Control Plane Security Configuration\n[INFO] 1.1 Control Plane Node Configuration Files\n[PASS] 1.1.1 Ensure that the API server pod specification file permissions are set to 600\n[PASS] 1.1.2 Ensure that the API server pod specification file ownership is set to root:root\n[FAIL] 1.1.3 Ensure that the controller manager pod specification file permissions are set to 600\n[WARN] 1.1.4 Ensure that the scheduler pod specification file permissions are set to 600\n\n== Summary ==\n45 checks PASS\n12 checks FAIL\n8 checks WARN\n0 checks INFO\n```\n\n## CI\u002FCD Integration\n\n### GitHub Actions\n\n```yaml\nname: CIS Benchmark\non:\n  schedule:\n    - cron: '0 6 * * 1'\n\njobs:\n  kube-bench:\n    runs-on: ubuntu-latest\n    steps:\n      - name: Configure kubectl\n        uses: azure\u002Fsetup-kubectl@v3\n\n      - name: Run kube-bench\n        run: |\n          kubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob.yaml\n          kubectl wait --for=condition=complete job\u002Fkube-bench --timeout=120s\n          kubectl logs job\u002Fkube-bench > kube-bench-report.txt\n\n      - name: Check for failures\n        run: |\n          FAILS=$(grep -c \"\\[FAIL\\]\" kube-bench-report.txt || true)\n          echo \"Failed checks: $FAILS\"\n          if [ \"$FAILS\" -gt 0 ]; then\n            echo \"::warning::$FAILS CIS benchmark checks failed\"\n          fi\n\n      - name: Upload report\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: kube-bench-report\n          path: kube-bench-report.txt\n```\n\n## Remediation Examples\n\n### 1.2.1 - Ensure --anonymous-auth is set to false\n```yaml\n# \u002Fetc\u002Fkubernetes\u002Fmanifests\u002Fkube-apiserver.yaml\nspec:\n  containers:\n  - command:\n    - kube-apiserver\n    - --anonymous-auth=false\n```\n\n### 4.2.1 - Ensure --anonymous-auth is set to false on kubelet\n```yaml\n# \u002Fvar\u002Flib\u002Fkubelet\u002Fconfig.yaml\nauthentication:\n  anonymous:\n    enabled: false\n  webhook:\n    enabled: true\n```\n\n### 5.2.1 - Minimize wildcard RBAC\n```bash\n# Find roles with wildcard permissions\nkubectl get clusterroles -o json | jq '.items[] | select(.rules[].resources[] == \"*\") | .metadata.name'\n```\n\n## Best Practices\n\n1. **Run kube-bench before and after** cluster provisioning\n2. **Schedule weekly scans** via CronJob for drift detection\n3. **Export JSON** for SIEM\u002Fcompliance reporting\n4. **Fix FAIL items first**, then address WARN items\n5. **Use benchmark profiles** matching your Kubernetes distribution\n6. **Track score over time** to measure security posture improvement\n7. **Combine with admission controllers** to prevent drift\n",{"name":5,"tags":54,"author":56,"domain":41,"license":15,"version":57,"nist_csf":58,"subdomain":32,"description":7,"mitre_attack":63},[37,36,29,43,55,34],"hardening","mahipal","1.0",[59,60,61,62],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01",[64,65,66,67],"T1610","T1611","T1609","T1525","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fperforming-kubernetes-cis-benchmark-with-kube-bench",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":79,"prompt":89,"zipAvailable":90},[80,83,86],{"tool":81,"command":82},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-kubernetes-cis-benchmark-with-kube-bench",{"tool":84,"command":85},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-kubernetes-cis-benchmark-with-kube-bench",{"tool":87,"command":88},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-kubernetes-cis-benchmark-with-kube-bench","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-kubernetes-cis-benchmark-with-kube-bench\u002FSKILL.md",true,[92,98,103,109,113,117,123,127],{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"assets\u002Ftemplate.md","ASSET","资产文件",1014,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-kubernetes-cis-benchmark-with-kube-bench\u002Fassets\u002Ftemplate.md",{"path":99,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-kubernetes-cis-benchmark-with-kube-bench\u002FLICENSE",{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fapi-reference.md","REFERENCE","参考文档",1694,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-kubernetes-cis-benchmark-with-kube-bench\u002Freferences\u002Fapi-reference.md",{"path":110,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fstandards.md",1482,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-kubernetes-cis-benchmark-with-kube-bench\u002Freferences\u002Fstandards.md",{"path":114,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fworkflows.md",2036,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-kubernetes-cis-benchmark-with-kube-bench\u002Freferences\u002Fworkflows.md",{"path":118,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002Fagent.py","SCRIPT","脚本",7990,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-kubernetes-cis-benchmark-with-kube-bench\u002Fscripts\u002Fagent.py",{"path":124,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":125,"sourceHtmlUrl":126},"scripts\u002Ffind-base-branch.sh",2593,"https:\u002F\u002Fgithub.com\u002Fasermax\u002Fclaude-plugins\u002Fblob\u002Fmaster\u002Fmahou\u002Fskills\u002Fchangeset\u002Fscripts\u002Ffind-base-branch.sh",{"path":128,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":129,"sourceHtmlUrl":130},"scripts\u002Fprocess.py",6139,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-kubernetes-cis-benchmark-with-kube-bench\u002Fscripts\u002Fprocess.py",[132,159,183,210,236,262],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":141,"publishedAt":49},"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",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[142,143,144,145,46,41,146,147,47,148,149,150,151,152,153,154,155,156,157,158],"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":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":49},"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":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},[167,155,168,169,46,170,41,47,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":49},"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":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},[177,194,195,196,197,41,198,199,171,43,200,201,202,203,204,205,206,207,208,209],"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":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":217,"publishedAt":49},"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",[216],{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},[218,219,220,41,221,222,223,224,225,226,227,228,229,230,231,232,174,233,234,235],"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":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":243,"publishedAt":49},"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",[242],{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},[244,245,246,41,247,248,249,250,251,252,253,254,255,35,256,257,258,259,260,261],"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":263,"name":264,"nameZh":6,"description":265,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":266,"categories":267,"keywords":269,"publishedAt":49},"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",[268],{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},[46,270,41,271,272,273,42,274,275,276,277,205,278,206,279,280,281,282,283,284],"triaging security incident","siem","file","ioc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]