Template library
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

Worked example

This example uses fictional details. Use the same fields with evidence from your work.

Fictional claim review
The form reviewer traces the release to its signed build record and approval. The staging pipeline is omitted from the evidence because the claim covers software delivered to the agency.

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.

Review

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

Handoff

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

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes