OMB M-26-05 and the end of the federal secure software attestation requirement, explained
OMB Memorandum M-26-05 rescinded M-22-18 and M-23-16 in January 2026, so a single government-wide attestation no longer applies; each agency now sets software and hardware assurance terms from its own risk determinations, with the attestation form and SBOM terms as options.
Under OMB Memorandum M-22-18, a company selling software to a federal agency faced one government-wide request: attest to secure development practices, on a common form CISA released in 2024 [1] [4]. OMB Memorandum M-26-05, dated January 23, 2026, removed that single requirement and left each agency to set its own assurance terms [1]. The change reaches software and hardware producers in every sector that sell to agencies. This explainer covers three parts: what the rescinded regime asked for, what the 2025 executive order and the 2026 memo changed, and what agencies are still told to do, with the status of each reference document they are pointed to.
What the rescinded regime asked for
Executive Order 14028 directed the development of guidance on secure software development practices and on artifacts that demonstrate them, and directed OMB to require agencies to use only software from providers that attest to those practices [2]. CISA states that Executive Order 14028, M-22-18, Enhancing the Security of the Software Supply Chain through Secure Software Development Practices, and M-23-16, an update to M-22-18, required development of an attestation form in which software producers serving the federal government confirm specific security practices [4]. M-26-05 calls M-23-16 a companion policy to M-22-18 [1].
CISA released the Secure Software Development Attestation Form on March 11, 2024. It was developed with OMB and based on practices in NIST’s Secure Software Development Framework (SSDF), and producers could submit it by email or through CISA’s online Repository for Software Attestations and Artifacts [4]. The SSDF itself is NIST SP 800-218, version 1.1, published in February 2022: a core set of high-level secure development practices that software purchasers can also use in acquisition [5].
Executive Order 14144, signed January 16, 2025, would have gone further. It told OMB to recommend contract language to the FAR Council requiring software providers to submit machine-readable attestations, high-level artifacts to validate them, and a list of their federal civilian agency customers through CISA’s repository. It told the FAR Council to act on those recommendations within 120 days of receiving them [2].
What changed in 2025 and 2026
June 2025. Executive Order 14306, signed June 6, 2025, struck subsections 2(a) and 2(b) of Executive Order 14144, the subsections that carried the attestation and FAR language, and renumbered the rest of section 2 [3] [2]. It then rewrote the renumbered subsection 2(c) to give NIST three tasks [3]:
- by August 1, 2025, a consortium with industry at the National Cybersecurity Center of Excellence to develop guidance demonstrating SSDF-based practices;
- by September 2, 2025, an update to SP 800-53 on securely and reliably deploying patches and updates; and
- by December 1, 2025, a preliminary update to the SSDF, with a final version within 120 days of publishing the preliminary update.
January 2026. M-26-05 rescinds M-22-18 and M-23-16 [1]. OMB’s stated reasons are that M-22-18 imposed unproven and burdensome software accounting processes that put compliance ahead of security investment, diverted agencies from tailored assurance requirements, and neglected the threat from insecure hardware [1]. The memo states that each agency head bears final responsibility for the security of software and hardware allowed on the agency’s network, that there is no one-size-fits-all method, and that each agency should validate provider security using secure development principles and a comprehensive risk assessment [1].
What agencies are still told to do
M-26-05 keeps two duties and offers several options [1]:
- agencies shall continue to maintain a complete inventory of software and hardware;
- agencies shall develop software and hardware assurance policies and processes that match their risk determinations and mission needs;
- agencies may choose to keep using the government-wide resources developed under M-22-18, such as the attestation form;
- agencies may adopt contract terms requiring a software producer to provide a current software bill of materials (SBOM) on request, and for a cloud platform such a term should specify an SBOM of the runtime production environment; and
- agencies can refer to NIST SP 800-218, CISA’s 2025 minimum elements for an SBOM, and CISA’s hardware bill of materials framework of September 2023.
The memo sets no deadline and names no form, repository or format that all agencies must use [1].
Where the reference documents stand
Each document the memo points to has its own status, and two of them read differently from the memo.
- The attestation form. M-26-05 says agencies may still use it [1]. As checked on November 14, 2026, CISA’s page for the form carries an “Archived Content” banner saying the archive contains outdated information that may not reflect current policy or programs [4]. The memo permits the form; CISA’s page labels it archived.
- The SSDF. The memo cites SP 800-218 [1], and NIST’s page for it still shows version 1.1 of February 2022 [5]. NIST published SP 800-218 Rev. 1, SSDF version 1.2, as an initial public draft on December 17, 2025, with comments due by January 30, 2026 [6]. Executive Order 14306 called for a final version within 120 days of the preliminary update [3]. As checked on November 14, 2026, NIST’s page for Rev. 1 still shows it as an initial public draft with the comment period closed [6].
- SBOM minimum elements. CISA published its draft 2025 minimum elements on August 22, 2025, building on the 2021 NTIA minimum elements, with public comment until October 3, 2025 [7]. The memo itself describes it as published in draft form [1], and as checked on November 14, 2026 CISA’s page still describes it as a draft offered for comment before it is finalized [7].
The procurement effect
Under M-22-18 a producer could prepare one attestation for every civilian agency. Under M-26-05 the evidence an agency asks for depends on that agency’s own risk determinations [1]. In our view, producers selling to several agencies should expect different requests from different buyers: some may keep asking for the CISA form, some may write SBOM-on-request terms into contracts, and some may ask about hardware, which the memo now names alongside software. The cost moves from completing one standard form to answering varied questionnaires and contract clauses, each priced into a bid. Our comparison of federal software security attestation after M-26-05 sets out what replaced M-22-18 and M-23-16.
In our view, the memo’s reference set also matters beyond government buyers. NIST describes the SSDF as a common vocabulary that software purchasers and consumers can use with suppliers in acquisition [5], and CISA describes its SBOM elements as guidance to help agencies and organizations manage software risk [7]. Banks, health systems and other regulated buyers that already ask for SSDF-aligned practices or SBOMs in their own contracts will find those documents still current reference points, with version 1.2 of the SSDF and the 2025 SBOM elements both still marked as drafts as of November 14, 2026 [6] [7].
What a producer must provide to a given agency is set by that agency’s solicitation and contract. Producers should check each solicitation and confirm with counsel which terms apply.
This explainer describes the memo and its references; it is not legal advice.
Moraph’s teams help organizations with work like this. See our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.