# M-26-05: Adopting a Risk-based Approach to Software and Hardware Security

**In short:** M-26-05 rescinds M-22-18 and its companion M-23-16, which required agencies to obtain a self-attestation of secure development practices from software producers before using their software. 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. Agencies may choose to use the government-wide secure software development resources developed under M-22-18, such as the Secure Software Development Attestation Form, and may adopt contract terms requiring a current software bill of materials on request. OMB issued the memorandum on January 23, 2026.

OMB Memorandum M-26-05 · Government · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

## At a glance

- Citation: OMB Memorandum M-26-05
- Issued by: Office of Management and Budget
- Type: Memorandum
- Status: Effective (as of November 14, 2026) [2]
- Applies to: Heads of executive departments and agencies.
- Jurisdiction: United States (federal)

## Key dates

Each date ends with the number of its source in "Sources". Dates were checked on November 14, 2026 unless the row gives another date.

| Date | Kind | What | Source |
|---|---|---|---|
| September 14, 2022 | Published | M-22-18, the attestation memorandum this one rescinds, issued | [3] |
| June 9, 2023 | Published | M-23-16, the companion update to M-22-18, also rescinded, issued | [4] |
| January 23, 2026 | Published | Memorandum issued, rescinding M-22-18 and M-23-16 | [1] |

## What it changed

OMB states that M-22-18 imposed unproven and burdensome software accounting processes that prioritized compliance over genuine security investments, and that it did not account for threats posed by insecure hardware. The new memorandum states that each agency head is responsible for assuring the security of software and hardware permitted to operate on the agency network, says each agency should validate provider security based on a comprehensive risk assessment, and brings hardware into scope.

## Not listed

- The memorandum sets no dated deadlines for agencies. [1]

## 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 (January 23, 2026). <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. Office of Management and Budget, Executive Office of the President. Memoranda (OMB page listing memoranda issued from 2025 onward). <https://www.whitehouse.gov/omb/information-resources/guidance/memoranda/> Checked November 14, 2026.
3. Office of Management and Budget, Executive Office of the President. M-22-18, Enhancing the Security of the Software Supply Chain through Secure Software Development Practices (September 14, 2022), Internet Archive copy captured January 19, 2026. <https://web.archive.org/web/20260119095057/https://www.whitehouse.gov/wp-content/uploads/2022/09/M-22-18.pdf> Checked November 14, 2026.
4. Office of Management and Budget, Executive Office of the President. M-23-16, Update to Memorandum M-22-18 (June 9, 2023), Internet Archive copy captured January 20, 2026. <https://web.archive.org/web/20260120132337/https://www.whitehouse.gov/wp-content/uploads/2023/06/M-23-16-Update-to-M-22-18-Enhancing-Software-Security.pdf> Checked November 14, 2026.

Last reviewed: November 14, 2026
Canonical URL: <https://insights.moraph.com/rules/omb-m-26-05>
Publisher: Moraph Insights
