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

**In short:** OMB M-26-05, dated January 23, 2026, rescinded M-22-18 and its companion M-23-16. Agencies must still keep a complete inventory of software and hardware and develop assurance policies and processes that match their risk determinations and mission needs; they may choose to use the Secure Software Development Attestation Form and may adopt contract terms that require a current SBOM on request. NIST SP 800-218 (SSDF Version 1.1, February 2022) is final; Version 1.2 (SP 800-218 Rev. 1) is an initial public draft whose comment period closed January 30, 2026. CISA's Secure by Design Pledge is voluntary and not legally binding.

Government · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. <https://creativecommons.org/licenses/by/4.0/>. Attribution: "Moraph Insights", <https://insights.moraph.com/compare/federal-software-security-attestation>.

## The table

Each cell ends with the number of its source in "Sources". Cells were checked on November 14, 2026 unless the cell gives another date. Data: <https://insights.moraph.com/compare/federal-software-security-attestation.csv> (CSV), <https://insights.moraph.com/compare/federal-software-security-attestation.json> (JSON).

| Instrument | Issuer | Duty | Who | Status |
|---|---|---|---|---|
| OMB M-22-18, Enhancing the Security of the Software Supply Chain through Secure Software Development Practices, and its companion M-23-16 [1] | Office of Management and Budget [1] | With Executive Order 14028, required development of an attestation form in which software producers serving the federal government confirm they implement specific security practices [3] | Producers of software used by the federal government [3] | Rescinded by M-26-05 on January 23, 2026 [1] |
| OMB M-26-05, Adopting a Risk-based Approach to Software and Hardware Security [1] | Office of Management and Budget, January 23, 2026 [1] | Keep a complete inventory of software and hardware; develop software and hardware assurance policies and processes that match risk determinations and mission needs [1] | Heads of executive departments and agencies [1] | CISA's attestation form page summarizes agencies' duties under M-26-05, as checked 2026-11-14 [2] |
| Secure Software Development Attestation Form (common form) [2] | CISA, developed with OMB; released March 11, 2024 [3] | The producer attests to selected practices from NIST SP 800-218, SSDF Version 1.1 [2] | Optional: under M-26-05 agencies may choose to use it [1] | CISA's earlier page for the form and its Repository for Software Attestations and Artifacts is marked Archived Content, as checked 2026-11-14 [3] |
| Contract term requiring a current software bill of materials (SBOM) [1] | Named in OMB M-26-05 [1] | Producer provides a current SBOM on request; for a cloud platform, an SBOM of the runtime production environment [1] | Optional: agencies may choose to adopt the term [1] | M-26-05 points to CISA's 2025 Minimum Elements for an SBOM, published in draft on August 22, 2025 [1] |
| NIST SP 800-218, Secure Software Development Framework (SSDF) Version 1.1 (final; supersedes CSWP 13) [4] | National Institute of Standards and Technology, February 2022 [4] | Recommends a core set of high-level secure software development practices to build into each software development life cycle [4] | Software producers [4] | M-26-05 lists it, with its associated appendices, as a reference agencies can use [1] |
| NIST SP 800-218 Rev. 1, SSDF Version 1.2 (initial public draft) [5] | National Institute of Standards and Technology, December 17, 2025 [5] | Describes new and improved practices, tasks and examples for secure and reliable development, delivery and improvement of software [5] | Software producers [5] | Draft; comments closed January 30, 2026. Its document history lists only the December 17, 2025 draft, as checked 2026-11-14 [5] |
| Secure by Design Pledge [6] | Cybersecurity and Infrastructure Security Agency [6] | Good-faith effort over the following year toward seven goals; where progress is measurable, publicly document it within one year of signing [6] | Enterprise software manufacturers: on-premises software, cloud services and SaaS. Physical products such as IoT devices and consumer products are not in scope [6] | Voluntary and not legally binding; CISA's page still invites manufacturers to sign, as checked 2026-11-14 [6] |

## 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

- **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. <https://www.whitehouse.gov/wp-content/uploads/2026/01/M-26-05-Adopting-a-Risk-based-Approach-to-Software-and-Hardware-Security.pdf> Checked November 14, 2026.
2. Cybersecurity and Infrastructure Security Agency. Secure Software Development Attestation Form (resource page). <https://www.cisa.gov/resources-tools/resources/secure-software-development-attestation-form> Checked November 14, 2026.
3. Cybersecurity and Infrastructure Security Agency. Secure Software Development Attestation Form (archived page). <https://www.cisa.gov/secure-software-attestation-form> Checked November 14, 2026.
4. National Institute of Standards and Technology. NIST SP 800-218, Secure Software Development Framework (SSDF) Version 1.1. <https://csrc.nist.gov/pubs/sp/800/218/final> Checked November 14, 2026.
5. National Institute of Standards and Technology. NIST SP 800-218 Rev. 1 (Initial Public Draft), SSDF Version 1.2. <https://csrc.nist.gov/pubs/sp/800/218/r1/ipd> Checked November 14, 2026.
6. Cybersecurity and Infrastructure Security Agency. Secure by Design Pledge. <https://www.cisa.gov/securebydesign/pledge> Checked November 14, 2026.

Last reviewed: November 14, 2026
Canonical URL: <https://insights.moraph.com/compare/federal-software-security-attestation>
Publisher: Moraph Insights
