A signature is not an approval policy
Verify who signed an artifact and whether that identity was allowed to authorize it.
Research note · November 14, 2026Research question
What does a valid signature establish, and what must a consumer decide separately?
Method
- Choose a controlled artifact and two test identities. Verify signatures from both identities, then apply an explicit policy that accepts only one for the intended project or release channel.
- Record certificate identity, issuer and verification material alongside the artifact digest. Avoid treating any cryptographically valid signature as sufficient authorization.
- Test an unexpected identity, a changed artifact and missing verification material separately. Preserve the verification error and policy decision as distinct results so a reviewer can locate the failure.
Records to retain
- Artifact digest
- Signer identity and issuer
- Verification policy revision
- Cryptographic and authorization outcomes
Source basis
Sigstore’s security model ties short-lived signing certificates to identities and uses transparency infrastructure to support verification. Consumers still need expectations about acceptable identities; transparency does not make every published signature authorized.
Interpretation & limits
This is a protocol for evaluating signature policy, not a claim that Prompto implements Sigstore verification. A trusted signer can still sign an unsuitable artifact.
Next experiments
- Create a fixture where the signature is valid but the identity is wrong.
- Specify how trust-policy changes are reviewed and recorded.
References
Technical reference
Implementation details supporting this note, drawn directly from the maintained documentation. These are technical references, not additional papers or new experimental results. Expand a topic to inspect its method, fields and limits.