Skip to the content ForoHackers
Log inJoin

Supply chain security: start here

Supply chain security
#811 · Ophuscado · · Report

Software supply chain security is trusting what you build on: every dependency, build tool, container image and update channel between a source file and a running system. A modern program is mostly other people's code, so a flaw or a tampering anywhere upstream reaches you. The field aims to know what you ship and to prove where it came from.

Key concepts

  • Dependencies: direct and transitive libraries all run with your program's privileges.
  • Pinning and lockfiles: fix exact versions and hashes so builds are repeatable and silent swaps are noticed.
  • Build integrity: the build runs in a controlled, logged environment, so the artefact matches its source.
  • Signing and provenance: signatures and build records say who made an artefact and how.
  • Reproducible builds: anyone can rebuild from source and get the identical result.

Vocabulary

  • SBOM: software bill of materials, the list of components inside a build.
  • Typosquatting: a malicious package named like a popular one, hoping for a mistyped install.
  • Provenance: verifiable evidence of where and how an artefact was built.
  • Vulnerability database: a catalogue of known flaws by package and version.

What to study, in order

  1. How your language's package manager resolves versions, and what a lockfile records.
  2. Generate an SBOM for a project of your own and read it line by line.
  3. Scan dependencies for known vulnerabilities and practise a safe upgrade with tests.
  4. Sign a release artefact and verify the signature on another machine.
  5. Move your project's build into a clean CI environment with minimal permissions and no long-lived secrets.

Related tags

#build-systems #ci-cd #open-source #appsec #containers

Log in or join to reply.