Package provenance and SBOM · Linux

A package manager tells you what is installed; an SBOM tells you what is in each package; a vulnerability scanner tells you which of those components have known CVEs. Together, they are the discipline that answers “what is on this host, where did it come from, and is any of it vulnerable?”.

SBOM — Software Bill of Materials

An SBOM is a structured inventory of every component in a package or container. The two main formats are SPDX and CycloneDX; both are machine-readable.

Read-only / Safesyft SBOM— syft (from Anchore) generates an SBOM from a package file. The output lists every component, its version, and its license. SBOMs feed into vulnerability scanners and compliance audits.

$ syft /var/cache/apt/archives/openssh-server_*.deb 2>/dev/null | head -30

...

Illustrative output

Format	Use
SPDX	Linux Foundation standard; widely supported by package managers
CycloneDX	OWASP; widely supported by security tooling

Vulnerability scanning

Read-only / Safevulnerability scan— grype (from Anchore) and trivy (from Aqua) scan an SBOM or a live filesystem for known CVEs. Output lists CVE ID, severity, package, and the fixed version. Use this to verify that the host is up-to-date on all known vulnerabilities.

$ grype /var/cache/apt/archives/openssh-server_*.deb 2>/dev/null | head -20; trivy rootfs / 2>/dev/null | head -20

...

Illustrative output

Read-only / Safehost scanners— vuls and lynis scan the live host for vulnerabilities and misconfigurations. vuls focuses on CVEs; lynis focuses on configuration. Both complement each other for vulnerability management.

$ vuls scan openssh-server; lynis audit system

...

Illustrative output

Attestations and provenance

Modern supply chains include attestations — signed statements about how a package was built. The Sigstore project provides tooling for signing and verifying attestations:

Read-only / Safecosign verify— cosign verifies Sigstore-signed attestations. The output confirms that the package was built in a specific GitHub Actions workflow, by a specific identity, with a specific certificate. Provenance attestations catch packages that were built outside the expected workflow.

$ cosign verify openssh-server_*.deb --certificate-identity-regexp 'https://github.com/.*' --certificate-oidc-issuer 'https://token.actions.githubusercontent.com'

...

Illustrative output

Production workflow

Generate SBOMs at build time for in-house packages; at install time for vendor packages
Store SBOMs centrally with version information
Subscribe to vulnerability feeds (NVD, distribution advisories, vendor security lists)
Query the SBOM database when a CVE is published: which hosts are affected?
Patch via the package manager; verify with a re-scan that the vulnerable package is gone
Document the response in the runbook for post-incident review

SBOM — Software Bill of Materials

Vulnerability scanning

Attestations and provenance

Production workflow

Knowledge check