[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF4Y8601HBS5VHDD6M5TGE":3,"skill-same:01M6AF4Y8601HBS5VHDD6M5TGE":130},{"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},"01M6AF4Y8601HBS5VHDD6M5TGE","implementing-gcp-binary-authorization",null,"Implements GCP Binary Authorization end to end, including creating KMS-backed attestors, Container Analysis notes, deploy-time policies, and signing image attestations, so that only trusted, verified images deploy to GKE and Cloud Run. Use when enforcing container supply-chain integrity or deploy-time attestation checks on GCP.","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-gcp-binary-authorization\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","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 gcp binary authorization","authorization","gcp","software-integrity","integrity","KMS","attestation","t1078","cloud-run","gke","image","supply-chain","container-security","cloud-security","cloud","run","pr","notes","cybersecurity","security","2026-11-10 10:12:30",false,"---\nname: implementing-gcp-binary-authorization\ndescription: Implements GCP Binary Authorization end to end, including creating KMS-backed attestors, Container Analysis notes, deploy-time policies, and signing image attestations, so that only trusted, verified images deploy to GKE and Cloud Run. Use when enforcing container supply-chain integrity or deploy-time attestation checks on GCP.\ndomain: cybersecurity\nsubdomain: cloud-security\ntags:\n- gcp\n- binary-authorization\n- container-security\n- supply-chain\n- gke\n- cloud-run\n- attestation\n- software-integrity\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.IR-01\n- ID.AM-08\n- GV.SC-06\n- DE.CM-01\nmitre_attack:\n- T1078.004\n- T1530\n- T1537\n- T1580\n- T1610\n---\n\n# Implementing GCP Binary Authorization\n\n## Overview\n\nBinary Authorization is a Google Cloud deploy-time security control that ensures only trusted container images are deployed on GKE or Cloud Run. It works through a policy-based model where images must have cryptographic attestations confirming they passed predefined requirements such as vulnerability scans, code reviews, or build pipeline verification. Continuous validation (CV) monitors running pods against policies and logs violations.\n\n\n## When to Use\n\n- When deploying or configuring implementing gcp binary authorization 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- GCP project with Binary Authorization API enabled\n- GKE cluster or Cloud Run service\n- Container Analysis API enabled\n- KMS keys for attestation signing\n- Cloud Build or external CI\u002FCD pipeline\n\n## Enable Binary Authorization\n\n```bash\n# Enable required APIs\ngcloud services enable binaryauthorization.googleapis.com\ngcloud services enable containeranalysis.googleapis.com\ngcloud services enable container.googleapis.com\n\n# Enable Binary Authorization on GKE cluster\ngcloud container clusters update CLUSTER_NAME \\\n  --enable-binauthz \\\n  --zone us-central1-a\n```\n\n## Create Attestor\n\n### Create a KMS key for signing\n\n```bash\n# Create keyring\ngcloud kms keyrings create binauthz-keyring \\\n  --location global\n\n# Create signing key\ngcloud kms keys create attestor-key \\\n  --keyring binauthz-keyring \\\n  --location global \\\n  --algorithm ec-sign-p256-sha256 \\\n  --purpose asymmetric-signing\n```\n\n### Create Container Analysis note\n\n```bash\ncat > \u002Ftmp\u002Fnote.json \u003C\u003C 'EOF'\n{\n  \"attestation\": {\n    \"hint\": {\n      \"humanReadableName\": \"Production Build Attestor\"\n    }\n  }\n}\nEOF\n\ncurl -X POST \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -H \"Authorization: Bearer $(gcloud auth print-access-token)\" \\\n  \"https:\u002F\u002Fcontaineranalysis.googleapis.com\u002Fv1\u002Fprojects\u002FPROJECT_ID\u002Fnotes\u002F?noteId=prod-build-note\" \\\n  -d @\u002Ftmp\u002Fnote.json\n```\n\n### Create the attestor\n\n```bash\ngcloud container binauthz attestors create prod-build-attestor \\\n  --attestation-authority-note=prod-build-note \\\n  --attestation-authority-note-project=PROJECT_ID\n\n# Add KMS key to attestor\ngcloud container binauthz attestors public-keys add \\\n  --attestor=prod-build-attestor \\\n  --keyversion-project=PROJECT_ID \\\n  --keyversion-location=global \\\n  --keyversion-keyring=binauthz-keyring \\\n  --keyversion-key=attestor-key \\\n  --keyversion=1\n```\n\n## Configure Policy\n\n### Default deny-all policy\n\n```yaml\n# binauthz-policy.yaml\nadmissionWhitelistPatterns:\n  - namePattern: \"gcr.io\u002Fgoogle_containers\u002F*\"\n  - namePattern: \"gcr.io\u002Fgoogle-containers\u002F*\"\n  - namePattern: \"k8s.gcr.io\u002F**\"\n  - namePattern: \"gke.gcr.io\u002F**\"\n  - namePattern: \"gcr.io\u002Fstackdriver-agents\u002F*\"\ndefaultAdmissionRule:\n  evaluationMode: REQUIRE_ATTESTATION\n  enforcementMode: ENFORCED_BLOCK_AND_AUDIT_LOG\n  requireAttestationsBy:\n    - projects\u002FPROJECT_ID\u002Fattestors\u002Fprod-build-attestor\nglobalPolicyEvaluationMode: ENABLE\n```\n\n```bash\ngcloud container binauthz policy import binauthz-policy.yaml\n```\n\n### Per-cluster rules\n\n```yaml\nadmissionWhitelistPatterns:\n  - namePattern: \"gcr.io\u002Fgoogle_containers\u002F*\"\nclusterAdmissionRules:\n  us-central1-a.production-cluster:\n    evaluationMode: REQUIRE_ATTESTATION\n    enforcementMode: ENFORCED_BLOCK_AND_AUDIT_LOG\n    requireAttestationsBy:\n      - projects\u002FPROJECT_ID\u002Fattestors\u002Fprod-build-attestor\n  us-central1-a.staging-cluster:\n    evaluationMode: ALWAYS_ALLOW\n    enforcementMode: DRYRUN_AUDIT_LOG_ONLY\ndefaultAdmissionRule:\n  evaluationMode: ALWAYS_DENY\n  enforcementMode: ENFORCED_BLOCK_AND_AUDIT_LOG\n```\n\n## Create Attestations\n\n### Attest an image after successful build\n\n```bash\n# Get image digest\nIMAGE_DIGEST=$(gcloud container images describe \\\n  gcr.io\u002FPROJECT_ID\u002Fmy-app:latest \\\n  --format='get(image_summary.digest)')\n\n# Create attestation\ngcloud container binauthz attestations sign-and-create \\\n  --artifact-url=\"gcr.io\u002FPROJECT_ID\u002Fmy-app@${IMAGE_DIGEST}\" \\\n  --attestor=\"prod-build-attestor\" \\\n  --attestor-project=\"PROJECT_ID\" \\\n  --keyversion-project=\"PROJECT_ID\" \\\n  --keyversion-location=\"global\" \\\n  --keyversion-keyring=\"binauthz-keyring\" \\\n  --keyversion-key=\"attestor-key\" \\\n  --keyversion=\"1\"\n```\n\n### Cloud Build integration\n\n```yaml\n# cloudbuild.yaml\nsteps:\n  - name: 'gcr.io\u002Fcloud-builders\u002Fdocker'\n    args: ['build', '-t', 'gcr.io\u002F$PROJECT_ID\u002Fmy-app:$SHORT_SHA', '.']\n\n  - name: 'gcr.io\u002Fcloud-builders\u002Fdocker'\n    args: ['push', 'gcr.io\u002F$PROJECT_ID\u002Fmy-app:$SHORT_SHA']\n\n  # Vulnerability scanning\n  - name: 'gcr.io\u002Fcloud-builders\u002Fgcloud'\n    entrypoint: 'bash'\n    args:\n      - '-c'\n      - |\n        gcloud artifacts docker images scan \\\n          gcr.io\u002F$PROJECT_ID\u002Fmy-app:$SHORT_SHA \\\n          --format='value(response.scan)'\n\n  # Create attestation after successful scan\n  - name: 'gcr.io\u002Fcloud-builders\u002Fgcloud'\n    entrypoint: 'bash'\n    args:\n      - '-c'\n      - |\n        IMAGE_DIGEST=$(gcloud container images describe \\\n          gcr.io\u002F$PROJECT_ID\u002Fmy-app:$SHORT_SHA \\\n          --format='get(image_summary.digest)')\n        gcloud container binauthz attestations sign-and-create \\\n          --artifact-url=\"gcr.io\u002F$PROJECT_ID\u002Fmy-app@$${IMAGE_DIGEST}\" \\\n          --attestor=\"prod-build-attestor\" \\\n          --attestor-project=\"$PROJECT_ID\" \\\n          --keyversion-project=\"$PROJECT_ID\" \\\n          --keyversion-location=\"global\" \\\n          --keyversion-keyring=\"binauthz-keyring\" \\\n          --keyversion-key=\"attestor-key\" \\\n          --keyversion=\"1\"\n```\n\n## Continuous Validation\n\n```bash\n# Enable CV on a GKE cluster\ngcloud container clusters update CLUSTER_NAME \\\n  --enable-binauthz-monitoring \\\n  --zone us-central1-a\n```\n\n### Monitor CV violations in Cloud Logging\n\n```\nresource.type=\"k8s_cluster\"\nlogName=\"projects\u002FPROJECT_ID\u002Flogs\u002Fbinaryauthorization.googleapis.com%2Fcontinuous_validation\"\n```\n\n## Verification and Testing\n\n### Test deployment of unattested image\n\n```bash\n# This should be blocked\nkubectl run test-unapproved \\\n  --image=docker.io\u002Flibrary\u002Fnginx:latest\n\n# Verify the pod was denied\nkubectl get events --field-selector reason=FailedCreate\n```\n\n### Verify attestation exists\n\n```bash\ngcloud container binauthz attestations list \\\n  --attestor=prod-build-attestor \\\n  --attestor-project=PROJECT_ID\n```\n\n## Break-Glass Override\n\nFor emergency deployments bypassing Binary Authorization:\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: emergency-pod\n  labels:\n    image-policy.k8s.io\u002Fbreak-glass: \"true\"\n  annotations:\n    alpha.image-policy.k8s.io\u002Fbreak-glass: \"Emergency deployment - ticket INC-12345\"\nspec:\n  containers:\n    - name: emergency\n      image: gcr.io\u002FPROJECT_ID\u002Femergency-fix:latest\n```\n\n## References\n\n- GCP Binary Authorization: https:\u002F\u002Fcloud.google.com\u002Fbinary-authorization\u002Fdocs\n- SLSA Framework: https:\u002F\u002Fslsa.dev\n- Sigstore\u002FCosign for container signing\n- Google Software Supply Chain Security Best Practices\n","# Implementing GCP Binary Authorization\n\n## Overview\n\nBinary Authorization is a Google Cloud deploy-time security control that ensures only trusted container images are deployed on GKE or Cloud Run. It works through a policy-based model where images must have cryptographic attestations confirming they passed predefined requirements such as vulnerability scans, code reviews, or build pipeline verification. Continuous validation (CV) monitors running pods against policies and logs violations.\n\n\n## When to Use\n\n- When deploying or configuring implementing gcp binary authorization 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- GCP project with Binary Authorization API enabled\n- GKE cluster or Cloud Run service\n- Container Analysis API enabled\n- KMS keys for attestation signing\n- Cloud Build or external CI\u002FCD pipeline\n\n## Enable Binary Authorization\n\n```bash\n# Enable required APIs\ngcloud services enable binaryauthorization.googleapis.com\ngcloud services enable containeranalysis.googleapis.com\ngcloud services enable container.googleapis.com\n\n# Enable Binary Authorization on GKE cluster\ngcloud container clusters update CLUSTER_NAME \\\n  --enable-binauthz \\\n  --zone us-central1-a\n```\n\n## Create Attestor\n\n### Create a KMS key for signing\n\n```bash\n# Create keyring\ngcloud kms keyrings create binauthz-keyring \\\n  --location global\n\n# Create signing key\ngcloud kms keys create attestor-key \\\n  --keyring binauthz-keyring \\\n  --location global \\\n  --algorithm ec-sign-p256-sha256 \\\n  --purpose asymmetric-signing\n```\n\n### Create Container Analysis note\n\n```bash\ncat > \u002Ftmp\u002Fnote.json \u003C\u003C 'EOF'\n{\n  \"attestation\": {\n    \"hint\": {\n      \"humanReadableName\": \"Production Build Attestor\"\n    }\n  }\n}\nEOF\n\ncurl -X POST \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -H \"Authorization: Bearer $(gcloud auth print-access-token)\" \\\n  \"https:\u002F\u002Fcontaineranalysis.googleapis.com\u002Fv1\u002Fprojects\u002FPROJECT_ID\u002Fnotes\u002F?noteId=prod-build-note\" \\\n  -d @\u002Ftmp\u002Fnote.json\n```\n\n### Create the attestor\n\n```bash\ngcloud container binauthz attestors create prod-build-attestor \\\n  --attestation-authority-note=prod-build-note \\\n  --attestation-authority-note-project=PROJECT_ID\n\n# Add KMS key to attestor\ngcloud container binauthz attestors public-keys add \\\n  --attestor=prod-build-attestor \\\n  --keyversion-project=PROJECT_ID \\\n  --keyversion-location=global \\\n  --keyversion-keyring=binauthz-keyring \\\n  --keyversion-key=attestor-key \\\n  --keyversion=1\n```\n\n## Configure Policy\n\n### Default deny-all policy\n\n```yaml\n# binauthz-policy.yaml\nadmissionWhitelistPatterns:\n  - namePattern: \"gcr.io\u002Fgoogle_containers\u002F*\"\n  - namePattern: \"gcr.io\u002Fgoogle-containers\u002F*\"\n  - namePattern: \"k8s.gcr.io\u002F**\"\n  - namePattern: \"gke.gcr.io\u002F**\"\n  - namePattern: \"gcr.io\u002Fstackdriver-agents\u002F*\"\ndefaultAdmissionRule:\n  evaluationMode: REQUIRE_ATTESTATION\n  enforcementMode: ENFORCED_BLOCK_AND_AUDIT_LOG\n  requireAttestationsBy:\n    - projects\u002FPROJECT_ID\u002Fattestors\u002Fprod-build-attestor\nglobalPolicyEvaluationMode: ENABLE\n```\n\n```bash\ngcloud container binauthz policy import binauthz-policy.yaml\n```\n\n### Per-cluster rules\n\n```yaml\nadmissionWhitelistPatterns:\n  - namePattern: \"gcr.io\u002Fgoogle_containers\u002F*\"\nclusterAdmissionRules:\n  us-central1-a.production-cluster:\n    evaluationMode: REQUIRE_ATTESTATION\n    enforcementMode: ENFORCED_BLOCK_AND_AUDIT_LOG\n    requireAttestationsBy:\n      - projects\u002FPROJECT_ID\u002Fattestors\u002Fprod-build-attestor\n  us-central1-a.staging-cluster:\n    evaluationMode: ALWAYS_ALLOW\n    enforcementMode: DRYRUN_AUDIT_LOG_ONLY\ndefaultAdmissionRule:\n  evaluationMode: ALWAYS_DENY\n  enforcementMode: ENFORCED_BLOCK_AND_AUDIT_LOG\n```\n\n## Create Attestations\n\n### Attest an image after successful build\n\n```bash\n# Get image digest\nIMAGE_DIGEST=$(gcloud container images describe \\\n  gcr.io\u002FPROJECT_ID\u002Fmy-app:latest \\\n  --format='get(image_summary.digest)')\n\n# Create attestation\ngcloud container binauthz attestations sign-and-create \\\n  --artifact-url=\"gcr.io\u002FPROJECT_ID\u002Fmy-app@${IMAGE_DIGEST}\" \\\n  --attestor=\"prod-build-attestor\" \\\n  --attestor-project=\"PROJECT_ID\" \\\n  --keyversion-project=\"PROJECT_ID\" \\\n  --keyversion-location=\"global\" \\\n  --keyversion-keyring=\"binauthz-keyring\" \\\n  --keyversion-key=\"attestor-key\" \\\n  --keyversion=\"1\"\n```\n\n### Cloud Build integration\n\n```yaml\n# cloudbuild.yaml\nsteps:\n  - name: 'gcr.io\u002Fcloud-builders\u002Fdocker'\n    args: ['build', '-t', 'gcr.io\u002F$PROJECT_ID\u002Fmy-app:$SHORT_SHA', '.']\n\n  - name: 'gcr.io\u002Fcloud-builders\u002Fdocker'\n    args: ['push', 'gcr.io\u002F$PROJECT_ID\u002Fmy-app:$SHORT_SHA']\n\n  # Vulnerability scanning\n  - name: 'gcr.io\u002Fcloud-builders\u002Fgcloud'\n    entrypoint: 'bash'\n    args:\n      - '-c'\n      - |\n        gcloud artifacts docker images scan \\\n          gcr.io\u002F$PROJECT_ID\u002Fmy-app:$SHORT_SHA \\\n          --format='value(response.scan)'\n\n  # Create attestation after successful scan\n  - name: 'gcr.io\u002Fcloud-builders\u002Fgcloud'\n    entrypoint: 'bash'\n    args:\n      - '-c'\n      - |\n        IMAGE_DIGEST=$(gcloud container images describe \\\n          gcr.io\u002F$PROJECT_ID\u002Fmy-app:$SHORT_SHA \\\n          --format='get(image_summary.digest)')\n        gcloud container binauthz attestations sign-and-create \\\n          --artifact-url=\"gcr.io\u002F$PROJECT_ID\u002Fmy-app@$${IMAGE_DIGEST}\" \\\n          --attestor=\"prod-build-attestor\" \\\n          --attestor-project=\"$PROJECT_ID\" \\\n          --keyversion-project=\"$PROJECT_ID\" \\\n          --keyversion-location=\"global\" \\\n          --keyversion-keyring=\"binauthz-keyring\" \\\n          --keyversion-key=\"attestor-key\" \\\n          --keyversion=\"1\"\n```\n\n## Continuous Validation\n\n```bash\n# Enable CV on a GKE cluster\ngcloud container clusters update CLUSTER_NAME \\\n  --enable-binauthz-monitoring \\\n  --zone us-central1-a\n```\n\n### Monitor CV violations in Cloud Logging\n\n```\nresource.type=\"k8s_cluster\"\nlogName=\"projects\u002FPROJECT_ID\u002Flogs\u002Fbinaryauthorization.googleapis.com%2Fcontinuous_validation\"\n```\n\n## Verification and Testing\n\n### Test deployment of unattested image\n\n```bash\n# This should be blocked\nkubectl run test-unapproved \\\n  --image=docker.io\u002Flibrary\u002Fnginx:latest\n\n# Verify the pod was denied\nkubectl get events --field-selector reason=FailedCreate\n```\n\n### Verify attestation exists\n\n```bash\ngcloud container binauthz attestations list \\\n  --attestor=prod-build-attestor \\\n  --attestor-project=PROJECT_ID\n```\n\n## Break-Glass Override\n\nFor emergency deployments bypassing Binary Authorization:\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: emergency-pod\n  labels:\n    image-policy.k8s.io\u002Fbreak-glass: \"true\"\n  annotations:\n    alpha.image-policy.k8s.io\u002Fbreak-glass: \"Emergency deployment - ticket INC-12345\"\nspec:\n  containers:\n    - name: emergency\n      image: gcr.io\u002FPROJECT_ID\u002Femergency-fix:latest\n```\n\n## References\n\n- GCP Binary Authorization: https:\u002F\u002Fcloud.google.com\u002Fbinary-authorization\u002Fdocs\n- SLSA Framework: https:\u002F\u002Fslsa.dev\n- Sigstore\u002FCosign for container signing\n- Google Software Supply Chain Security Best Practices\n",{"name":5,"tags":52,"author":54,"domain":45,"license":15,"version":55,"nist_csf":56,"subdomain":40,"description":7,"mitre_attack":61},[29,53,39,38,36,35,33,30],"binary-authorization","mahipal","1.0",[57,58,59,60],"PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01",[62,63,64,65,66],"T1078.004","T1530","T1537","T1580","T1610","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-gcp-binary-authorization",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-gcp-binary-authorization",{"tool":83,"command":84},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-gcp-binary-authorization",{"tool":86,"command":87},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-gcp-binary-authorization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gcp-binary-authorization\u002FSKILL.md",true,[91,97,102,108,112,116,120,126],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"assets\u002Ftemplate.md","ASSET","资产文件",690,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gcp-binary-authorization\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-gcp-binary-authorization\u002FLICENSE",{"path":103,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fadvanced-attacks.md","REFERENCE","参考文档",9996,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Factive-directory-attacks\u002Freferences\u002Fadvanced-attacks.md",{"path":109,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fapi-reference.md",1796,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gcp-binary-authorization\u002Freferences\u002Fapi-reference.md",{"path":113,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fstandards.md",473,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gcp-binary-authorization\u002Freferences\u002Fstandards.md",{"path":117,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":118,"sourceHtmlUrl":119},"references\u002Fworkflows.md",653,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gcp-binary-authorization\u002Freferences\u002Fworkflows.md",{"path":121,"resourceType":122,"resourceTypeDesc":123,"sizeBytes":124,"sourceHtmlUrl":125},"scripts\u002Fagent.py","SCRIPT","脚本",8013,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gcp-binary-authorization\u002Fscripts\u002Fagent.py",{"path":127,"resourceType":122,"resourceTypeDesc":123,"sizeBytes":128,"sourceHtmlUrl":129},"scripts\u002Fprocess.py",6093,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-gcp-binary-authorization\u002Fscripts\u002Fprocess.py",[131,156,179,204,230,257],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":140,"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",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[141,142,143,144,46,45,145,146,43,147,148,149,38,150,151,152,33,153,154,155],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","ci","pipeline","supply-chain-security","t1195","code-signing","cosign","keyless",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"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",[162],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},[164,33,165,166,46,167,45,43,168,169,170,171,172,173,31,174,175,176,177,178],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":187,"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",[185,186],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},[31,188,189,190,191,45,192,193,168,194,195,196,197,198,199,34,200,201,202,203],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":211,"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",[210],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},[212,213,214,45,215,216,217,218,219,220,221,222,223,224,225,226,171,227,228,229],"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":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":237,"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",[236],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},[238,239,240,45,241,242,243,244,245,246,247,248,249,250,251,252,253,254,255,256],"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":258,"name":259,"nameZh":6,"description":260,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":261,"categories":262,"keywords":264,"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",[263],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},[46,265,45,266,267,268,269,270,271,272,273,34,274,200,275,276,277,278,279,280],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]