International (OpenSSF, Linux Foundation)

SLSA

72 controls. 140 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

72 controls 140 frameworks share controls with it International (OpenSSF, Linux Foundation) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
SLSA-BUILD-L1-1Documented Build Process0
SLSA-BUILD-L1-2Provenance Generation0
SLSA-BUILD-L2-1Hosted Build Platform0
SLSA-BUILD-L2-2Signed Provenance0
SLSA-BUILD-L3-1Hardened Build Platform0
SLSA-BUILD-L3-2Isolated Provenance Generation0
SLSA-BUILD-PARAM-1Build Parameter Recording0
SLSA-CONSUMER-1Provenance Verification by Consumer0
SLSA-CONSUMER-2Artifact Storage and Distribution Integrity0
SLSA-DEP-1Dependency Inventory0
SLSA-DEP-2Dependency Provenance Verification0
SLSA-DEP-3Vulnerability Monitoring of Dependencies0
SLSA-EXPECT-1Expectations Document for Artifacts0
SLSA-INCIDENT-1Supply Chain Incident Response0
SLSA-PROD-1Producer Identification0
SLSA-PROD-2Public Source Repository0
SLSA-RUNNER-1Build Runner Integrity0
SLSA-SRC-1Verified Source History0
SLSA-SRC-2Two Person Reviewed Changes0
SLSA-VSA-1Verification Summary Attestation0
SUPCHAIN-1Build Integrity - Source, Build, Provenance128
SUPCHAIN-2Source Integrity - Branch Protection, Code Review, Two-Person Rule88
SUPCHAIN-3Dependency Verification and SBOM26
SUPCHAIN-4Verification, Attestation, In-Toto Integration0
AF.1Build provenance content and model0
AF.2Produce verification summary attestations correctly0
AF.3Verify verification summary attestations0
AF.4Issue SLSA verified properties only when earned0
BB.1Industry security best practices for every implementation0
BB.2Provenance exists (Build L1)0
BB.3Provenance is authentic (Build L2)0
BB.4Provenance is unforgeable (Build L3)0
BB.5Hosted build platform (Build L2)0
BB.6Isolated builds (Build L3)0
BD.1Bind attestations to artifacts, not releases0
BD.2Publish attestations where consumers can get them0
BD.3Immutable attestations in an accepted format0
BP.1Choose an appropriate build platform (Build L1 to L3)0
BP.2Follow a consistent build process (Build L1 to L3)0
BP.3Distribute provenance to consumers (Build L1 to L3)0
BV.1Verify the artifact's Build level against roots of trust0
BV.2Check provenance against expectations0
BV.3Form and protect expectations0
BV.4Verify at one or more architecture points0
BV.5Assess build platforms before trusting them0
SE.1Expert code review0
SE.2Review every single revision0
SE.3Automated testing before acceptance0
SE.4Every revision reachable from a branch was approved0
SE.5Immutable change discussion0
SE.6Merge trains0
SO.1Choose an appropriate source control system (Source L1 to L4)0
SO.2Configure the SCS to control access and enforce history (Source L2 to L4)0
SO.3Safe expunging process (Source L2 to L4)0
SO.4Continuous technical controls (Source L3 and L4)0
SS.1Repositories are uniquely identifiable (Source L1 to L4)0
SS.10Protected named references (Source L3 and L4)0
SS.11Two-party review (Source L4)0
SS.2Revisions are immutable and uniquely identifiable (Source L1 to L4)0
SS.3Human readable changes (Source L1 to L4)0
SS.4Source verification summary attestations (Source L1 to L4)0
SS.5Source VSA content0
SS.6Change history (Source L2 to L4)0
SS.7Control continuity (Source L2 to L4)0
SS.8Identity management (Source L2 to L4)0
SS.9Source provenance (Source L2 to L4)0
SV.1Verify source revisions0
SV.2Assess source control systems before trusting them0
X.1SLSA, its editions and status0
X.2Tracks and levels0
X.3Terminology and roles0
X.4Threat model and guiding principles0

Tell me when SLSA files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for SLSA, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition