The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
| Stage | Software Supply Chain Security |
| Maturity | Minimal |
| Content Last Reviewed | 2025-09-23 |
To secure software supply chains by creating secure, tamper-proof, and verifiable software artifacts and attestations.
The vision for Artifact Security is to make it easy for software teams to implement best practices to secure their release, packages, and containers, and provide simple mechanisms for their consumers to verify the authenticity. By making it low-friction, and easy to implement, more software teams will be able to secure their artifacts with little effort, increasing adoption, and improving software supply chain security overall.
GitLab Secure Artifacts are designed to conform to the highest level (Build L3) of the Supply-chain Levels for Software Artifacts, or SLSA ("salsa") specification. We intend to implement this specification using a suite of open source tools called Sigstore, which will be integrated into the GitLab Trusted Control Plane to create an end-to-end solution for securing software artifacts.
Archiecture and workflow diagrams can be found in the Architecture Design Document.
GitLab will aggregate security metadata from across the entire software development lifecycle into comprehensive, verifiable attestations:
This aggregated approach provides complete artifact security context in a single, verifiable attestation while maintaining simplicity for consumers.
Tamper-proof provenance will be automatically generated in the GitLab Trusted Control Plane, collecting security metadata from all pipeline stages.
Comprehensive attestations will be generated and signed using Sigstore's keyless signing approach, leveraging GitLab's identity system for seamless integration.
Attestations will be published via the GitLab Attestations API and stored alongside artifacts in registries, with support for both public and self-managed Sigstore infrastructure.
Verification capabilities will include command-line tools (cosign, glab), Kubernetes admission controllers for automated policy enforcement, and developer workflow integrations.
A compliance framework will be developed to help teams maintain SLSA requirements and meet industry standards (SOC 2, NIST SSDF, FedRAMP) with automated monitoring and reporting.
Customers for Secure Artifacts range from small, open-source projects to large enterprise customers with the highest security and compliance requirements.
We have identified several internal customers within GitLab including the Delivery and Runner teams who will help validate and refine the solution.
###Target Segments
Job Artifacts for Public Projects
Container Images for Public Projects
Capture various artifacts from the build process: build logs, security scanning rules, security scan results, SBOM, runner SBOM
Support for self-hosted Sigstore, X.509 Keys for signing and attestation
Review, implement and attest to controls of runner mapping to SLSA controls and work toward providing hermetic build capabilities and publish SBOM for validation Anomaly detection capabilities
Provide compliance view for groups and projects to highlight adoption and gaps of SLSA specification controls
Thanks for visiting this category direction page on Artifact Security in GitLab. This page belongs to the Pipeline Security group of the Software Supply Chain Security (SSCS) stage and is maintained by Jocelyn Eillis (E-Mail).
Please comment and contribute in the linked issues and epics on this page. Sharing your feedback directly on GitLab.com is the best way to contribute to our strategy and vision.