[Analysis] OMB M-26-05: The Pivot to HBOM & Risk-Based Security

White House rescinds software security mandates (M-22-18) for a risk-based approach. Learn about the new Hardware Bill of Materials (HBOM) framework.

OMB M-26-05 replaces the earlier software security mandate set out in M-22-18 with a risk-based model. Agencies are no longer steered toward one-size-fits-all software attestation and control checklists as the primary path to compliance. Instead, they are expected to size security effort to the sensitivity of the system, the criticality of the mission, and the actual exposure of the supply chain involved.

What happened

Read the source's account next to the product docs, not instead of them. Names and figures in the lede are the ones we can stand behind; everything else below is how teams usually absorb a story like this. If a number, ship date, or quote is not in the source excerpt, it is not in this briefing. That is deliberate — day-one coverage is where invented specifics do the most damage.

White House rescinds software security mandates (M-22-18) for a risk-based approach. Learn about the new Hardware Bill of Materials (HBOM) framework.

Under the hood this is a systems change, not a press-release adjective. Ask what surface area moved — API, policy, hardware, model behavior, or go-to-market — and which of those you actually ship against. A useful working question: if you had to draw the before/after on a whiteboard, which box would you erase? That is the mechanism. Everything else is packaging.

How it works

OMB M-26-05 replaces the earlier software security mandate set out in M-22-18 with a risk-based model. Agencies are no longer steered toward one-size-fits-all software attestation and control checklists as the primary path to compliance.

If you build on or compete with the parties named in [Analysis] OMB M-26-05: The Pivot to HBOM & Risk-Based Security, the practical hit is on roadmap sequencing and risk reviews this quarter, not on a vague 'future of the industry'. Put one owner on the story, give them a day to read the primary material, and decide whether this is a this-sprint item, a this-quarter item, or noise.

Instead, they are expected to size security effort to the sensitivity of the system, the criticality of the mission, and the actual exposure of the supply chain involved. That shift does not mean software security becomes optional.

Why it matters

Incumbents, customers, and adjacent open-source projects do not feel this equally. Map the change to your own stack: what you operate, what you buy, and what you will have to explain to a security, legal, or finance review. Partners and resellers often feel it before the end user does — check those contracts before you assume nothing moved.

It means attestation, scanning, and vendor documentation compete with other controls for attention. Teams should treat former M-22-18 artifacts as inputs to a risk decision, not as a standing checklist that applies equally to every system.

Treat the next two weeks as a verification window. Watch the vendor's own changelog, any regulator or standards follow-up, and whether a competitor ships a matching capability. Do not change production on day-one coverage alone. If nothing new is published in that window, the story was smaller than the headline.

Who is affected

M-26-05 elevates the Hardware Bill of Materials as a first-class supply-chain artifact. An HBOM is an inventory of hardware components—boards, chips, firmware modules, peripherals, and subassemblies—that make up a device or system.

A 3–5 minute news post is a briefing, not a runbook. Keep the source and the vendor's primary page in another tab, quote only what they printed, and write down the single decision this story forces (upgrade, wait, or ignore) before you Slack it to the rest of the team. If you need more than that decision, you want the primary docs or a later engineering deep-dive — not another recap of [Analysis] OMB M-26-05: The Pivot to HBOM & Risk-Based Security.

What to watch next

See the original reporting on [Analysis] OMB M-26-05: The Pivot to HBOM & Risk-Based Security for primary quotes. Confirm vendor docs before changing production systems.