provenance attestation
A signed record, attached to an image, of how, where and from what source it was built.
In more detail
It lets consumers check that an image really came from your CI system and your repository. The SLSA framework defines levels of provenance; BuildKit can produce it with --provenance.
Example
A pipeline owns provenance: link commit, artifact, desired state, deployment and user indicators into one chain of evidence.Related terms
- artifact — A file produced by a build, such as a compiled program or an image, that is stored and passed on to later steps.
- pipeline — An automated sequence of steps, such as build, test, scan and publish, that runs on every change.
- SBOM — A list of every software package and version inside an image, like an ingredients label.
- software supply chain — Everything that goes into your software before it runs: base images, packages, build tools, CI systems and registries.
- continuous integration — Automatically building and testing every change as soon as it is pushed, so problems are caught early.
- builder identity — The recorded identity of the system that built an artefact, such as a named continuous integration pool.
- 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.
- source revision — The exact version of the source code a build used, usually a commit identifier.
Taught in
- Pipelines And GitOps Context — DevOps & Site Reliability 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
- Provenance And Signing — Application Security & Threat Modeling for Engineers