Modern DevSecOps Foundations Module 5 · Artifacts and Evidence

Provenance and SBOM

Updated

Intermediate

What you'll learn

~18 min
  • Attach build provenance to artifacts with the platform's native attestation machinery
  • Generate SBOMs in CI - and know the real 2026 drivers now that the US mandate story changed
  • Navigate the signing landscape: what to use where, and what nobody has standardized yet

From your hashes to everyone’s proofs

Lesson 5.1’s manifest asserts integrity to yourself. This lesson is the ecosystem-standard machinery that asserts it to everyone else - three artifacts in this integrity structure, each answering a different question:

PROVENANCE "who built this, from what, how?" - a signed attestation
ATTESTATION binding artifact -> source commit -> build system -> workflow
SBOM "what's inside it?" - the ingredient list
(CycloneDX or SPDX - both now international standards)
SIGNATURE "has it changed since signing?" - and, keyless, "was the
signer really that CI workflow?"

Provenance - the signed statement of who built this artifact, from which commit, on which build system - is cheap on the platforms that produce it natively, and one build-it-yourself step on the one that does not, as shown in this platform layout:

PLATFORM NATIVE PROVENANCE? WHAT YOU DO
GitHub yes one action call attests workflow / commit / builder
GitLab yes built-in attestation on the job
Azure DevOps NO - and it is this a cosign `attest` step signed with a Key Vault key
training's reference
platform
(its KMS integration), placed in the 2.2 stage
template so every pipeline inherits it

The framework language for “how trustworthy is this build?” is SLSA (Supply-chain Levels for Software Artifacts) — a 0-to-3 ladder for build integrity (the Build track); on GitHub the defaults land you at Build L2 and hardened reusable workflows at L3, while GitLab’s provenance is opt-in and Azure DevOps has none native (current version and pairings: the callout below). What matters more than producing provenance is checking it: a verify step in your own deploy gate refuses any artifact whose attestation does not match the expected repository and workflow — so an artifact built outside your pipeline, or from a repository or workflow you did not expect, is stopped before production (provenance proves where a build came from — review is a separate gate). That refusal is the control, and it costs one template step. Provenance nobody verifies is Lesson 3.4’s SARIF lesson again — emitted on the bet that a consumer arrives; here the consumer can be your own gate, today.

The signing-tool split, stated plainly for an Azure-leaning audience: cosign/Sigstore is the open-ecosystem volume leader (keyless signing bound to CI identity — the workload-identity idea from the other trainings, applied to artifacts); Notation is what the Azure container registry and AKS admission tooling natively expect for enterprise PKI signing. They coexist: cosign for OSS-facing and CI attestations, Notation where your ACR/AKS policy enforcement lives. Choosing is an ADR (3.5), not a religion.

One honest gap to name: as of 2026-11-07 none of this has a widely adopted standard category for AI authorship: agent-authored commits carry the co-author trailers from Lesson 2.4, but no mainstream provenance spec we know of attests “which agent, which model, which prompt.” The trailer convention is what exists; treat it as provenance’s TODO, not its answer.

The SBOM story: mandate died, practice didn’t

Teach this as the case study in why controls survive, because 2026 rewrote the compliance story mid-year: the US federal attestation-collection regime was rescinded - M-26-05 (January 2026) withdrew the M-22-18/M-23-16 memos requiring vendor attestation forms; agencies set their own risk-based requirements now, and contract- or agency-specific SBOM obligations can still apply, so read your own contracts before declaring anything gone. Naive prediction: SBOM practice collapses. What actually happened: generation kept growing - because the real drivers in this summary excerpt were never that one memo:

- EU Cyber Resilience Act: reporting obligations have applied since 11
September 2026, with full application from 11 December 2027 - anyone
selling into Europe keeps SBOMs (ENISA's SBOM Adoption State of Play
2026, n=334, June 2026: 78% had STARTED adopting, 44 of those points
still pilot or limited - and its sample was over 80% CRA-affected, so
read it as a CRA cohort, not the market)
- DoD's software-fast-track experiments went the OTHER way from the
civilian rescission: their SBOM-diff model put supply-chain artifacts at
the CENTER (the program was last reported stalled; the pattern
survives - status in the callout)
- The worm-class attacks (3.3) made "what's inside, exactly?" an incident-
response question you answer in minutes or in days
- CISA's 2026 Minimum Elements for a Software Bill of Materials (final, published 2026-07-29, after a 2025 draft for comment; details in the callout) means
the bar for what a useful SBOM contains is better-defined than ever

The durable lesson beneath the churn: a control justified by one memo dies with the memo; a control justified by operations survives every administration. Generate the SBOM because you need the ingredient list on worm-day — the compliance uses then come free. (And the gap practitioners most often name is consumption: SBOMs get generated far more often than anyone reads them into vulnerability workflows, so being the shop whose SBOMs feed something is a real advantage.)

Switch your workspace agent to Plan mode on your Module 2 pipeline templates and ask it to plan the integrity stage:

Plan an integrity stage for our Module 2 pipeline templates: CycloneDX SBOM generation, build provenance attestation and deploy-gate verification, an ADR on our cosign/Notation signing split, and a nightly VEX-filtered vulnerability diff over deployed digests.

Check that the plan or draft covers:

  • Generating a CycloneDX SBOM at build time for both the container and application, attached alongside Lesson 5.1’s promotion manifest
  • Emitting build provenance attestations (native on GitHub or cosign attest with Key Vault KMS on Azure DevOps) paired with a deploy-template verification step that refuses artifacts from unexpected repositories or workflows
  • An ADR recording the signing-tool split (cosign in CI, Notation where ACR and AKS admission policy consume it) and noting that AI authorship currently relies on commit trailers pending a formal provenance standard
  • A nightly consumption job that diffs the SBOMs bound to every currently deployed artifact digest against the vulnerability feed, filtered by supplier VEX statements and routed into the Lesson 3.4 severity flow

If the nightly vulnerability diff scans only the latest branch build rather than currently deployed digests, follow up with: Query the SBOMs bound to the currently deployed production digests so we check what is actually running.

🔍Status specifics (volatile - verify before citing)click to expand

As of 2026-11-07: SLSA v1.2 current (Source Track new alongside Build); platform attestations = Build L2 default / L3 via hardened reusable workflows; CycloneDX 1.7 is an ECMA standard, SPDX an ISO one; CRA reporting obligations have applied since 11 September 2026, and the main obligations apply from 11 December 2027; the rescission memo is M-26-05, January 2026; CISA’s minimum-elements refresh, a 2025 draft for comment, was finalized as the 2026 Minimum Elements for a Software Bill of Materials (SBOM), published 2026-07-29 (CISA’s announcement) jointly with NSA, FBI and international partners; Azure DevOps has no native attestation producer (BYO via cosign attest + Key Vault KMS signing); DoD’s SWFT (Software Fast Track) program, the SBOM-centric counter-current, was last reported in August 2026 as stalled, with its SBOM-diff model surviving as a pattern (Lesson 4.2 of Secure Software Delivery for Federal Environments, a separate training in this series, tracks its status; re-check before citing); npm and PyPI now generate provenance attestations by default for packages released through trusted publishing. Dates and levels rot: this callout is their canonical home, so check here, then the source.

KNOWLEDGE CHECK

Post-rescission, Meridian's compliance lead proposes: 'The federal SBOM mandate is gone and we're not selling into the EU or doing federal-adjacent work — cut the SBOM generation from the pipelines and revisit if regulation returns.' What's the operations-grounded answer?

Practice status — among mature regulated delivery programs, commercial and federal

(a few rows carry a more specific status - principle, canon, suspended - where one of the five would mislead)

PracticeStatusAlso called
build provenance / attestationcommon baseline native on GitHub and GitLab; BYO on Azure DevOps (cosign + Key Vault)—
SLSA build levelsstrong optional the framework language for build integrity—
SBOM generation per buildcommon baseline formats: SPDX or CycloneDX—
SBOM consumption (deployed-digest diffs)strong optionalSBOM drift detection
VEX statementsemerging supplier not-affected notes; filters feed noise—
keyless signing (cosign/Sigstore)common baseline federal delta: private Sigstore or your own CA - public Fulcio/Rekor often unacceptable—

Scale: required | common baseline | strong optional | reference-shop (seen only at organizations that publish their own practice) | emerging

Key takeaway

Provenance attests who-built-from-what (platform-native, verify-side wired into your own gates), SBOMs inventory what’s inside (generated because worm-day is operational, consumed so they’re not residue), signatures follow the cosign/Notation split by consumer — and the whole stack survived its mandate churn because it was never really about the mandate. AI authorship remains the standards gap; trailers hold the line. Next: pushing all of this evidence somewhere it counts.

LEADERSHIP DECISION
fund provenance + SBOM as standing pipeline steps regardless of mandate status - the driver is incident response time, not a memo
PRACTITIONER ACTION
attest in CI (native or cosign+Key Vault), verify in the deploy gate, generate SBOMs per build and diff the deployed ones nightly with VEX filtering
SUCCESS MEASURE
time to answer 'are we exposed to today's worm?' measured in minutes of query, not days of inventory; zero unverified artifacts reaching prod
Search lessons