A new critical CVE is published for a widely used compression library. The security team must quickly list which of the 400 images in its registry include that library, without pulling and unpacking every image. Which practice makes this possible?
Choose one.
SBOMs turn 'are we affected?' into a search.
Because an SBOM records every component and version, a team that generated one per image can respond to a new disclosure by querying the SBOMs. A signature and a provenance attestation answer different questions (who and how), and a scan result from build day was produced before the CVE existed, so it cannot list it.
- Identify the need: find which images contain a named component.
- Pick the record that lists components: the SBOM.
- Reject records about identity or build origin.
- Reject point-in-time scan results that predate the CVE.
Exam tip: Keep an SBOM per image so a new CVE becomes a query, not a rescan.
KCSA Supply Chain Security, Image Registries and Admission Control — the lesson that teaches this.