# Secure development claim matrix

CISA software attestation | Blank worksheet

Step: Connect each claim to operating evidence
Owner: Product security + engineering and release owners
When: Before the internal signature review

## Gather first
- Scoped form or buyer instructions
- SSDF references
- Workflow evidence
- Release history
- Vulnerability records

## How to prepare it
1. Record the claim, requirement source, matching SSDF practice, responsible engineer, product boundary and relevant evidence period.
2. Attach a restricted reference to operational records and explain what each record proves. Document separate evidence where different deployment environments have their own approvals.
3. Ask a second reviewer to reproduce the chain from an example product release back to the evidence. Escalate any unsupported claim before signature.

## Fill in

### Fictional claim review
[Add details here]

## Review
Every claim has product-specific support and an identified reviewer.

## Handoff
Share the reviewed evidence index and open issues with the signer.

Use the current rules and any prescribed forms for your engagement.
