SSZcreate/Pentab_server / .agents/skills/cybersecurity/skills/implementing-gcp-binary-authorization
implementing-gcp-binary-authorization
VerifiedImplements 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.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 11.0 KB |
| SKILL.md | skill md | 7.7 KB |
| assets/template.md | markdown | 690 B |
| references/api-reference.md | markdown | 1.8 KB |
| references/standards.md | markdown | 473 B |
| references/workflows.md | markdown | 653 B |
| scripts/agent.py | script | 7.8 KB |
| scripts/process.py | script | 6.0 KB |
references/api-reference.md
View on GitHub# API Reference: Implementing GCP Binary Authorization
## gcloud CLI Commands
```bash
# Enable APIs
gcloud services enable binaryauthorization.googleapis.com containeranalysis.googleapis.com
# Enable on GKE cluster
gcloud container clusters update CLUSTER --enable-binauthz --zone ZONE
# Export policy
gcloud container binauthz policy export --project PROJECT_ID
# Import policy
gcloud container binauthz policy import policy.yaml
# Create attestor
gcloud container binauthz attestors create ATTESTOR_NAME \
--attestation-authority-note=NOTE_ID \
--attestation-authority-note-project=PROJECT_ID
# Create attestation
gcloud container binauthz attestations sign-and-create \
--artifact-url="gcr.io/PROJECT/IMAGE@DIGEST" \
--attestor="ATTESTOR" --attestor-project="PROJECT" \
--keyversion-project=PROJECT --keyversion-location=global \
--keyversion-keyring=KEYRING --keyversion-key=KEY --keyversion=1
```
## Policy Structure
| Field | Values | Description |
|-------|--------|-------------|
| `evaluationMode` | ALWAYS_ALLOW, ALWAYS_DENY, REQUIRE_ATTESTATION | How images are evaluated |
| `enforcementMode` | ENFORCED_BLOCK_AND_AUDIT_LOG, DRYRUN_AUDIT_LOG_ONLY | Block or audit-only |
| `globalPolicyEvaluationMode` | ENABLE, DISABLE | Google-maintained system policy |
## Break-Glass Annotation
```yaml
metadata:
annotations:
alpha.image-policy.k8s.io/break-glass: "Emergency - INC-12345"
```
## Cloud Logging Filter (CV Violations)
```
resource.type="k8s_cluster"
logName="projects/PROJECT/logs/binaryauthorization.googleapis.com%2Fcontinuous_validation"
```
### References
- GCP Binary Authorization: https://cloud.google.com/binary-authorization/docs
- Container Analysis API: https://cloud.google.com/container-analysis/docs
- SLSA Framework: https://slsa.dev
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Verified | Install |