Dependency Security
Lockfiles, review, scanning, provenance and compatibility tests manage transitive code without treating every update as automatically safe.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
Unreviewed floating versions or abandoned transitive packages execute in build scripts or production with broad access.
The important question is not “what is Dependency Security?” but “which assumption let untrusted data or an over-scoped identity cross package ecosystem → build and runtime?” 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: Use lockfiles and trusted registries 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 |
|---|---|---|
| Use lockfiles and trusted registries · Minimize dependencies and review meaningful changes · Patch based on exposure and test compatibility | Dependency inventory and vulnerability/provenance scanning | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: Application integrity and the build graph.
- Boundary: Package ecosystem → build and runtime
- Primary control: Use lockfiles and trusted registries
- Detection signal: Dependency inventory and vulnerability/provenance scanning
- 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 vulnerable or malicious direct/transitive package.
- 2Unreviewed floating versions or abandoned transitive packages execute in build scripts or production with broad access.
- 3The weak or missing boundary control is crossed: Package ecosystem → build and runtime
- 4Impact: Application compromise or exploitable behavior inherited from a package.
- Application compromise or exploitable behavior inherited from a package.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Use lockfiles and trusted registries
- • Minimize dependencies and review meaningful changes
- • Patch based on exposure and test compatibility
- • Dependency inventory and vulnerability/provenance scanning
- • 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.