⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All AWS & Cloud Architecture Interview Questions Scenario 140 of 179 in AWS & Cloud Architecture
Senior DevOps / SRE GCP & Cloud Cloud Security & DevSecOps Supply Chain Security
🎯 Target Role / Context: Senior DevSecOps / Cloud Platform Engineer Scenario

Q: How do you build a zero-trust software supply chain on Google Cloud that guarantees only container images cryptographically signed by your CI/CD pipeline and free of Critical CVEs can ever be scheduled on production GKE clusters?

End-to-end security pipeline implementing vulnerability scanning in GCP Artifact Registry and cryptographically enforcing image signatures via Binary Authorization admission controllers on GKE.

#GCP #Artifact Registry #Binary Authorization #Kritis #Security #GKE
🎙️ Candidate Opening & Architectural Context
"To comply with SOC 2 Type II and FedRAMP controls, our engineering org required an automated gate preventing unsigned containers or images with unpatched Critical vulnerabilities from being deployed to production."
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: To comply with SOC 2 Type II and FedRAMP controls, our engineering org required an automated gate preventing unsigned containers or images with unpatched Critical vulnerabilities from being deployed to production.

1️⃣

Deploy Artifact Registry with Automated Container Vulnerability Scanning

Provision enterprise container repositories with automatic package vulnerability analysis:

  • Repository Creation: Executed gcloud artifacts repositories create prod-containers --repository-format=docker --location=us-central1 --description='Production Images'.
  • Continuous Scanning: Enabled Container Scanning API (containerscanning.googleapis.com) to continuously analyze OS packages and language dependencies against the CVE database.
Pro Tip: Continuous scanning rescans stored images whenever new zero-day CVEs are published, alerting even if images haven't been rebuilt.
2️⃣

Generate Asymmetric Cryptographic Attestation Keys in Cloud KMS

Create an immutable signing authority using Google Cloud Key Management Service:

  • KMS Keyring & Key: Provisioned asymmetric signing key: gcloud kms keys create binauth-signer --keyring=attestors --location=global --purpose=asymmetric-signing --default-algorithm=rsa-sign-pkcs1-4096-sha512.
  • Binary Authorization Attestor: Created Container Analysis note and registered the Attestor linked to the KMS public key.
Pro Tip: Storing the signing private key in Cloud KMS Hardware Security Modules (HSM) prevents private key exfiltration by developers or compromised build workers.
Advertisement
3️⃣

Automate Image Signing and Attestation Creation in Cloud Build / GitHub Actions

Sign container digests only after vulnerability scans and automated integration tests pass:

  • CVE Gate Check: Executed automated check verifying zero Critical/High vulnerabilities exist via Container Analysis API.
  • Sign Image Digest: Executed gcloud beta container binauthz attestations sign-and-create --artifact-url=us-central1-docker.pkg.dev/PROJ/prod/api@sha256:digest --attestor=prod-attestor --keyversion=1.
Pro Tip: Attestations are bound to the immutable SHA256 digest, not mutable image tags like :latest.
4️⃣

Enforce Strict Binary Authorization Admission Controller in GKE

Block non-compliant container deployment attempts directly at the Kubernetes API admission phase:

  • Cluster Policy: Updated GKE cluster with --enable-binauthz --binauthz-evaluation-mode=PROJECT_SINGLETON_POLICY_ENFORCE.
  • Policy Configuration: Configured policy rule requiring attestations from prod-attestor for all workloads in production namespaces.
  • Audit Logging: Verified that any pod deployed with an unsigned image or manual kubectl edit is rejected with HTTP 403 Forbidden and logged to Cloud Audit Logs.
Pro Tip: Even cluster administrators with cluster-admin RBAC permissions cannot bypass Binary Authorization admission controls on GKE.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Binary Authorization pairs with Artifact Registry and Cloud KMS to form a cryptographically verifiable supply chain, ensuring that only vetted, signed container digests can run in production."
⚡ 60-Second Elevator Pitch Talking Points
  • Enable continuous vulnerability scanning on Google Artifact Registry repositories.
  • Establish an asymmetric RSA signing key in Google Cloud KMS for attestations.
  • Cryptographically sign container SHA256 digests in CI/CD only when security test suites pass.
  • Enforce Binary Authorization admission controllers on GKE to block unauthorized or tampered images.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Engineering bespoke in-house developer tools instead of adopting standardized platform Golden Paths when configuring Software Supply Chain Bespoke internal tools create long-term maintenance debt and fragmented workflows, whereas standardized Golden Paths accelerate delivery.
  2. Overlooking infrastructure cost visibility and FinOps allocation tagging across multi-tenant environments when configuring Software Supply Chain Without granular resource tagging, engineering organizations cannot attribute cloud infrastructure costs to specific teams or business units.
  3. Failing to define explicit Service Level Objectives (SLOs) and Error Budgets to balance feature velocity with reliability when configuring Software Supply Chain Without agreed SLOs, engineering and product teams lack an objective data-driven framework to prioritize technical debt over new features.
  4. Neglecting automated continuous drift detection between declarative configuration and deployed cloud state when configuring Software Supply Chain Unmanaged drift accumulates over time, causing future automated deployments to fail or overwrite emergency manual adjustments.
Advertisement
Want more AWS & Cloud Architecture scenarios?
Explore our complete collection of scenario-based AWS & Cloud Architecture interview runbooks.
Browse All AWS & Cloud Architecture Questions →