[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF2ECXD63WPTH5VMTPFJWV":3,"skill-same:01M6AF2ECXD63WPTH5VMTPFJWV":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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":74,"commitSha":75,"skillDirectory":76,"forksCount":77,"repositoryHtmlUrl":78,"repositoryHomepageUrl":79,"ownerHtmlUrl":80,"ownerBlogUrl":81,"ownerDescription":82,"updatedAt":83,"install":84,"resources":97},"01M6AF2ECXD63WPTH5VMTPFJWV","implementing-container-image-minimal-base-with-distroless",null,"Reduces container attack surface by building application images on Google distroless base images that ship only the application runtime - no shell, package manager, or OS utilities - using multi-stage build patterns plus debugging and scanning techniques adapted to distroless. Use when hardening container images, cutting attack surface in a container architecture, or answering an assessment finding about bloated base images. Keywords: distroless, multi-stage build, no shell, nonroot tag, debug image, scratch, attack surface. Do not use for scanning an image for known CVEs - use scanning-docker-images-with-trivy.","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-container-image-minimal-base-with-distroless\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"implementing container image minimal base with distroless","image","assessment","t1195","attack-surface","security-hardening","supply-chain","container-security","package","container images","debugging","pr","debug","architecture","package manager","cybersecurity","security","kubernetes","docker","google","2026-11-10 10:12:30",false,"---\nname: implementing-container-image-minimal-base-with-distroless\ndescription: >-\n  Reduces container attack surface by building application images on Google distroless base\n  images that ship only the application runtime - no shell, package manager, or OS utilities -\n  using multi-stage build patterns plus debugging and scanning techniques adapted to\n  distroless. Use when hardening container images, cutting attack surface in a container\n  architecture, or answering an assessment finding about bloated base images. Keywords:\n  distroless, multi-stage build, no shell, nonroot tag, debug image, scratch, attack surface.\n  Do not use for scanning an image for known CVEs - use scanning-docker-images-with-trivy.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- distroless\n- container-images\n- minimal-base\n- attack-surface\n- docker\n- security-hardening\n- supply-chain\n- kubernetes\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- T1195\n---\n\n# Implementing Container Image Minimal Base with Distroless\n\n## Overview\n\nGoogle distroless images contain only your application and its runtime dependencies, without package managers, shells, or other programs found in standard Linux distributions. By eliminating unnecessary OS components, distroless images achieve up to 95% reduction in attack surface compared to traditional base images like ubuntu or debian. Major projects including Kubernetes itself, Knative, and Tekton use distroless images in production. As of 2025, Docker also offers Hardened Images (DHI) as an open-source alternative for minimal container bases.\n\n\n## When to Use\n\n- When deploying or configuring implementing container image minimal base with distroless 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- Docker 20.10+ or compatible container build tool (Buildah, Kaniko)\n- Multi-stage Dockerfile knowledge\n- Application compiled as a static binary or with runtime bundled\n- Container registry for image storage\n\n## Available Distroless Images\n\n| Image | Use Case | Size |\n|-------|----------|------|\n| `gcr.io\u002Fdistroless\u002Fstatic-debian12` | Statically compiled binaries (Go, Rust) | ~2MB |\n| `gcr.io\u002Fdistroless\u002Fbase-debian12` | Dynamically linked binaries needing glibc | ~20MB |\n| `gcr.io\u002Fdistroless\u002Fcc-debian12` | C\u002FC++ applications needing libstdc++ | ~25MB |\n| `gcr.io\u002Fdistroless\u002Fjava21-debian12` | Java 21 applications | ~220MB |\n| `gcr.io\u002Fdistroless\u002Fpython3-debian12` | Python 3 applications | ~50MB |\n| `gcr.io\u002Fdistroless\u002Fnodejs22-debian12` | Node.js 22 applications | ~130MB |\n\n## Multi-Stage Build Patterns\n\n### Go Application\n\n```dockerfile\n# Build stage\nFROM golang:1.22-bookworm AS builder\nWORKDIR \u002Fapp\nCOPY go.mod go.sum .\u002F\nRUN go mod download\nCOPY . .\nRUN CGO_ENABLED=0 GOOS=linux go build -ldflags=\"-s -w\" -o \u002Fserver .\u002Fcmd\u002Fserver\n\n# Runtime stage - static distroless\nFROM gcr.io\u002Fdistroless\u002Fstatic-debian12:nonroot\nCOPY --from=builder \u002Fserver \u002Fserver\nUSER nonroot:nonroot\nENTRYPOINT [\"\u002Fserver\"]\n```\n\n### Java Application\n\n```dockerfile\n# Build stage\nFROM maven:3.9-eclipse-temurin-21 AS builder\nWORKDIR \u002Fapp\nCOPY pom.xml .\nRUN mvn dependency:go-offline\nCOPY src .\u002Fsrc\nRUN mvn package -DskipTests\n\n# Runtime stage - Java distroless\nFROM gcr.io\u002Fdistroless\u002Fjava21-debian12:nonroot\nCOPY --from=builder \u002Fapp\u002Ftarget\u002Fapp.jar \u002Fapp.jar\nUSER nonroot:nonroot\nENTRYPOINT [\"java\", \"-jar\", \"\u002Fapp.jar\"]\n```\n\n### Python Application\n\n```dockerfile\n# Build stage\nFROM python:3.12-bookworm AS builder\nWORKDIR \u002Fapp\nCOPY requirements.txt .\nRUN pip install --no-cache-dir --target=\u002Fdeps -r requirements.txt\nCOPY . .\n\n# Runtime stage - Python distroless\nFROM gcr.io\u002Fdistroless\u002Fpython3-debian12:nonroot\nWORKDIR \u002Fapp\nCOPY --from=builder \u002Fdeps \u002Fdeps\nCOPY --from=builder \u002Fapp \u002Fapp\nENV PYTHONPATH=\u002Fdeps\nUSER nonroot:nonroot\nENTRYPOINT [\"python3\", \"\u002Fapp\u002Fmain.py\"]\n```\n\n### Node.js Application\n\n```dockerfile\n# Build stage\nFROM node:22-bookworm AS builder\nWORKDIR \u002Fapp\nCOPY package*.json .\u002F\nRUN npm ci --production\nCOPY . .\n\n# Runtime stage - Node distroless\nFROM gcr.io\u002Fdistroless\u002Fnodejs22-debian12:nonroot\nWORKDIR \u002Fapp\nCOPY --from=builder \u002Fapp .\nUSER nonroot:nonroot\nCMD [\"server.js\"]\n```\n\n## Security Benefits\n\n### Attack Surface Comparison\n\n| Component | Ubuntu | Alpine | Distroless |\n|-----------|--------|--------|-----------|\n| Shell (bash\u002Fsh) | Yes | Yes | No |\n| Package manager | apt | apk | No |\n| coreutils | Full | BusyBox | No |\n| curl\u002Fwget | Yes | Yes | No |\n| User management | Yes | Yes | No |\n| Known CVEs (typical) | 50-200+ | 5-20 | 0-5 |\n| Image size (base) | ~77MB | ~7MB | ~2-20MB |\n\n### Security Implications\n\n- **No shell**: Attackers cannot exec into containers to run commands\n- **No package manager**: Cannot install additional tools or malware\n- **No coreutils**: No `cat`, `ls`, `find`, `curl` for reconnaissance\n- **Minimal CVEs**: Fewer packages means fewer vulnerabilities to patch\n- **Non-root by default**: `:nonroot` tag runs as UID 65534\n\n## Debugging Distroless Containers\n\nSince distroless has no shell, use these techniques for debugging:\n\n### Debug Image Variant\n\n```dockerfile\n# Use debug variant in non-production environments only\nFROM gcr.io\u002Fdistroless\u002Fbase-debian12:debug\n# Includes busybox shell at \u002Fbusybox\u002Fsh\n```\n\n```bash\n# Exec into debug variant\nkubectl exec -it pod-name -- \u002Fbusybox\u002Fsh\n```\n\n### Ephemeral Debug Containers (Kubernetes 1.25+)\n\n```bash\n# Attach a debug container with full tooling\nkubectl debug -it pod-name --image=busybox:1.36 --target=app-container\n```\n\n### Crane\u002FDive for Image Inspection\n\n```bash\n# Inspect image layers without running\ncrane export gcr.io\u002Fdistroless\u002Fstatic-debian12 - | tar -tf - | head -50\n\n# Analyze image layers\ndive gcr.io\u002Fdistroless\u002Fstatic-debian12\n```\n\n## Image Scanning Results\n\nTypical vulnerability comparison using Trivy:\n\n```bash\n# Scan Ubuntu-based image\ntrivy image myapp:ubuntu\n# Result: 47 vulnerabilities (3 CRITICAL, 12 HIGH)\n\n# Scan Distroless-based image\ntrivy image myapp:distroless\n# Result: 2 vulnerabilities (0 CRITICAL, 0 HIGH)\n```\n\n## References\n\n- [GoogleContainerTools\u002Fdistroless GitHub](https:\u002F\u002Fgithub.com\u002FGoogleContainerTools\u002Fdistroless)\n- [Distroless Images - Docker Documentation](https:\u002F\u002Fdocs.docker.com\u002Fdhi\u002Fcore-concepts\u002Fdistroless\u002F)\n- [Alpine, Distroless, or Scratch? - Google Cloud](https:\u002F\u002Fmedium.com\u002Fgoogle-cloud\u002Falpine-distroless-or-scratch-caac35250e0b)\n- [Docker Hardened Images](https:\u002F\u002Fwww.infoq.com\u002Fnews\u002F2025\u002F12\u002Fdocker-hardened-images\u002F)\n","# Implementing Container Image Minimal Base with Distroless\n\n## Overview\n\nGoogle distroless images contain only your application and its runtime dependencies, without package managers, shells, or other programs found in standard Linux distributions. By eliminating unnecessary OS components, distroless images achieve up to 95% reduction in attack surface compared to traditional base images like ubuntu or debian. Major projects including Kubernetes itself, Knative, and Tekton use distroless images in production. As of 2025, Docker also offers Hardened Images (DHI) as an open-source alternative for minimal container bases.\n\n\n## When to Use\n\n- When deploying or configuring implementing container image minimal base with distroless 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- Docker 20.10+ or compatible container build tool (Buildah, Kaniko)\n- Multi-stage Dockerfile knowledge\n- Application compiled as a static binary or with runtime bundled\n- Container registry for image storage\n\n## Available Distroless Images\n\n| Image | Use Case | Size |\n|-------|----------|------|\n| `gcr.io\u002Fdistroless\u002Fstatic-debian12` | Statically compiled binaries (Go, Rust) | ~2MB |\n| `gcr.io\u002Fdistroless\u002Fbase-debian12` | Dynamically linked binaries needing glibc | ~20MB |\n| `gcr.io\u002Fdistroless\u002Fcc-debian12` | C\u002FC++ applications needing libstdc++ | ~25MB |\n| `gcr.io\u002Fdistroless\u002Fjava21-debian12` | Java 21 applications | ~220MB |\n| `gcr.io\u002Fdistroless\u002Fpython3-debian12` | Python 3 applications | ~50MB |\n| `gcr.io\u002Fdistroless\u002Fnodejs22-debian12` | Node.js 22 applications | ~130MB |\n\n## Multi-Stage Build Patterns\n\n### Go Application\n\n```dockerfile\n# Build stage\nFROM golang:1.22-bookworm AS builder\nWORKDIR \u002Fapp\nCOPY go.mod go.sum .\u002F\nRUN go mod download\nCOPY . .\nRUN CGO_ENABLED=0 GOOS=linux go build -ldflags=\"-s -w\" -o \u002Fserver .\u002Fcmd\u002Fserver\n\n# Runtime stage - static distroless\nFROM gcr.io\u002Fdistroless\u002Fstatic-debian12:nonroot\nCOPY --from=builder \u002Fserver \u002Fserver\nUSER nonroot:nonroot\nENTRYPOINT [\"\u002Fserver\"]\n```\n\n### Java Application\n\n```dockerfile\n# Build stage\nFROM maven:3.9-eclipse-temurin-21 AS builder\nWORKDIR \u002Fapp\nCOPY pom.xml .\nRUN mvn dependency:go-offline\nCOPY src .\u002Fsrc\nRUN mvn package -DskipTests\n\n# Runtime stage - Java distroless\nFROM gcr.io\u002Fdistroless\u002Fjava21-debian12:nonroot\nCOPY --from=builder \u002Fapp\u002Ftarget\u002Fapp.jar \u002Fapp.jar\nUSER nonroot:nonroot\nENTRYPOINT [\"java\", \"-jar\", \"\u002Fapp.jar\"]\n```\n\n### Python Application\n\n```dockerfile\n# Build stage\nFROM python:3.12-bookworm AS builder\nWORKDIR \u002Fapp\nCOPY requirements.txt .\nRUN pip install --no-cache-dir --target=\u002Fdeps -r requirements.txt\nCOPY . .\n\n# Runtime stage - Python distroless\nFROM gcr.io\u002Fdistroless\u002Fpython3-debian12:nonroot\nWORKDIR \u002Fapp\nCOPY --from=builder \u002Fdeps \u002Fdeps\nCOPY --from=builder \u002Fapp \u002Fapp\nENV PYTHONPATH=\u002Fdeps\nUSER nonroot:nonroot\nENTRYPOINT [\"python3\", \"\u002Fapp\u002Fmain.py\"]\n```\n\n### Node.js Application\n\n```dockerfile\n# Build stage\nFROM node:22-bookworm AS builder\nWORKDIR \u002Fapp\nCOPY package*.json .\u002F\nRUN npm ci --production\nCOPY . .\n\n# Runtime stage - Node distroless\nFROM gcr.io\u002Fdistroless\u002Fnodejs22-debian12:nonroot\nWORKDIR \u002Fapp\nCOPY --from=builder \u002Fapp .\nUSER nonroot:nonroot\nCMD [\"server.js\"]\n```\n\n## Security Benefits\n\n### Attack Surface Comparison\n\n| Component | Ubuntu | Alpine | Distroless |\n|-----------|--------|--------|-----------|\n| Shell (bash\u002Fsh) | Yes | Yes | No |\n| Package manager | apt | apk | No |\n| coreutils | Full | BusyBox | No |\n| curl\u002Fwget | Yes | Yes | No |\n| User management | Yes | Yes | No |\n| Known CVEs (typical) | 50-200+ | 5-20 | 0-5 |\n| Image size (base) | ~77MB | ~7MB | ~2-20MB |\n\n### Security Implications\n\n- **No shell**: Attackers cannot exec into containers to run commands\n- **No package manager**: Cannot install additional tools or malware\n- **No coreutils**: No `cat`, `ls`, `find`, `curl` for reconnaissance\n- **Minimal CVEs**: Fewer packages means fewer vulnerabilities to patch\n- **Non-root by default**: `:nonroot` tag runs as UID 65534\n\n## Debugging Distroless Containers\n\nSince distroless has no shell, use these techniques for debugging:\n\n### Debug Image Variant\n\n```dockerfile\n# Use debug variant in non-production environments only\nFROM gcr.io\u002Fdistroless\u002Fbase-debian12:debug\n# Includes busybox shell at \u002Fbusybox\u002Fsh\n```\n\n```bash\n# Exec into debug variant\nkubectl exec -it pod-name -- \u002Fbusybox\u002Fsh\n```\n\n### Ephemeral Debug Containers (Kubernetes 1.25+)\n\n```bash\n# Attach a debug container with full tooling\nkubectl debug -it pod-name --image=busybox:1.36 --target=app-container\n```\n\n### Crane\u002FDive for Image Inspection\n\n```bash\n# Inspect image layers without running\ncrane export gcr.io\u002Fdistroless\u002Fstatic-debian12 - | tar -tf - | head -50\n\n# Analyze image layers\ndive gcr.io\u002Fdistroless\u002Fstatic-debian12\n```\n\n## Image Scanning Results\n\nTypical vulnerability comparison using Trivy:\n\n```bash\n# Scan Ubuntu-based image\ntrivy image myapp:ubuntu\n# Result: 47 vulnerabilities (3 CRITICAL, 12 HIGH)\n\n# Scan Distroless-based image\ntrivy image myapp:distroless\n# Result: 2 vulnerabilities (0 CRITICAL, 0 HIGH)\n```\n\n## References\n\n- [GoogleContainerTools\u002Fdistroless GitHub](https:\u002F\u002Fgithub.com\u002FGoogleContainerTools\u002Fdistroless)\n- [Distroless Images - Docker Documentation](https:\u002F\u002Fdocs.docker.com\u002Fdhi\u002Fcore-concepts\u002Fdistroless\u002F)\n- [Alpine, Distroless, or Scratch? - Google Cloud](https:\u002F\u002Fmedium.com\u002Fgoogle-cloud\u002Falpine-distroless-or-scratch-caac35250e0b)\n- [Docker Hardened Images](https:\u002F\u002Fwww.infoq.com\u002Fnews\u002F2025\u002F12\u002Fdocker-hardened-images\u002F)\n",{"name":5,"tags":57,"author":61,"domain":47,"license":15,"version":62,"nist_csf":63,"subdomain":39,"description":7,"mitre_attack":68},[58,59,60,36,50,37,38,49],"distroless","container-images","minimal-base","mahipal","1.0",[64,65,66,67],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01",[69,70,71,72,73],"T1610","T1611","T1609","T1525","T1195","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-container-image-minimal-base-with-distroless",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":85,"prompt":95,"zipAvailable":96},[86,89,92],{"tool":87,"command":88},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-container-image-minimal-base-with-distroless",{"tool":90,"command":91},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-container-image-minimal-base-with-distroless",{"tool":93,"command":94},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-container-image-minimal-base-with-distroless","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-container-image-minimal-base-with-distroless\u002FSKILL.md",true,[98,104,109,115,119,123,129],{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"assets\u002Ftemplate.md","ASSET","资产文件",732,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-container-image-minimal-base-with-distroless\u002Fassets\u002Ftemplate.md",{"path":105,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-container-image-minimal-base-with-distroless\u002FLICENSE",{"path":110,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fapi-reference.md","REFERENCE","参考文档",1666,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-container-image-minimal-base-with-distroless\u002Freferences\u002Fapi-reference.md",{"path":116,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fstandards.md",626,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-container-image-minimal-base-with-distroless\u002Freferences\u002Fstandards.md",{"path":120,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Fworkflows.md",756,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-container-image-minimal-base-with-distroless\u002Freferences\u002Fworkflows.md",{"path":124,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":127,"sourceHtmlUrl":128},"scripts\u002Fagent.py","SCRIPT","脚本",5914,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-container-image-minimal-base-with-distroless\u002Fscripts\u002Fagent.py",{"path":130,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":131,"sourceHtmlUrl":132},"scripts\u002Fprocess.py",6930,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-container-image-minimal-base-with-distroless\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":143,"publishedAt":52},"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":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[144,145,146,147,48,47,148,149,43,150,151,152,38,153,154,35,155,156,157,158],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","ci","pipeline","supply-chain-security","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":52},"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":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},[167,155,168,169,48,170,47,43,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":52},"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":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},[177,194,195,196,197,47,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":52},"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":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},[219,220,221,47,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":52},"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":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},[245,246,247,47,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":52},"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":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},[48,272,47,273,274,275,276,277,278,279,280,206,281,207,282,283,284,285,286,287],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]