TechStreamTechStream
Books/Vol. II
VOLUME II · COMING SOON

Securing CI/CD & the Software Supply Chain

SLSA, SBOM, Sigstore, and the Pipelines Attackers Target Most

Chapters20
Parts4
SeriesDevSecOps
SLSASBOMSigstoreOIDC KeylessSupply Chain Attacks
Notify me when it launches
Securing CI/CD & the Software Supply Chain
What this book solves

The software supply chain is the most targeted attack surface in modern infrastructure. SolarWinds, Codecov, XZ Utils, 3CX — every major breach of the last five years ran through a pipeline or a dependency. This volume is the practitioner's manual for building pipelines attackers cannot compromise.

You'll implement SLSA (Supply-chain Levels for Software Artifacts) from Level 1 through Level 4, with specific pipeline configurations for GitHub Actions, GitLab CI, Tekton, and Jenkins. The SLSA chapter doesn't stop at theory — it includes the exact attestation schema, the Sigstore Cosign signing workflow for keyless signatures using OIDC tokens from your CI provider, and the Rekor transparency log verification steps.

SBOM generation gets a dedicated section covering both SPDX and CycloneDX formats, automated SBOM generation with Syft and Grype, SBOM-driven vulnerability management workflows, and the emerging VEX (Vulnerability Exploitability eXchange) standard for reducing SBOM noise. You'll build an SBOM pipeline that produces audit-ready artifacts on every release.

The supply chain attack taxonomy chapter is the most complete public analysis of build-time attack patterns: dependency confusion, typosquatting, CI poisoning, build system compromise, and insider threat vectors — each with detection signatures and preventive controls you can implement this sprint.

After reading this volume you will

Four concrete capabilities you will have

1

Achieve SLSA Level 3 on GitHub Actions or GitLab CI with keyless Sigstore signing using your CI provider's OIDC token

2

Generate SPDX/CycloneDX SBOMs with Syft, automate Grype vulnerability scanning, and implement VEX workflows to suppress known-false-positive CVEs

3

Build a dependency review pipeline that blocks PRs introducing packages with CVSS ≥ 7.0 or no provenance attestation

4

Implement the complete supply chain attack detection taxonomy: 12 attack patterns with YARA-compatible detection signatures

Core concept

The idea behind Volume II

CI/CD Supply Chain SecuritySOURCEGitBUILDDockerfileSIGNcosignVERIFYRekorDEPLOYSLSA L3SBOM generated at every stageSigstore EcosystemFulcio (CA)Rekor (log)keyless signing via OIDCSLSA LevelsL1 – scriptedL2 – hostedL3 – hardenedL4 – two-partyPolicy Engine (OPA / Kyverno)verifies attestations before deployevery artifact is signed, attested, and verifiable
Table of contents

4 parts · 20 chapters

01

Part I — The Pipeline Attack Surface

Complete taxonomy of supply chain attacks (SolarWinds to XZ Utils post-mortem), attacker TTPs mapped to MITRE ATT&CK for CI/CD, and the Pipeline Threat Model template. Covers the trust boundary map every pipeline team needs to draw before adding controls.

02

Part II — SLSA: From Theory to Pipeline Config

SLSA Level 1-4 implementation for GitHub Actions, GitLab CI, Tekton, and Jenkins. Includes the complete provenance attestation schema, build environment hardening (ephemeral build runners, network isolation), and the SLSA verifier integration for downstream consumers.

03

Part III — Artifact Signing and Transparency

Sigstore ecosystem deep-dive: Cosign for container signing, Fulcio as the certificate authority, Rekor transparency log for auditability. Keyless signing workflow using GitHub Actions OIDC. Policy enforcement with OPA Gatekeeper and Kyverno for admission control.

04

Part IV — SBOM, VEX, and Dependency Management

SPDX vs CycloneDX format comparison and when to use each. Syft + Grype automated SBOM pipeline. VEX document workflow for suppressing non-exploitable CVEs. Dependency update automation with Renovate and Dependabot — configuration patterns that don't break production.

Launching 2026 — Early access available

Be the first to read Volume II

Join the waitlist for early access, release announcements, and sample chapters. No spam — one email when it ships.