COPRSETR WORKSHEET
Secure development claim matrix
CISA software attestation · Step 2 · Connect each claim to operating evidence- Who prepares it
- Product security + engineering and release owners
- When to prepare it
- Before the internal signature review
Template fields
Fill in each section with details from your work.
- Fictional claim review
- [Add details here]
Gather first
- Scoped form or buyer instructions
- SSDF references
- Workflow evidence
- Release history
- Vulnerability records
How to prepare it
- Record the claim, requirement source, matching SSDF practice, responsible engineer, product boundary and relevant evidence period.
- Attach a restricted reference to operational records and explain what each record proves. Document separate evidence where different deployment environments have their own approvals.
- Ask a second reviewer to reproduce the chain from an example product release back to the evidence. Escalate any unsupported claim before signature.
Review
Every claim has product-specific support and an identified reviewer.
Handoff
Share the reviewed evidence index and open issues with the signer.