Published Sep 12, 2026 · 12 min read
Attackers no longer brute-force firewalls — they poison build artifacts. SolarWinds, MOVEit, and 3CX taught one lesson: your pipeline is the perimeter. In 2026 the median time-to-exploit for a newly disclosed dependency vulnerability is under 5 hours. A pipeline that ships fast but ships blind is an open door.
Rotate short-lived credentials. Use Workload Identity Federation (WI) or OIDC instead of static service account keys. Mount secrets at runtime via Secret Manager or Vault — never commit them. Enforce short-lived tokens for registry and cloud access.
Pin base images by digest (python:3.12-slim@sha256:…), distroless where possible, rebuild nightly, scan with Grype/Trivy before push. Fail builds on CRITICAL CVEs without a signed exception record.
Generate SBOM (CycloneDX) and provenance (SLSA level 3). Sign images with Cosign. Publish signatures and SBOM to the registry next to the image — consumers can verify before deploy.
package main
deny[msg] { input.digest == "" ; msg = "Image must be pinned by digest" }
deny[msg] { count(input.scans.critical) > 0 ; msg = "CRITICAL CVEs present" }
allow { count(deny)==0 }
deny[msg] { not input.signatures.cosign ; msg = "Image not cosigned" }
Emit build attestations to your SIEM. Alert on signature verification failures at deploy time. On incident, your SBOM lets you answer in minutes: Which services include the affected vulnerability? Which hosts ran them? Roll, patch, redeploy — with evidence.