GitHub Launches SLSA Build Level 3 Security with Full Code-to-Cloud Traceability

GitHub rolled out a major safety improve on January 20, 2026, introducing new APIs and tooling that allow improvement groups observe construct artifacts from supply code all the way in which to manufacturing environments—even when these artifacts reside exterior GitHub’s ecosystem.

The discharge addresses a persistent blind spot in enterprise software program safety: understanding precisely what code is operating in manufacturing and whether or not it matches what was really constructed. With software program provide chain assaults turning into more and more subtle, that visibility hole has change into a legal responsibility.

What’s Truly New

Three core capabilities make up the discharge. First, new REST API endpoints permit groups to create storage data (capturing the place artifacts reside in bundle registries) and deployment data (monitoring the place code is operating and related runtime dangers like web publicity or delicate knowledge processing). These APIs work with exterior CI/CD instruments and cloud monitoring programs, not simply GitHub Actions.

Second, a brand new “Linked artifacts view” within the group Packages tab consolidates all artifact knowledge—attestations, storage places, deployment historical past—right into a single dashboard. For groups utilizing GitHub’s artifact attestations, every artifact will get cryptographically certain to its supply repository and construct workflow.

Third, production-context filtering now works throughout Dependabot alerts, code scanning alerts, and safety campaigns. Groups can filter by artifact registry, deployment standing, and runtime danger, then mix these filters with EPSS and CVSS scores to prioritize what really issues.

The SLSA Connection

The cryptographic binding piece is what permits SLSA Construct Stage 3 compliance—a provide chain safety framework that requires verifiable provenance for construct artifacts. Reasonably than trusting {that a} container picture got here from a selected commit, groups can mathematically confirm it. The system surfaces construct provenance attestations, attested SBOMs, and customized attestations by means of the artifact view.

Integration Companions at Launch

Microsoft Defender for Cloud (presently in public preview) handles deployment and runtime knowledge integration. JFrog Artifactory supplies storage and promotion context. Each supply native integrations requiring no further configuration. For groups utilizing different tooling, the REST APIs settle for data from any supply.

GitHub’s attest-build-provenance motion can robotically generate storage data when publishing artifacts, decreasing guide overhead for groups already within the GitHub Actions ecosystem.

Why This Issues for Enterprise Groups

Code-to-cloud traceability has change into a compliance requirement in regulated industries and a sensible necessity all over the place else. Understanding whether or not a flagged vulnerability really made it to manufacturing—versus sitting in an unused department—basically modifications remediation priorities. Safety groups waste vital time chasing vulnerabilities in code that by no means ships.

The timing aligns with broader trade strikes towards software program provide chain verification. With the function now reside, groups can begin constructing deployment data and testing the filtering capabilities instantly. Dialogue threads are energetic in GitHub Group for groups working by means of implementation particulars.

Picture supply: Shutterstock