CISA software attestation
Federal secure software attestation after OMB M-26-05
Find out whether your federal buyer asks for the CISA attestation form and build a release evidence package the signer can review. Use the same process to respond to agency-specific requests for software assurance.
- Issuing authority
- U.S. Office of Management and Budget (OMB), CISA and the purchasing agency
- Timing
- Use the buyer’s deadline and release or change terms. Determine scope before pricing or promising an attestation. Leave time for an evidence review and signature before submission. Confirm the date and channel for responding to a later request for an updated software bill of materials (SBOM).
- Reviewed
- Inside this guide
- 4 steps · 4 templates
Who it applies to
Federal agency procurement and software assurance teams, and vendors responding to their requirements. OMB memorandum M-26-05 rescinded M-22-18 and M-23-16 on January 23, 2026. Under M-26-05, an agency may choose the common CISA form or use other assurance measures based on assessed risk. Confirm the actual solicitation, contract and agency instructions.
What you’ll produce
A written applicability decision, scoped and traceable release evidence, approved responses to gaps, and a signed submission and receipt when required by the agency.
NIST lists SSDF v1.1 as final and v1.2 as a draft. Use the version required by the buyer. A supplier’s attestation represents the claims in the signed form for the stated scope. When an agency adopts an SBOM-on-request term for a cloud platform, OMB says that agency should specify production runtime coverage. Budget for evidence upkeep, release inventory and review by engineering and counsel.
Run the project
Go to the roadmapDecisions for leadership
- Which risks will we reduce and how will we measure it?
- Set a target for each priority service or outcome. Use a current baseline to decide the investment needed, what can be phased in, and who accepts remaining risk.
- Who will do the work and who can sign?
- Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
- Which deadlines can we promise?
- Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
- Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
- Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target.
- Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor progress against the target, failed control tests and gaps that leave a critical service exposed.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
CISA software attestation kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Capture the agency requirement · Contracting lead + agency buyer + counsel [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
- Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
- Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
- Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
- Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
How this works in practice
Two questions to check scope
- What evidence does the actual agency request?
- Which products, versions and production environments does the request cover?
- Who owns the controls, who can sign, and who must receive renewal or change notices?
Worked scenario
A federal buyer requests a common form and a production runtime SBOM on request. The vendor finds that its prior declaration covers only its commercial deployment. It confirms the federal tenant and production components with the buyer, gathers evidence scoped to that tenant, and routes it for sign-off.
What to read next
- FedRAMP
Check with your agency if it also requires cloud authorization or certification for the service.
Official milestones
See the deadline calendar- 23 Jan 2026
OMB M-26-05 issued
OMB rescinded the two previous memoranda and allowed agencies to choose assurance measures for their needs.
Official reference (opens in a new tab)
- 01Capture the agency requirement, Contracting lead + agency buyer + counsel, about 4 days
- 02Connect each claim to operating evidence, Product security + engineering and release owners, about 10 days
- 03Prepare and validate requested SBOM evidence, Release engineering + product security + vendor management, about 5 days
- 04Review, sign and track changes, Authorized signer + legal + contracts lead, about 4 days
Step by step
Checklist, instructions and 4 templates.
View plan as a table
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Capture the agency requirement | Contracting lead + agency buyer + counsel | Before proposal, renewal or any attestation commitment | Set a start date | Agency applicability and scope memo | Open |
| Connect each claim to operating evidence | Product security + engineering and release owners | Before the internal signature review | Set a start date | Secure development claim matrix | Open |
| Prepare and validate requested SBOM evidence | Release engineering + product security + vendor management | Before an applicable submission or request deadline | Set a start date | Release inventory and SBOM review | Open |
| Review, sign and track changes | Authorized signer + legal + contracts lead | Before submission and at covered release or contract changes | Set a start date | Signature decision and submission log | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
- 01
Capture the agency requirement
Collect the solicitation, signed contract and amendments, plus any agency instructions. Record the exact artifact the buyer requires, the product scope, due date, channel, eligible signer and any change duty. Resolve conflicting instructions in writing.
What to produce
Agency applicability and scope memoWritten contract requirement memo
Gather first
- Solicitation
- Contract and amendments
- Agency security instructions
- Product and deployment inventory
- OMB M-26-05
How to prepare it
- Copy the exact requirement and its source reference. Record the required evidence, recipient, deadline, whether signature is requested and who can sign.
- List covered product editions, versions, agencies and hosting deployments. Identify unresolved scope or conflicts and obtain written clarification.
- Attach the agency answer and a dated decision, then assign owners and reminders for each deliverable.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional buyer requirement
- The federal tenant and version 4.x are in scope. The buyer requests the common form at award and a production runtime SBOM on written request. The contract owner saves the supporting clause and confirms the delivery channel.
Check before handing it over
Legal, engineering and sales can cite the same source for what the team must deliver.
Send the memo and deadlines to evidence owners.
- 02
Connect each claim to operating evidence
Match each form statement or agency requirement to the applicable SSDF practices and product boundary. Use dated evidence for protected build environments, source and release integrity, vulnerability response and third-party components. Record gaps and owners.
What to produce
Secure development claim matrixClaim and evidence spreadsheet
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.
Worked example
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.
Check before handing it over
Every claim has product-specific support and an identified reviewer.
Share the reviewed evidence index and open issues with the signer.
- 03
Prepare and validate requested SBOM evidence
Determine the buyer’s requested scope, format and exchange channel. Generate an inventory from the relevant release and verify component versions, coverage and output format against the deployed environment. Record limitations and the process for refreshing it.
What to produce
Release inventory and SBOM reviewMachine-readable SBOM and quality review memo
Gather first
- Buyer requirements
- Deployment manifest
- Dependency outputs
- Release inventory
- Distribution instructions
How to prepare it
- Confirm format, fields, version and scope with the buyer. For a cloud runtime request, identify production components and images that actually run for the covered service.
- Match inventory objects to immutable release references, component identities and versions. Check output against the requested syntax and compare a sample to deployment records.
- Document gaps, what is excluded and when the inventory was generated. Store approved output and send it through the required channel only after a handling review.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional review result
- The initial inventory reflects the web image but misses a production job image. The owner adds the missing components, reruns validation and records both image references in the review memo.
Check before handing it over
The software inventory can be tied to the intended product release and inspected by the buyer.
Save the approved artifact and receipt with the release record.
- 04
Review, sign and track changes
Require a supportable evidence trail for each signed claim. Escalate gaps to the agency using the authorized process. Record what the signer approved and submit via the buyer’s specified channel. Keep a receipt and schedule contract-defined updates.
What to produce
Signature decision and submission logSign-off checklist and submission register
Gather first
- Approved evidence matrix
- Current agency instructions
- Authorized signer list
- Outstanding findings
- Delivery receipt
How to prepare it
- Match the final artifact to the agency’s scope and the evidence version. Route unresolved claims to counsel and the contracting officer for an approved disposition.
- Provide the signer with the claim summary, covered versions, remediation decisions and official artifact. Keep the signed copy in the controlled repository.
- Record the submission and receipt, and schedule review for covered changes, renewals and deadlines. Assign an alternate contact.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional signature decision
- Legal identifies an unsupported claim for one deployment. Contracts asks the agency whether narrower scope is acceptable and holds signature until the reply and evidence agree.
Check before handing it over
The archive shows who signed, what the buyer received and when the next review is due.
Give the account owner a copy of the receipt and the controlled change checklist.
Official sources
- OMB M-26-05, current federal policy (opens in a new tab)
- CISA common form and signing instructions (opens in a new tab)
- NIST SSDF v1.1 (opens in a new tab)
- NIST SSDF publication status (opens in a new tab)
- GAO 2026 federal cloud procurement review (opens in a new tab)