[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEZJSYY3DPYBMNVK5T2VFW":3,"skill-same:01M6AEZJSYY3DPYBMNVK5T2VFW":126},{"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":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":74,"ownerDescription":75,"updatedAt":76,"install":77,"resources":90},"01M6AEZJSYY3DPYBMNVK5T2VFW","implementing-aqua-security-for-container-scanning",null,"Deploy Aqua Security's Trivy scanner to detect vulnerabilities, misconfigurations, secrets, and license issues in container images across CI\u002FCD pipelines and registries.","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\u002Fimplementing-aqua-security-for-container-scanning\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"implementing aqua security for container scanning","security","SBOM","image-security","trivy","aqua-security","t1195","t1059","vulnerability-scanning","container-scanning","supply-chain","image","ci","license","issues","container images","pr","vulnerabilities","cybersecurity","devsecops","2026-11-10 10:12:30",false,"---\nname: implementing-aqua-security-for-container-scanning\ndescription: Deploy Aqua Security's Trivy scanner to detect vulnerabilities, misconfigurations,\n  secrets, and license issues in container images across CI\u002FCD pipelines and registries.\ndomain: cybersecurity\nsubdomain: devsecops\ntags:\n- aqua-security\n- trivy\n- container-scanning\n- vulnerability-scanning\n- sbom\n- image-security\n- supply-chain\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- GV.SC-07\n- ID.IM-04\n- PR.PS-04\nmitre_attack:\n- T1195\n- T1554\n- T1059.004\n- T1610\n- T1611\n---\n\n# Implementing Aqua Security for Container Scanning\n\n## Overview\n\nAqua Security provides Trivy, the world's most popular open-source universal security scanner, designed to find vulnerabilities, misconfigurations, secrets, SBOM data, and license issues in containers, Kubernetes, code repositories, and cloud environments. Trivy covers OS packages (Alpine, Debian, Ubuntu, RHEL, etc.) and language-specific dependencies (npm, pip, Maven, Go modules, Cargo, etc.) with vulnerability databases sourced from NVD, vendor advisories, and GitHub Security Advisories. The enterprise Aqua Platform extends Trivy with centralized policy management, runtime protection, and compliance reporting.\n\n\n## When to Use\n\n- When deploying or configuring implementing aqua security for container scanning 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 installed for local image scanning\n- CI\u002FCD platform (GitHub Actions, GitLab CI, Jenkins, etc.)\n- Container registry access (Docker Hub, ECR, GCR, ACR, Harbor)\n- Trivy CLI (`trivy`) or Trivy Operator for Kubernetes\n- Aqua Platform license for enterprise features (optional)\n\n## Core Scanning Capabilities\n\n### Image Vulnerability Scanning\n\nTrivy scans container images layer by layer, identifying CVEs in OS packages and application dependencies. It supports scanning local images, remote registry images, and tar archives.\n\n```bash\n# Scan a remote image\ntrivy image python:3.11-slim\n\n# Scan with severity filter\ntrivy image --severity HIGH,CRITICAL nginx:latest\n\n# Scan and fail CI if critical CVEs found\ntrivy image --exit-code 1 --severity CRITICAL myapp:latest\n\n# Generate SBOM in CycloneDX format\ntrivy image --format cyclonedx --output sbom.json myapp:latest\n```\n\n### Filesystem and Repository Scanning\n\n```bash\n# Scan project directory for vulnerabilities in dependencies\ntrivy fs --scanners vuln,secret,misconfig .\n\n# Scan a specific lockfile\ntrivy fs --scanners vuln package-lock.json\n\n# Scan git repository\ntrivy repo https:\u002F\u002Fgithub.com\u002Forg\u002Fproject\n```\n\n### Kubernetes Scanning with Trivy Operator\n\nThe Trivy Operator runs inside a Kubernetes cluster and continuously scans workloads:\n\n```bash\n# Install Trivy Operator via Helm\nhelm repo add aqua https:\u002F\u002Faquasecurity.github.io\u002Fhelm-charts\u002F\nhelm repo update\nhelm install trivy-operator aqua\u002Ftrivy-operator \\\n  --namespace trivy-system \\\n  --create-namespace \\\n  --set trivy.severity=\"HIGH,CRITICAL\" \\\n  --set operator.scanJobTimeout=\"5m\"\n```\n\nThe operator creates VulnerabilityReport and ConfigAuditReport custom resources for each workload.\n\n### IaC Misconfiguration Scanning\n\n```bash\n# Scan Terraform files\ntrivy config --severity HIGH,CRITICAL .\u002Fterraform\u002F\n\n# Scan Dockerfile for misconfigurations\ntrivy config Dockerfile\n\n# Scan Kubernetes manifests\ntrivy config .\u002Fk8s-manifests\u002F\n```\n\n## CI\u002FCD Integration\n\n### GitHub Actions\n\n```yaml\nname: Container Security Scan\non:\n  push:\n    branches: [main]\n  pull_request:\n\njobs:\n  scan:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Build Docker image\n        run: docker build -t myapp:${{ github.sha }} .\n\n      - name: Run Trivy vulnerability scanner\n        uses: aquasecurity\u002Ftrivy-action@master\n        with:\n          image-ref: 'myapp:${{ github.sha }}'\n          format: 'sarif'\n          output: 'trivy-results.sarif'\n          severity: 'CRITICAL,HIGH'\n          exit-code: '1'\n\n      - name: Upload Trivy scan results to GitHub Security tab\n        uses: github\u002Fcodeql-action\u002Fupload-sarif@v3\n        if: always()\n        with:\n          sarif_file: 'trivy-results.sarif'\n```\n\n### GitLab CI\n\n```yaml\ncontainer_scanning:\n  stage: security\n  image:\n    name: aquasec\u002Ftrivy:latest\n    entrypoint: [\"\"]\n  variables:\n    FULL_IMAGE_NAME: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHORT_SHA\n  script:\n    - trivy image --exit-code 0 --format template --template \"@\u002Fcontrib\u002Fgitlab.tpl\"\n      --output gl-container-scanning-report.json $FULL_IMAGE_NAME\n    - trivy image --exit-code 1 --severity CRITICAL $FULL_IMAGE_NAME\n  artifacts:\n    reports:\n      container_scanning: gl-container-scanning-report.json\n```\n\n### Jenkins Pipeline\n\n```groovy\npipeline {\n    agent any\n    stages {\n        stage('Build') {\n            steps {\n                sh 'docker build -t myapp:${BUILD_NUMBER} .'\n            }\n        }\n        stage('Security Scan') {\n            steps {\n                sh '''\n                    trivy image --exit-code 1 \\\n                      --severity HIGH,CRITICAL \\\n                      --format json \\\n                      --output trivy-report.json \\\n                      myapp:${BUILD_NUMBER}\n                '''\n            }\n            post {\n                always {\n                    archiveArtifacts artifacts: 'trivy-report.json'\n                }\n            }\n        }\n    }\n}\n```\n\n## Policy Configuration\n\n### Trivy Policy with OPA\u002FRego\n\nCreate `.trivy\u002Fpolicy.rego` for custom policy enforcement:\n\n```rego\npackage trivy\n\ndeny[msg] {\n    input.Results[_].Vulnerabilities[_].Severity == \"CRITICAL\"\n    msg := \"Critical vulnerabilities found in image\"\n}\n\ndeny[msg] {\n    input.Results[_].Vulnerabilities[vuln]\n    vuln.FixedVersion != \"\"\n    vuln.Severity == \"HIGH\"\n    msg := sprintf(\"Fixable HIGH vulnerability: %s\", [vuln.VulnerabilityID])\n}\n```\n\n### Ignore File Configuration\n\nCreate `.trivyignore` for accepted risks:\n\n```\n# Accepted risk: vulnerability in test dependency only\nCVE-2023-12345\n\n# Accepted until expiry date\nCVE-2024-67890 exp:2025-06-01\n```\n\n## SBOM Generation and Management\n\n```bash\n# Generate CycloneDX SBOM\ntrivy image --format cyclonedx --output sbom-cyclonedx.json myapp:latest\n\n# Generate SPDX SBOM\ntrivy image --format spdx-json --output sbom-spdx.json myapp:latest\n\n# Scan an existing SBOM for new vulnerabilities\ntrivy sbom sbom-cyclonedx.json\n```\n\n## Monitoring and Reporting\n\n| Metric | Description | Target |\n|--------|-------------|--------|\n| Images scanned per day | Total images passing through scanning pipeline | All production images |\n| Critical CVE count | Open critical vulnerabilities across all images | 0 in production |\n| Mean time to patch | Average days from CVE publication to patched image | \u003C 7 days |\n| SBOM coverage | Percentage of production images with generated SBOMs | 100% |\n| Scan duration | Average time per image scan | \u003C 2 minutes |\n\n## References\n\n- [Trivy Documentation](https:\u002F\u002Faquasecurity.github.io\u002Ftrivy\u002F)\n- [Trivy GitHub Repository](https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Ftrivy)\n- [Trivy Operator for Kubernetes](https:\u002F\u002Faquasecurity.github.io\u002Ftrivy-operator\u002F)\n- [Aqua Security Platform](https:\u002F\u002Fwww.aquasec.com\u002Fproducts\u002F)\n- [CycloneDX SBOM Specification](https:\u002F\u002Fcyclonedx.org\u002Fspecification\u002Foverview\u002F)\n","# Implementing Aqua Security for Container Scanning\n\n## Overview\n\nAqua Security provides Trivy, the world's most popular open-source universal security scanner, designed to find vulnerabilities, misconfigurations, secrets, SBOM data, and license issues in containers, Kubernetes, code repositories, and cloud environments. Trivy covers OS packages (Alpine, Debian, Ubuntu, RHEL, etc.) and language-specific dependencies (npm, pip, Maven, Go modules, Cargo, etc.) with vulnerability databases sourced from NVD, vendor advisories, and GitHub Security Advisories. The enterprise Aqua Platform extends Trivy with centralized policy management, runtime protection, and compliance reporting.\n\n\n## When to Use\n\n- When deploying or configuring implementing aqua security for container scanning 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 installed for local image scanning\n- CI\u002FCD platform (GitHub Actions, GitLab CI, Jenkins, etc.)\n- Container registry access (Docker Hub, ECR, GCR, ACR, Harbor)\n- Trivy CLI (`trivy`) or Trivy Operator for Kubernetes\n- Aqua Platform license for enterprise features (optional)\n\n## Core Scanning Capabilities\n\n### Image Vulnerability Scanning\n\nTrivy scans container images layer by layer, identifying CVEs in OS packages and application dependencies. It supports scanning local images, remote registry images, and tar archives.\n\n```bash\n# Scan a remote image\ntrivy image python:3.11-slim\n\n# Scan with severity filter\ntrivy image --severity HIGH,CRITICAL nginx:latest\n\n# Scan and fail CI if critical CVEs found\ntrivy image --exit-code 1 --severity CRITICAL myapp:latest\n\n# Generate SBOM in CycloneDX format\ntrivy image --format cyclonedx --output sbom.json myapp:latest\n```\n\n### Filesystem and Repository Scanning\n\n```bash\n# Scan project directory for vulnerabilities in dependencies\ntrivy fs --scanners vuln,secret,misconfig .\n\n# Scan a specific lockfile\ntrivy fs --scanners vuln package-lock.json\n\n# Scan git repository\ntrivy repo https:\u002F\u002Fgithub.com\u002Forg\u002Fproject\n```\n\n### Kubernetes Scanning with Trivy Operator\n\nThe Trivy Operator runs inside a Kubernetes cluster and continuously scans workloads:\n\n```bash\n# Install Trivy Operator via Helm\nhelm repo add aqua https:\u002F\u002Faquasecurity.github.io\u002Fhelm-charts\u002F\nhelm repo update\nhelm install trivy-operator aqua\u002Ftrivy-operator \\\n  --namespace trivy-system \\\n  --create-namespace \\\n  --set trivy.severity=\"HIGH,CRITICAL\" \\\n  --set operator.scanJobTimeout=\"5m\"\n```\n\nThe operator creates VulnerabilityReport and ConfigAuditReport custom resources for each workload.\n\n### IaC Misconfiguration Scanning\n\n```bash\n# Scan Terraform files\ntrivy config --severity HIGH,CRITICAL .\u002Fterraform\u002F\n\n# Scan Dockerfile for misconfigurations\ntrivy config Dockerfile\n\n# Scan Kubernetes manifests\ntrivy config .\u002Fk8s-manifests\u002F\n```\n\n## CI\u002FCD Integration\n\n### GitHub Actions\n\n```yaml\nname: Container Security Scan\non:\n  push:\n    branches: [main]\n  pull_request:\n\njobs:\n  scan:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Build Docker image\n        run: docker build -t myapp:${{ github.sha }} .\n\n      - name: Run Trivy vulnerability scanner\n        uses: aquasecurity\u002Ftrivy-action@master\n        with:\n          image-ref: 'myapp:${{ github.sha }}'\n          format: 'sarif'\n          output: 'trivy-results.sarif'\n          severity: 'CRITICAL,HIGH'\n          exit-code: '1'\n\n      - name: Upload Trivy scan results to GitHub Security tab\n        uses: github\u002Fcodeql-action\u002Fupload-sarif@v3\n        if: always()\n        with:\n          sarif_file: 'trivy-results.sarif'\n```\n\n### GitLab CI\n\n```yaml\ncontainer_scanning:\n  stage: security\n  image:\n    name: aquasec\u002Ftrivy:latest\n    entrypoint: [\"\"]\n  variables:\n    FULL_IMAGE_NAME: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHORT_SHA\n  script:\n    - trivy image --exit-code 0 --format template --template \"@\u002Fcontrib\u002Fgitlab.tpl\"\n      --output gl-container-scanning-report.json $FULL_IMAGE_NAME\n    - trivy image --exit-code 1 --severity CRITICAL $FULL_IMAGE_NAME\n  artifacts:\n    reports:\n      container_scanning: gl-container-scanning-report.json\n```\n\n### Jenkins Pipeline\n\n```groovy\npipeline {\n    agent any\n    stages {\n        stage('Build') {\n            steps {\n                sh 'docker build -t myapp:${BUILD_NUMBER} .'\n            }\n        }\n        stage('Security Scan') {\n            steps {\n                sh '''\n                    trivy image --exit-code 1 \\\n                      --severity HIGH,CRITICAL \\\n                      --format json \\\n                      --output trivy-report.json \\\n                      myapp:${BUILD_NUMBER}\n                '''\n            }\n            post {\n                always {\n                    archiveArtifacts artifacts: 'trivy-report.json'\n                }\n            }\n        }\n    }\n}\n```\n\n## Policy Configuration\n\n### Trivy Policy with OPA\u002FRego\n\nCreate `.trivy\u002Fpolicy.rego` for custom policy enforcement:\n\n```rego\npackage trivy\n\ndeny[msg] {\n    input.Results[_].Vulnerabilities[_].Severity == \"CRITICAL\"\n    msg := \"Critical vulnerabilities found in image\"\n}\n\ndeny[msg] {\n    input.Results[_].Vulnerabilities[vuln]\n    vuln.FixedVersion != \"\"\n    vuln.Severity == \"HIGH\"\n    msg := sprintf(\"Fixable HIGH vulnerability: %s\", [vuln.VulnerabilityID])\n}\n```\n\n### Ignore File Configuration\n\nCreate `.trivyignore` for accepted risks:\n\n```\n# Accepted risk: vulnerability in test dependency only\nCVE-2023-12345\n\n# Accepted until expiry date\nCVE-2024-67890 exp:2025-06-01\n```\n\n## SBOM Generation and Management\n\n```bash\n# Generate CycloneDX SBOM\ntrivy image --format cyclonedx --output sbom-cyclonedx.json myapp:latest\n\n# Generate SPDX SBOM\ntrivy image --format spdx-json --output sbom-spdx.json myapp:latest\n\n# Scan an existing SBOM for new vulnerabilities\ntrivy sbom sbom-cyclonedx.json\n```\n\n## Monitoring and Reporting\n\n| Metric | Description | Target |\n|--------|-------------|--------|\n| Images scanned per day | Total images passing through scanning pipeline | All production images |\n| Critical CVE count | Open critical vulnerabilities across all images | 0 in production |\n| Mean time to patch | Average days from CVE publication to patched image | \u003C 7 days |\n| SBOM coverage | Percentage of production images with generated SBOMs | 100% |\n| Scan duration | Average time per image scan | \u003C 2 minutes |\n\n## References\n\n- [Trivy Documentation](https:\u002F\u002Faquasecurity.github.io\u002Ftrivy\u002F)\n- [Trivy GitHub Repository](https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Ftrivy)\n- [Trivy Operator for Kubernetes](https:\u002F\u002Faquasecurity.github.io\u002Ftrivy-operator\u002F)\n- [Aqua Security Platform](https:\u002F\u002Fwww.aquasec.com\u002Fproducts\u002F)\n- [CycloneDX SBOM Specification](https:\u002F\u002Fcyclonedx.org\u002Fspecification\u002Foverview\u002F)\n",{"name":5,"tags":52,"author":54,"domain":45,"license":15,"version":55,"nist_csf":56,"subdomain":46,"description":7,"mitre_attack":61},[32,31,36,35,53,30,37],"sbom","mahipal","1.0",[57,58,59,60],"PR.PS-01","GV.SC-07","ID.IM-04","PR.PS-04",[62,63,64,65,66],"T1195","T1554","T1059.004","T1610","T1611","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-aqua-security-for-container-scanning",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":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-aqua-security-for-container-scanning",{"tool":83,"command":84},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-aqua-security-for-container-scanning",{"tool":86,"command":87},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-aqua-security-for-container-scanning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-aqua-security-for-container-scanning\u002FSKILL.md",true,[91,97,102,108,112,116,122],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"assets\u002Ftemplate.md","ASSET","资产文件",866,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-aqua-security-for-container-scanning\u002Fassets\u002Ftemplate.md",{"path":98,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-aqua-security-for-container-scanning\u002FLICENSE",{"path":103,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fapi-reference.md","REFERENCE","参考文档",1977,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-aqua-security-for-container-scanning\u002Freferences\u002Fapi-reference.md",{"path":109,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fstandards.md",1633,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-aqua-security-for-container-scanning\u002Freferences\u002Fstandards.md",{"path":113,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fworkflows.md",1245,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-aqua-security-for-container-scanning\u002Freferences\u002Fworkflows.md",{"path":117,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":120,"sourceHtmlUrl":121},"scripts\u002Fagent.py","SCRIPT","脚本",5887,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-aqua-security-for-container-scanning\u002Fscripts\u002Fagent.py",{"path":123,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":124,"sourceHtmlUrl":125},"scripts\u002Fprocess.py",5514,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-aqua-security-for-container-scanning\u002Fscripts\u002Fprocess.py",[127,151,175,203,229,255],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":136,"publishedAt":47},"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",[133],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[137,138,139,140,28,45,141,142,43,143,144,39,37,145,146,33,147,148,149,150],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","pipeline","supply-chain-security","attestation","code-signing","cosign","keyless",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":47},"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",[157],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},[159,147,160,161,28,162,45,43,163,164,165,166,167,168,169,170,171,172,173,174],"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":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":185,"publishedAt":47},"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",[181,184],{"categoryNo":182,"categoryName":183,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},[169,186,187,188,189,45,190,191,163,192,193,194,195,196,197,198,199,200,201,202],"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":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":47},"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",[209],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},[211,212,213,45,214,215,216,217,218,219,220,221,222,223,224,225,166,226,227,228],"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":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":236,"publishedAt":47},"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",[235],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},[44,237,238,45,239,240,241,242,243,244,245,246,247,248,249,250,251,252,253,254],"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":256,"name":257,"nameZh":6,"description":258,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":259,"categories":260,"keywords":262,"publishedAt":47},"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",[261],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},[28,263,45,264,265,266,267,268,269,270,271,198,272,199,273,274,275,276,277,278],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]