Breaking

Saturday, November 21, 2026

Eliminating CI/CD Supply Chain Attacks in 2026: SLSA Level 4 & Sigstore Provenance

 


Across US, UK, and EU enterprise software organizations, attackers have shifted away from breaching hardened production networks directly. Instead, they target the software build pipeline—injecting malicious dependencies, compromising runner environments, or tampering with container registries before artifacts ever reach Kubernetes clusters.

1. Why Traditional Container Scanning Fails Against Build Tampering

Conventional vulnerability scanners only inspect known CVE signatures inside static image layers. They cannot prove whether a binary was actually compiled from your reviewed Git commit or altered inside a compromised CI runner. By enforcing SLSA Level 4 (Supply-chain Levels for Software Artifacts) alongside Sigstore Cosign and ephemeral OIDC identities, platform teams generate unforgeable cryptographic provenance attestations at build time.

2. Admission-Time Cryptographic Attestation Policy

Before any container image is scheduled onto production nodes, your Kubernetes admission controller must verify both the keyless OIDC signature and the immutable SLSA provenance predicate:

# Kyverno ClusterPolicy: Enforce Keyless Sigstore & SLSA Provenance
apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: enforce-slsa-provenance-verification
spec:
  validationFailureAction: Enforce
  webhookTimeoutSeconds: 10
  rules:
    - name: verify-cosign-oidc-and-slsa
      match:
        any:
          - resources:
              kinds: ["Pod"]
              namespaces: ["prod-fintech-*", "eu-core-*"]
      verifyImages:
        - imageReferences: ["ghcr.io/enterprise-org/*"]
          attestors:
            - entries:
                - keyless:
                    subject: "https://github.com/enterprise-org/.github/workflows/release.yml@refs/heads/main"
                    issuer: "https://token.actions.githubusercontent.com"
                    rekor:
                      url: https://rekor.sigstore.dev
          attestations:
            - predicateType: https://slsa.dev/provenance/v1
              conditions:
                - all:
                    - key: "{{ buildDefinition.buildType }}"
                      operator: Equals
                      value: "https://slsa-framework.github.io/github-actions-buildtypes/workflow/v1"

3. Enterprise Rollout Checklist for Regulated Engineering Teams

  • Hermetic Ephemeral Build Runners: Execute all release builds inside isolated, network-restricted runners destroyed immediately after artifact signing.
  • Keyless OIDC Workload Identity: Eliminate long-lived signing secrets in CI/CD by binding short-lived Fulcio certificates to verified workflow identities.
  • EU CRA & DORA Audit Compliance: Store immutable SBOMs and Rekor transparency log entries for every release to satisfy EU Cyber Resilience Act (CRA) and DORA audit requirements.

With cryptographic provenance enforced directly at cluster admission, unverified or tampered artifacts are automatically rejected before a single container process starts.

No comments:

Post a Comment