software supply chain
Everything that goes into your software before it runs: base images, packages, build tools, CI systems and registries.
Third-party automation runs with the same power as your own playbooks, so a malicious or careless update reaches every host.
In more detail
Every dependency you pull in runs with the same trust as your own code. Pinning reviewed versions, reading changes before upgrading and preferring well-maintained sources reduce the risk.
Examples
Roles and collections from Ansible Galaxy are part of your supply chain and run with your playbook's privileges.In Terraform: For Terraform the supply chain includes providers and public modules downloaded at init time. Pinning versions, committing the lock file and reviewing modules before adoption reduce the chance of running something malicious or unexpectedly changed.Related terms
- Ansible Galaxy — The public online hub for sharing Ansible roles and collections, and the ansible-galaxy command that installs from it.
- pinning — Fixing an exact version or digest of something you depend on so it cannot change without you noticing.
- dependency — Anything a program needs in order to work, such as a library, a tool or another service.
- cache poisoning — An attack that plants malicious content in a cache so later trusted builds restore and use it.
- action (GitHub Actions) — A reusable, published unit of automation that a workflow step calls with uses.
- SBOM — A list of every software package and version inside an image, like an ingredients label.
- provenance attestation — A signed record, attached to an image, of how, where and from what source it was built.
- image scanning — Checking the packages inside an image against lists of known vulnerabilities.
- Docker Official Image — A curated image on Docker Hub, such as alpine or python, maintained with documented, reviewed build files.
- typosquatting — Registering a name that differs from a popular one by a small typing mistake, such as a lookalike domain or package name, to catch people who mistype it.
- lockfile — A file that records the exact version of every dependency, including transitive ones, so every install gets the same set.
- public module — A reusable module published to the Terraform Registry, called by an address such as terraform-aws-modules/vpc/aws.
- dependency lock file — The .terraform.lock.hcl file that terraform init writes to record the exact provider versions chosen and their checksums.
- digital signature — A value computed from data and a secret key that lets anyone with the matching verification key confirm the data came from the key holder and was not changed.
Taught in
- Ansible Galaxy — Ansible Configuration Management at Scale
- Speeding Up Builds: Caching Dependencies — Continuous Integration & Continuous Delivery Pipelines
- Securing Pipelines: Secrets Management — Continuous Integration & Continuous Delivery Pipelines
- Supply Chain Security: SBOMs & Cosign Signing — Cloud Security & DevSecOps Engineering
- Scan, Patch And Inspect The Software Supply Chain — Docker Architecture & Production Containers
- Build, Test And Promote The Same Image In CI — Docker Architecture & Production Containers
- CSRF Mitigations, SameSite Cookies And Subresource Integrity — Frontend Architecture & Web Platform
- OIDC: Cloud Access Without Stored Keys — GitHub Actions (GH-200) Exam Prep
- Supply Chain: Pinning, Trusted Actions And Attestations — GitHub Actions (GH-200) Exam Prep
- Your First Program and go run — Concurrent Systems Programming with Go
- One Leaked Kubeconfig: How Far Does It Go? — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Ninety Minutes, Six Domains: Where The Marks Are — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Threat Model Sprint: Name It, Then Stop It — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Who Built This Image? Supply Chain And Registries — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Platform Sprint: Evidence, Order, Proof — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Which Benchmark, And Who Checked It? Compliance And Frameworks — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Dependency Risk And Typosquatting — Application Security & Threat Modeling for Engineers
- Lockfiles And Reproducible Builds — Application Security & Threat Modeling for Engineers
- Software Bill Of Materials — Application Security & Threat Modeling for Engineers
- Provenance And Signing — Application Security & Threat Modeling for Engineers
- Container Security: Minimal Bases And Non Root — Application Security & Threat Modeling for Engineers
- The Terraform Registry And Public Modules — Infrastructure as Code with Terraform
References
- NIST glossary: supply chain
- SLSA: supply-chain levels for software artifacts
- OWASP Top 10 CI/CD Security Risks
- SLSA: supply-chain threats
- Dependency lock file