Aller au contenu
Techstream

Vol. II

Securing CI/CD & the Software Supply Chain

SLSA, SBOM, Sigstore and the pipelines attackers target most

Vol. II

§ 01, De quoi il s'agit

Covers the pipeline as an attack surface: SLSA levels, SBOM and VEX, keyless signing with Sigstore, and the build-time attack patterns from SolarWinds to XZ Utils. Written from the SAST/DAST gates on several critical applications and the SBOM generation in the pipelines I work on today.

§ 02, Ce que je veux que le lecteur sache faire

  1. 01

    Say which SLSA level a pipeline is at and what the next one requires.

  2. 02

    Sign and attest an artifact, and refuse an unsigned one at deploy time.

  3. 03

    Produce an SBOM an auditor can read and a VEX statement for the findings that do not apply.

§ 03, Le schéma auquel je reviens toujours

Défile sur le côté →

CI/CD supply chain securitySourcegitBuildhermeticSigncosignVerifyrekorDeployBuild L3SBOM at each stageSigstore ecosystemFulcio (CA) · Rekor (log)keyless signing via OIDCSLSA v1.0 build levelsL1 provenance · L2 hosted, signedL3 hardened, isolated buildsPolicy engine (OPA / Kyverno)verifies attestations before deploy
Figure, Volume II: source to deploy, with an SBOM at each stage, keyless signing, a transparency log and a policy check before deploy.

§ 04, Structure prévue

  1. Partie I

    The pipeline attack surface

    A taxonomy of supply-chain attacks, from SolarWinds to XZ Utils, and the trust-boundary map to draw before adding controls.

  2. Partie II

    SLSA: from theory to pipeline config

    What each SLSA level requires of the build, and what changes in the pipeline configuration to get there.

  3. Partie III

    Artifact signing and transparency

    Keyless signing and a transparency log, and the policy check that refuses an unsigned artifact at deploy time.

  4. Partie IV

    SBOM, VEX and dependency management

    SBOM formats and when each fits, VEX for the findings that do not apply, and dependency updates that do not break production.

§ 05, Quand ce sera lisible

Ce volume est en cours d’écriture. Laissez votre e-mail et je vous enverrai un seul message quand il sera lisible.

Un seul e-mail quand ce sera lisible.