Cybersecurity glossary
What is Artifact Signing?
Learn what artifact signing is, why it extends beyond traditional code signing, and how signatures protect packages, container images, SBOMs, and attestations.
Definition
Artifact signing is the cryptographic signing of software supply chain outputs such as packages, container images, binaries, SBOMs, provenance, and attestations so consumers can verify origin and integrity.
Why artifact signing matters
Software is no longer delivered as a single executable. A release can include source archives, packages, container images, SBOMs, provenance files, signatures, attestations, and policy metadata spread across registries and mirrors.
Artifact signing gives each important supply chain output its own integrity check. That distinction matters: code signing is one case, while artifact signing covers the broader set of objects that build, security, and deployment systems trust.
What artifact signing protects
Packages
Language, OS, and application packages can be verified before installation or promotion.
Container images
Image digests can be signed so mutable tags do not become the trust anchor.
SBOMs
Component inventories can be signed to prevent tampering after release.
Attestations
Provenance and policy evidence can be signed so downstream systems can rely on it.
How artifact signing works
Produce the artifact
Build or generate the package, image, SBOM, provenance statement, or release file.
Address it immutably
Calculate the artifact digest so the signature binds to exact content, not just a tag or filename.
Sign with trusted identity
Use a protected key, KMS, HSM, or keyless certificate tied to a known publisher or workload.
Publish evidence
Store the signature, certificate, transparency log entry, or attestation where consumers can retrieve it.
Verify before trust
Consumers check the signature, identity, digest, freshness, and policy before install or deploy.
Artifact signing versus code signing
| Concept | Commonly signs | Trust question |
|---|---|---|
| Code signing | Executables, installers, drivers, mobile apps | Did this executable come from the expected publisher and remain unchanged? |
| Artifact signing | Packages, images, archives, SBOMs, provenance, attestations | Can this supply chain object be tied to a trusted identity and exact digest? |
| Provenance signing | Build metadata about source, builder, and parameters | Can I trust the statement describing how this artifact was produced? |
| Repository signing | Indexes, metadata, release channels, package sets | Has the distribution channel served expected metadata and versions? |
Artifact signing checklist
- Sign immutable artifact digests instead of mutable names whenever possible.
- Protect signing authority with short-lived credentials, HSM/KMS, or keyless identity.
- Separate development, test, and production signing identities.
- Sign SBOMs and provenance, not only runtime binaries.
- Record enough identity information for policy engines to make decisions.
- Verify signatures in CI, deployment admission, and package consumption workflows.
- Monitor transparency logs, release repositories, and registries for unexpected signatures.
- Maintain a rotation and revocation plan for compromised signing identities.
The practical takeaway
Artifact Signing is the integrity layer for the objects your software factory emits and consumes. It is broader than code signing because modern trust decisions depend on packages, images, SBOMs, and attestations as well as executables.
Sign what matters by digest, protect the signing identity, and make verification a required gate before production use.
Related security terms
Code Signing
Traditional signing focused on executable code and publisher identity.
Build Provenance
Signed metadata describing how an artifact was produced.
Supply-chain Levels for Software Artifacts (SLSA)
A framework that uses provenance and controls to improve artifact trust.
Package Hijacking
A distribution attack that signing and verification can help detect.
Software Bill of Materials (SBOM)
A component inventory that can be signed to protect integrity and origin.
Frequently asked questions
What is artifact signing in simple terms?
It is a cryptographic seal placed on a software output so tools can verify who produced it and whether it changed after signing.
How is artifact signing different from code signing?
Code signing usually focuses on executable software such as binaries, installers, and drivers. Artifact signing is broader and can cover packages, container images, SBOMs, provenance, and attestations.
What artifacts should be signed?
Sign release packages, container images, binaries, SBOMs, provenance attestations, policy bundles, and any file that consumers use for trust decisions.
Does signing prove an artifact is safe?
No. Signing proves integrity and identity claims. A signed artifact can still contain vulnerabilities or malicious logic if the signer or build process was compromised.
What is keyless signing?
Keyless signing uses short-lived certificates tied to workload or user identity, often with transparency logs, so long-lived private signing keys do not need to be managed by every project.
Why sign by digest?
Signing a cryptographic digest binds the signature to exact bytes, which avoids ambiguity when tags, filenames, or registry references move.
Where should verification happen?
Verify at publish time, deployment admission, package installation, CI dependency intake, and incident response investigations.
References
Explore authoritative guidance and frameworks related to artifact signing.
Explore every security definition
Return to the glossary to search by term, alias, starting letter, or security category.