Software Supply Chain Security
Your code, dependencies, build tools, CI identities, registries, container bases and deployment artifacts all execute with trust.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
The pipeline treats downloaded packages and mutable artifacts as trusted while CI has broad secrets and deployment authority.
The important question is not “what is Software Supply Chain Security?” but “which assumption let untrusted data or an over-scoped identity cross external code and build input → trusted production artifact?” Trace the decision at the boundary, then constrain what can happen after the first control fails.
Design the control in layers
Start with the control closest to the interpretation or privilege boundary: Minimize and pin dependencies and verify provenance Then add a control that reduces blast radius and telemetry that proves the decision was enforced.
The resulting design is not labelled secure. Record the identified controls, the known failure paths, the remaining exposure, and the evidence you would need during an incident.
| Prevent | Detect | Recover |
|---|---|---|
| Minimize and pin dependencies and verify provenance · Isolate untrusted builds from secrets · Promote immutable verified artifacts | Dependency, provenance and artifact verification failures | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: Integrity of the software that reaches users and production.
- Boundary: External code and build input → trusted production artifact
- Primary control: Minimize and pin dependencies and verify provenance
- Detection signal: Dependency, provenance and artifact verification failures
- Always ask what limits damage when the primary control fails.
Boundary control exercise
This lesson uses the shared boundary-control exercise.
Follow the attack
Safe conceptual simulation: capability → missing control → crossed boundary → asset impact.
- 1Attacker starts with: A malicious maintainer, compromised registry/account, dependency or CI runner.
- 2The pipeline treats downloaded packages and mutable artifacts as trusted while CI has broad secrets and deployment authority.
- 3The weak or missing boundary control is crossed: External code and build input → trusted production artifact
- 4Impact: Compromise distributed through every build or deployment.
- Compromise distributed through every build or deployment.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Minimize and pin dependencies and verify provenance
- • Isolate untrusted builds from secrets
- • Promote immutable verified artifacts
- • Dependency, provenance and artifact verification failures
- • Contain the affected identity or component.
- • Scope access from audit evidence.
- • Fix the boundary and add a regression test.
- • Misconfiguration and new access paths can bypass the intended control.
- • A privileged insider or compromised control plane may still reach the asset.