M-26-05: Adopting a Risk-based Approach to Software and Hardware Security
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.
- Sectors
- Government
- Jurisdiction
- United States (federal)
Key dates
| Date | Kind | What | When | Source |
|---|---|---|---|---|
| KindPublished | WhatM-22-18, the attestation memorandum this one rescinds, issued | WhenPassed | Source3 | |
| KindPublished | WhatM-23-16, the companion update to M-22-18, also rescinded, issued | WhenPassed | Source4 | |
| KindPublished | WhatMemorandum issued, rescinding M-22-18 and M-23-16 | WhenPassed | Source1 |
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
- 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). Checked .
- Office of Management and Budget, Executive Office of the President. Memoranda (OMB page listing memoranda issued from 2025 onward). Checked .
- 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. Checked .
- 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. Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed . Statuses and dates change: check the source before you rely on one.
Spotted an error? Tell us and we will check it and correct the entry where needed.