Compare

SBOM vs SLSA v1.0: how they differ, side by side

How SBOM and SLSA v1.0 differ: what each is, who owes it, when it applies and who enforces it.

SBOMGuidance; binding only where a contract or sector rule requires it

SLSA v1.0Voluntary framework

Checked21 Oct 2026

01 / Side by side

SBOM and SLSA v1.0, side by side

	SBOM	SLSA v1.0
What it is	guidance	technical specification
Jurisdiction	United States (federal)	International
Legal force	Guidance; binding only where a contract or sector rule requires it	Voluntary framework
Status	Published standard	Superseded
Applies from	12 Jul 2021	19 Apr 2023
Who owes it	Software producers selling to federal agencies or regulated buyers, and organizations that procure or operate software.	Software producers and build platform operators that want to show build integrity, and consumers verifying artifacts.
Enforcement	No general penalty. Federal agencies may require SBOMs by contract (OMB M-26-05); other mandates come from sector rules and foreign law.	None; voluntary.

02 / SBOM

What SBOM requires

The 2026 baseline expressly covers AI software but adds no AI-specific fields; CISA and G7 partners issued separate AI SBOM minimum elements in May 2026 as a supplement.

01Produce SBOMs with the 17 minimum data fields, including component producer, version, identifiers, hash value and license.
02Record SBOM author, timestamp, tool name and version, and generation context (lifecycle phase).
03Sign the SBOM so recipients can confirm it is unaltered (SBOM Author Signature).
04Use machine-processable formats such as SPDX or CycloneDX and update the SBOM when components change.
05For federal cloud contracts with SBOM terms, provide an SBOM of the runtime production environment on request.

03 / SLSA v1.0

What SLSA v1.0 requires

Build provenance can apply to model training or packaging pipelines that produce AI artifacts, but SLSA does not address models or data specifically.

01Build L1: follow a consistent build process and generate and distribute provenance describing platform, process and top-level inputs.
02Build L2: run builds on a hosted build platform that signs the provenance.
03Build L3: use a hardened platform that isolates runs and keeps signing secrets from user-defined build steps.
04Consumers verify provenance against expected builder, source and parameters before use.

Optional evidence · where Planisphere fits

Keep a record anyone can check

When your team meets a duty, Planisphere can seal the event it reports as a receipt.

01 · Your teamRecord the event

A disclosure shown, a review signed, a model change approved: the event your system reports.

02 · PlanisphereSeal it

The event becomes a sealed receipt, dated and attributed to whoever is signed in.

03 · AnyoneCheck it

Paste the receipt into Verify. No account or key.

A record supports your compliance evidence process. It is not a legal finding or a certification. Systems that call Planisphere's gate API can also hold or refuse an action before it runs.

SOURCES