Skip to content

dhi: add build transparency #24136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
craig-osterhout wants to merge 2 commits into
base: main
Choose a base branch
from
+30 −0
Open

dhi: add build transparency #24136

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
26e3a1e
dhi: add build transparency
craig-osterhout Feb 12, 2026
fe4c66a
agent feedback1
craig-osterhout Feb 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions content/manuals/dhi/explore/build-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,36 @@ both base and customized images is backed by SLA commitments, including a 7-day
SLA for critical and high severity vulnerabilities. Only DHI Enterprise includes
SLAs. DHI Free offers a secure baseline but no guaranteed remediation timelines.

## Build transparency

Docker Hardened Images provide transparency into how images are built through
publicly available definitions and verifiable attestations.

### Image definitions

All image definitions are publicly available in the [catalog
repository](https://github.com/docker-hardened-images/catalog).

Each image definition is a declarative YAML specification that includes metadata,
contents, build pipeline steps, security configurations, and runtime settings.

### SLSA attestations

Every Docker Hardened Image includes SLSA Build Level 3 attestations that provide
verifiable build provenance. These attestations show:

- Exactly how the image was built
- The build system and environment used
- All inputs and dependencies
- When and where the build occurred

You can verify and inspect these attestations to confirm the integrity and
provenance of any image. See [SLSA](../core-concepts/slsa.md) for details on
how to verify build attestations.

This transparency lets security teams review image configurations and
understand what goes into each image.

## Build triggers

Builds start automatically. You don't trigger them manually. The system monitors
Expand Down