Skip to the content ForoHackers
Log inJoin

Supply chain security: start here

Supply chain security
#3317 · · Quote · 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

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply