Comparison tables

Federal software security attestation after M-26-05: what replaced M-22-18 and M-23-16

Federal software security attestation after M-26-05: what replaced M-22-18 and M-23-16 Each number links to the cell's source. Cells checked unless the cell shows another date.
InstrumentIssuerDutyWhoStatus
OMB M-22-18, Enhancing the Security of the Software Supply Chain through Secure Software Development Practices, and its companion M-23-161IssuerOffice of Management and Budget1DutyWith Executive Order 14028, required development of an attestation form in which software producers serving the federal government confirm they implement specific security practices3WhoProducers of software used by the federal government3StatusRescinded by M-26-05 on January 23, 20261
OMB M-26-05, Adopting a Risk-based Approach to Software and Hardware Security1IssuerOffice of Management and Budget, January 23, 20261DutyKeep a complete inventory of software and hardware; develop software and hardware assurance policies and processes that match risk determinations and mission needs1WhoHeads of executive departments and agencies1StatusCISA's attestation form page summarizes agencies' duties under M-26-05, as checked 2026-11-142
Secure Software Development Attestation Form (common form)2IssuerCISA, developed with OMB; released March 11, 20243DutyThe producer attests to selected practices from NIST SP 800-218, SSDF Version 1.12WhoOptional: under M-26-05 agencies may choose to use it1StatusCISA's earlier page for the form and its Repository for Software Attestations and Artifacts is marked Archived Content, as checked 2026-11-143
Contract term requiring a current software bill of materials (SBOM)1IssuerNamed in OMB M-26-051DutyProducer provides a current SBOM on request; for a cloud platform, an SBOM of the runtime production environment1WhoOptional: agencies may choose to adopt the term1StatusM-26-05 points to CISA's 2025 Minimum Elements for an SBOM, published in draft on August 22, 20251
NIST SP 800-218, Secure Software Development Framework (SSDF) Version 1.1 (final; supersedes CSWP 13)4IssuerNational Institute of Standards and Technology, February 20224DutyRecommends a core set of high-level secure software development practices to build into each software development life cycle4WhoSoftware producers4StatusM-26-05 lists it, with its associated appendices, as a reference agencies can use1
NIST SP 800-218 Rev. 1, SSDF Version 1.2 (initial public draft)5IssuerNational Institute of Standards and Technology, December 17, 20255DutyDescribes new and improved practices, tasks and examples for secure and reliable development, delivery and improvement of software5WhoSoftware producers5StatusDraft; comments closed January 30, 2026. Its document history lists only the December 17, 2025 draft, as checked 2026-11-145
Secure by Design Pledge6IssuerCybersecurity and Infrastructure Security Agency6DutyGood-faith effort over the following year toward seven goals; where progress is measurable, publicly document it within one year of signing6WhoEnterprise software manufacturers: on-premises software, cloud services and SaaS. Physical products such as IoT devices and consumer products are not in scope6StatusVoluntary and not legally binding; CISA's page still invites manufacturers to sign, as checked 2026-11-146

Get the data: CSV · JSON

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.

Method

Federal instruments on secure software development compared on issuer, duty, who it reaches and status. Cells were taken from the M-26-05 PDF, CISA's current and archived pages for the attestation form, NIST's CSRC pages for SP 800-218 and its Rev. 1 draft, and CISA's Secure by Design Pledge page, all opened on 2026-11-14. The M-22-18 and M-23-16 PDFs were no longer at their former whitehouse.gov addresses, so that row relies on M-26-05 and CISA's archived page.

Omitted

What was left out, and why.

  • OMB M-22-18, Enhancing the Security of the Software Supply Chain through Secure Software Development Practices, and its companion M-23-16 · Issuer: The issue dates of M-22-18 and M-23-16 are left out: their PDFs were no longer at their former whitehouse.gov addresses on 2026-11-14, and M-26-05 does not state them.
  • NIST SP 800-218 Rev. 1, SSDF Version 1.2 (initial public draft) · Status: Whether NIST will finalize Rev. 1, or when, is not stated on its page.

Notes

  • M-26-05 says agencies may also reference CISA's Hardware Bill of Materials (HBOM) Framework for Supply Chain Risk Management (September 2023).

Sources

  1. Office of Management and Budget, Executive Office of the President. M-26-05, Adopting a Risk-based Approach to Software and Hardware Security. Checked .
  2. Cybersecurity and Infrastructure Security Agency. Secure Software Development Attestation Form (resource page). Checked .
  3. Cybersecurity and Infrastructure Security Agency. Secure Software Development Attestation Form (archived page). Checked .
  4. National Institute of Standards and Technology. NIST SP 800-218, Secure Software Development Framework (SSDF) Version 1.1. Checked .
  5. National Institute of Standards and Technology. NIST SP 800-218 Rev. 1 (Initial Public Draft), SSDF Version 1.2. Checked .
  6. Cybersecurity and Infrastructure Security Agency. Secure by Design Pledge. Checked .

How we source and check every fact: Editorial standards · Corrections

Last reviewed .

Spotted an error? Tell us and we will check it and correct the table where needed.