Sigstore - Software Artifact Signing and Verification
Sigstore is a set of open-source tools for signing, verifying, and protecting software artifacts. Created by Google, Red Hat, and Purdue University, now under the OpenSSF. Components: Cosign (container and artifact signing), Fulcio (certificate authority for ephemeral certificates), Rekor (transparency log), and Gitsign (git commit signing). Sigstore enables keyless signing using OIDC identity (GitHub, Google, Microsoft accounts). Used by npm, PyPI, Kubernetes, Homebrew, and major package ecosystems. Over 20 million signatures in the public Rekor transparency log. Adopted by Kubernetes as the standard for supply chain security.
Sigstore - Software Artifact Signing and Verification is a compliance framework from International (OpenSSF) with 8 domains and 17 controls that map to 120 other frameworks. The largest domains are Sigstore: Cosign Signing and Storage (4 controls), Sigstore: Fulcio Certificate Authority (3 controls), Sigstore: Rekor Transparency Log (3 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (8)
Cosign
| Code | Title |
|---|---|
| SIGSTORE-3 | Sigstore for Containers and Artifacts (Cosign) |
Keyless Signing
| Code | Title |
|---|---|
| SIGSTORE-1 | Keyless Signing with Short-Lived Certificates |
Private Deployment
| Code | Title |
|---|---|
| SIGSTORE-4 | Private Deployment, Long-Lived Migration, Regulated Environments |
Sigstore: Cosign Signing and Storage
| Code | Title |
|---|---|
| SIGSTORE-COS-1 | Keyless Signing |
| SIGSTORE-COS-2 | Key-Based Signing |
| SIGSTORE-COS-3 | OCI Registry Storage |
| SIGSTORE-COS-4 | Signature Verification |
Sigstore: Fulcio Certificate Authority
| Code | Title |
|---|---|
| SIGSTORE-FUL-1 | Short-Lived Certificate Issuance |
| SIGSTORE-FUL-2 | Identity Binding |
| SIGSTORE-FUL-3 | Certificate Transparency |
Sigstore: Rekor Transparency Log
| Code | Title |
|---|---|
| SIGSTORE-REK-1 | Signature Transparency Logging |
| SIGSTORE-REK-2 | Tamper-Evident Storage |
| SIGSTORE-REK-3 | RESTful API Validation |
Sigstore: Verification and Policy Enforcement
| Code | Title |
|---|---|
| SIGSTORE-VER-1 | Timestamp Verification |
| SIGSTORE-VER-2 | Supply Chain Attestation |
| SIGSTORE-VER-3 | Policy Enforcement |
Transparency Log
| Code | Title |
|---|---|
| SIGSTORE-2 | Transparency Log (Rekor) and Verification |
Your Compliance Coverage
If you comply with Sigstore - Software Artifact Signing and Verification, you already cover:
NIST SP 800-171A Rev 3 - Assessing CUI Security Requirements
29%
5 controls mapped
Compare →NIST SP 800-53 Rev 5
29%
5 controls mapped
Compare →South Korea ISMS-P
29%
5 controls mapped
Compare →+ 117 more: ISO 15189:2022 - Medical Laboratories Requirements for Quality and Competence (24%), Singapore Government Instruction Manual on ICT&SS Management (IM8) (24%)
See all 120 mapped frameworks ↓Maps to 120 other frameworks
What is Sigstore - Software Artifact Signing and Verification and who does it apply to?
Sigstore - Software Artifact Signing and Verification is a compliance framework from International (OpenSSF) with 8 domains and 17 controls. Sigstore is a set of open-source tools for signing, verifying, and protecting software artifacts. Created by Google, Red Hat, and Purdue University, now under the OpenSSF. Components: Cosign (container and artifact signing), Fulcio (certificate authority for ephemeral certificates), Rekor (transparency log), and Gitsign (git commit signing). Sigstore enables keyless signing using OIDC identity (GitHub, Google, Microsoft accounts). Used by npm, PyPI, Kubernetes, Homebrew, and major package ecosystems. Over 20 million signatures in the public Rekor transparency log. Adopted by Kubernetes as the standard for supply chain security. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does Sigstore - Software Artifact Signing and Verification actually require?
Sigstore - Software Artifact Signing and Verification has 17 controls organised across 8 domains. The largest domains are Sigstore: Cosign Signing and Storage (4 controls), Sigstore: Fulcio Certificate Authority (3 controls), Sigstore: Rekor Transparency Log (3 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of Sigstore - Software Artifact Signing and Verification do I already cover?
Sigstore - Software Artifact Signing and Verification maps to 120 other compliance frameworks. The top mapping partners are NIST SP 800-171A Rev 3 - Assessing CUI Security Requirements (29% coverage), NIST SP 800-53 Rev 5 (29% coverage), South Korea ISMS-P (29% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement Sigstore - Software Artifact Signing and Verification?
Start your Sigstore - Software Artifact Signing and Verification compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about Sigstore - Software Artifact Signing and Verification requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 17 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 686 frameworks.
Get Started Free →Free forever — no credit card required