Leanpub Header

Skip to main content

Secure Software Supply Chains

End-to-End Security for Modern Software Delivery

Secure Software Supply Chains
This book is 100% completeLast updated on 2026-08-01

Your software is only as secure as the path it takes to production. This book walks you through protecting every stage of the software supply chain, from dependencies and builds to deployment and runtime. Learn practical techniques, proven tools and the mindset needed to stop modern supply chain attacks before they spread.

Minimum price

$19.00

$29.00

You pay

Author earns

$

Also available for 1 book credit with a Reader Membership

PDF
EPUB
WEB
APP
214
Pages
About

About

About the Book

Every line of code you ship depends on hundreds of external components, automated build pipelines, and deployment systems that you do not fully control. The software supply chain is the longest attack surface in your infrastructure and the one most teams leave unprotected. This book shows you how to secure it from source code through dependencies, builds, artifacts, and runtime deployment using cryptographic verification, policy enforcement, and automation that works in production. You will learn the threat models behind real-world incidents like SolarWinds and Log4Shell, implement reproducible builds with Bazel and Nix, generate SBOMs and provenance attestations, sign artifacts with Sigstore, enforce policies in Kubernetes clusters, and wire everything together into a complete secure delivery pipeline that scales across teams. By the end you will understand not just which tools to use but why they work together, where they fail, and how to design a supply chain security program that survives audits, incidents, and organizational change.

Author

About the Author

Steve Publications

Steve is a technology professional with more than 20 years of experience spanning software development, server infrastructure, cybersecurity, vulnerability research and reverse engineering. His work focuses on understanding complex systems, uncovering security weaknesses and developing practical solutions that make technology more secure, reliable and effective.

Through Steve Publications, he collaborates with experienced researchers, engineers and industry experts to create practical, technically rigorous books on various topics not limited to self-improvement, software development, cybersecurity, cloud computing, DevOps, artificial intelligence and enterprise technologies. His mission is to make complex technical subjects accessible through clear explanations, real-world examples and hands-on exercises that help IT professionals, students and technology enthusiasts build valuable, practical skills.

Steve Publications embraces AI as a supporting tool for translation, proofreading and editorial refinement, not as a substitute for original research, technical expertise, or hands-on experience. Some contributors choose to publish under pseudonyms to protect their privacy or maintain professional boundaries.

Behind every book is a commitment to technical accuracy, practical relevance and continuous improvement. Our publications are written, reviewed and maintained by experienced professionals, with support from a private community of more than 420 engineers and researchers. Rather than prioritizing volume or mass-produced AI-generated content, we focus on delivering reliable, useful resources that readers can apply in real-world environments.

We also welcome experienced professionals who want to share their knowledge by writing or reviewing books, particularly in specialized and emerging technology fields. If you have expertise to contribute, we invite you to get in touch and explore opportunities to collaborate.

Our commitment is simple: To deliver books that respect our readers' time, support their professional growth and provide lasting practical value. If a book does not meet your expectations, Leanpub offers a 60-day money-back guarantee.

Contents

Table of Contents

End-to-End Security for Modern Software Delivery

Introduction: The Longest Attack Surface

  1. Why Traditional Security Fails
  2. What This Book Covers
  3. Who Should Read This Book
  4. How to Use the Code Examples
  5. The Security Mindset

Chapter 1: The Software Supply Chain Under Attack

  1. Anatomy of a Modern Build Pipeline
  2. High-Profile Breaches That Changed Everything
  3. The Trust Model We Inherited
  4. Attack Surfaces Across the Lifecycle
  5. Why Traditional Security Fails Supply Chains
  6. What Comes Next

Chapter 2: Threat Models and Adversary Playbooks

  1. Threat Actor Profiles
  2. The Software Supply Chain Kill Chain
  3. Dependency Confusion and Typosquatting Attacks
  4. Build System Compromise Scenarios
  5. Modeling Your Own Risk
  6. What Comes Next

Chapter 3: Securing Dependencies and Package Ecosystems

  1. How Package Ecosystems Work
  2. Dependency Confusion Explained and Defended
  3. Typosquatting and Malicious Packages
  4. Lock Files, Version Pinning, and Reproducible Resolutions
  5. Private Registries and Proxy Caching Strategies
  6. Software Composition Analysis (SCA) Tools in Practice
  7. What Comes Next

Chapter 4: Secure Source Code and Repository Hygiene

  1. Branch Protection Rules That Actually Work
  2. Code Review as a Security Control
  3. Secrets Detection in Source
  4. Signed Commits and Tags with GPG/SSH Keys
  5. Repository Permissions and Least Privilege
  6. Pre-Commit Hooks for Security Checks
  7. What Comes Next

Chapter 5: Reproducible and Hermetic Builds

  1. What Makes a Build Reproducible (and Why It Matters)
  2. Hermeticity: Eliminating Hidden Dependencies
  3. Bazel for Reproducible Builds
  4. Nix as a Build System and Package Manager
  5. BuildKit and Docker Build Reproducibility
  6. Testing Your Build Reproducibility
  7. Trade-offs and Practical Considerations
  8. What Comes Next

Chapter 6: Artifact Signing and Cryptographic Identity

  1. The Math Behind Artifact Signing
  2. Key Management Strategies for Organizations
  3. Cosign: Signing Containers and OCI Artifacts
  4. Fulcio: Certificate Authority for Software Supply Chains
  5. Rekor: Transparency Log for Artifact Signatures
  6. Policy Decisions: Long-Lived Keys vs Short-Lived Certificates
  7. What Comes Next

Chapter 7: Provenance, SLSA, and in-toto Attestations

  1. What Is Build Provenance and Why You Need It
  2. The SLSA Framework Explained
  3. in-toto Attestation Format Deep Dive
  4. Generating SLSA Provenance in CI/CD
  5. Verifying Provenance Before Deployment
  6. Mapping Your Current Pipeline to SLSA Levels
  7. What Comes Next

Chapter 8: SBOM Generation, Consumption, and Policy

  1. What an SBOM Is (and Is Not)
  2. SPDX vs CycloneDX Format Comparison
  3. Generating SBOMs Across Ecosystems
  4. Consuming SBOMs for Vulnerability Scanning
  5. SBOM in Regulatory Context
  6. Integrating SBOM Generation into CI/CD
  7. What Comes Next

Chapter 9: Secure CI/CD Pipeline Architecture

  1. Security Principles for CI/CD Design
  2. GitHub Actions Security
  3. GitLab CI Security Configuration
  4. Jenkins Security Best Practices
  5. Azure DevOps Pipeline Security
  6. Tekton Pipelines for Kubernetes-Native CI/CD
  7. Common Mistakes Across Platforms
  8. What Comes Next

Chapter 10: Secrets Management in the Supply Chain

  1. Why Hardcoded Secrets Destroy Supply Chain Security
  2. OIDC-Based Authentication for Cloud Providers
  3. Vault Integration in CI/CD Pipelines
  4. Kubernetes Secrets and External Secrets Operator
  5. Short-Lived Credentials vs Long-Lived Keys
  6. Secrets Scanning and Rotation Automation
  7. What Comes Next

Chapter 11: Container Image and OCI Artifact Security

  1. Dockerfile Security Best Practices
  2. Image Scanning in the Build Pipeline
  3. Registry Security
  4. OCI Artifacts Beyond Containers
  5. Cosign Policies for Image Verification
  6. Immutable Tags and Content Addressing
  7. What Comes Next

Chapter 12: Kubernetes Supply Chain Security

  1. Admission Controllers as Gatekeepers
  2. Image Verification with Cosign Admissions
  3. Pod Security Standards and Policies
  4. Network Policies for Supply Chain Isolation
  5. Runtime Security Monitoring (Falco)
  6. GitOps Supply Chain Security (Argo CD, Flux)
  7. What Comes Next

Chapter 13: Infrastructure as Code Security

  1. Threat Model for IaC
  2. Terraform Security Best Practices
  3. Policy as Code with OPA/Conftest
  4. Cloud Configuration Scanning
  5. State File Security
  6. Drift Detection and Compliance Monitoring
  7. What Comes Next

Chapter 14: Vulnerability Management and CVE Response

  1. How the CVE Ecosystem Works
  2. Scanning Strategies: SAST, DAST, SCA, Container Scanning
  3. Prioritizing Vulnerabilities Beyond CVSS Scores
  4. Automated Patching and Dependency Updates
  5. Incident Response for Supply Chain Compromises
  6. Building a Vulnerability Management Program
  7. What Comes Next

Chapter 15: End-to-End Secure Pipeline Implementation

  1. Architecture Overview and Design Decisions
  2. Setting Up the Development Environment
  3. Implementing the GitHub Actions Pipeline
  4. Signing and Attesting Artifacts with Sigstore
  5. Generating SBOMs and Verifying Provenance
  6. Deploying to Kubernetes with Admission Control Enforcement
  7. Monitoring, Auditing, and Alerting Configuration
  8. Troubleshooting Common Issues
  9. What You Have Built

Conclusion

References

Get the free sample chapters

Click the buttons to get the free sample in PDF or EPUB, or read the sample online here

The Leanpub 60 Day 100% Happiness Guarantee

Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

See full terms...

Earn $8 on a $10 Purchase, and $16 on a $20 Purchase

We pay 80% royalties on purchases of $7.99 or more, and 80% royalties minus a 50 cent flat fee on purchases between $0.99 and $7.98. You earn $8 on a $10 sale, and $16 on a $20 sale. So, if we sell 5000 non-refunded copies of your book for $20, you'll earn $80,000.

(Yes, some authors have already earned much more than that on Leanpub.)

Learn more about writing on Leanpub

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Learn more about Leanpub's ebook formats and where to read them

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses!

Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks.

Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy.

Learn more about writing on Leanpub