Engineers with a laptop at automation test rigs in a bright production hall

SBOM

HBOM (Hardware Bill of Materials): CISA's framework explained

Last updated:

An HBOM (Hardware Bill of Materials) is a structured inventory of the physical components — processors, chipsets, modules, boards — that a product is actually built from, plus the firmware bound to each one, published by CISA's Information and Communications Technology (ICT) Supply Chain Risk Management Task Force as a formal framework on 25 September 2023. Where a software SBOM answers "what code is in this firmware image," an HBOM answers "what physical parts, from which suppliers, make up this product" — a question device buyers, regulators and risk teams increasingly ask separately from the software question.

Key takeaways

  • The firmware link is narrow, though.
  • The framework is explicit that it is voluntary.
  • The framework does not expect every HBOM to carry all 47 fields.
  • Parent-child nesting.

Why does hardware need its own bill of materials?

A software SBOM, built from a firmware image or a build pipeline, inventories libraries, packages and components at the code level — the question Executive Order 14028 and the NTIA/CISA Minimum Elements process were built to answer for software supply chains. It says nothing about the physical hardware a device ships with: which vendor made the main processor, whether a module was sourced from a single-source supplier in a geography a buyer wants to flag, or whether the same radio or security chip recurs across a dozen otherwise-unrelated product lines. CISA's ICT SCRM Task Force built the HBOM Framework to close that specific gap, with a scope that explicitly extends to the firmware tied to each hardware part — the framework's own stated goal, per CISA's press release, is "a consistent and repeatable way for vendors and purchasers to communicate about hardware components, enabling effective risk assessment and mitigation in the supply chain."

The firmware link is narrow, though. Section 1.3 of the framework says it records basic firmware information (the provider of the firmware) but "stops short" of a framework for firmware provenance, and it puts SBOM information out of scope. The two documents sit side by side; neither replaces the other.

What does CISA's framework define?

CISA's HBOM Framework, developed by the Task Force's HBOM Working Group and published 25 September 2023, is structured in four appendices:

Part What it covers
Appendix A — Use cases Three use-case categories (Compliance, Security, Availability) split into eight sub-categories, seven data field categories, and a table mapping which field categories each sub-category needs
Appendix B — Format Parent-child nesting of assemblies, how to separate OEM from contract manufacturer and foundry from assembly-and-test site, and how to handle fields CycloneDX or SPDX cannot carry
Appendix C — Data field taxonomy 47 named fields in seven categories (HBOM header, finished-good product details, entity name, entity location, component part information, component part details, production details), each with a type, example and CycloneDX/SPDX equivalent where one exists
Appendix D — Possible enhancements Open problems: part and entity name resolution, HBOM provenance and integrity, roles, concept of operations, more format mappings

The framework is explicit that it is voluntary. Section 1.2 says purchasers and vendors "can use the HBOM Framework on a voluntary basis", and a footnote in Appendix A adds that using it does not mean a company has complied with any US regulation. It is the same posture the original 2021 NTIA Minimum Elements took for software SBOMs before elements of that model found their way into binding procurement and reporting rules. OMB's January 2026 Memorandum M-26-05 on software and hardware risk management cites the HBOM Framework as a resource agencies should draw on alongside CISA's SBOM guidance — see our attestation form guide for the fuller M-26-05 picture — without converting it into a mandatory HBOM filing requirement in its own right.

Which fields does each use case need?

The framework does not expect every HBOM to carry all 47 fields. Table 4 of the CISA framework PDF maps each use-case sub-category to the field categories it needs. Header information, entity names and component part information are needed for all eight. The others vary:

Category Sub-category Typical question Extra field categories beyond header, entity name and part information
Compliance Government Does any part come from an entity or region a law restricts (for example NDAA section 889 or the UFLPA)? Entity location, finished-good details, part details
Compliance Industry or customer Can we answer a customer's supply-chain questionnaire? Entity location, finished-good details, part details
Compliance Internal and quality Are parts bought only from OEM-authorised sources? Finished-good details, part details
Security Geography and entity level Is anything made by an untrusted entity or in a flagged location? Entity location, finished-good details, part details
Security Product and component level Could a part be counterfeit or compromised? Finished-good details, part details, production details
Availability World events Which products are hit if one region shuts down? Entity location, production details
Availability Clustering: risks Where are our single points of failure? Entity location, production details
Availability Clustering: optimise Where can we consolidate suppliers? Entity location, production details

Source: CISA HBOM Framework (September 2023), Appendix A, Tables 2 and 4.

Two of the examples CISA gives make the point. To check UFLPA exposure, a buyer needs entity names and locations down to component level, because "wholly or in part" reaches sub-tier parts. To assess a city-wide shutdown, a buyer queries the entity-location fields for that city and then uses production details (lead times, the share sourced from each supplier) to judge the impact.

How should an HBOM be structured?

Appendix B gives three conventions:

  • Parent-child nesting. Any product, kit or assembly that breaks down into smaller parts gets its own HBOM, and the HBOMs join through part-level information. CISA's example product needs four HBOMs: the finished good, two assemblies and a kit. In a spreadsheet, one tab per assembly level works.
  • OEM vs manufacturer. FGA_SUPPLIER is the brand owner and FGA_MAIN_MANUFACTURER is whoever builds the product. With a contract manufacturer, these are different companies with different locations, and both are recorded.
  • Semiconductors. For chips, the framework recommends recording the supplier and the fab separately (COMP_SUPPLIER, COMP_MANUFACTURER, COMP_MFG_LOCATION), plus the assembly-and-test supplier and site and the technology node where needed.

Each location appears three ways: as text, as decimal coordinates (_LOC_COORDS) and as an ISO country-and-subdivision code (_LOC_CODE, for example "US-NY").

Where do CycloneDX and SPDX stand today?

Of the two dominant SBOM formats, CycloneDX is the one built to carry hardware data natively. Its own specification repository lists HBOM as one of the bill-of-materials types the format covers, alongside SBOM, SaaSBOM, CBOM and AI/ML-BOM — one data model extended across component types rather than a separate standard per BOM type, the same pattern this guide's AI-BOM and CBOM guides describe for their respective component types. A device component type ("a hardware device such as a processor or chip-set") has existed since CycloneDX 1.0, and a dedicated firmware component type ("a special type of software that provides low-level control over a device's hardware") was added in CycloneDX 1.2 (May 2020) — together, a device component nesting a firmware component is the standard CycloneDX pattern for describing a hardware part and the software bound to it, matching CISA's own framing of hardware-plus-firmware. The CycloneDX 1.6 schema also added a component-level manufacturer, which CISA's 2023 mapping predates.

SPDX has no dedicated hardware profile as of SPDX 3.0.1. Its software profile does offer device ("a chipset, processor, or electronic board") and firmware as primary-purpose values, so a part can be labelled, but supplier sites, fabs and sourcing shares have nowhere standard to go. That is a practical reason vendors building an HBOM today more often reach for CycloneDX.

Even there, the mapping is thin. Counting the "Equivalent CycloneDX field" lines in Appendix C, 10 of the 47 fields have a CycloneDX equivalent and 11 have an SPDX 2.x equivalent: dates and author, product and part names, versions, hashes and manufacturer names. None of the 15 entity-location fields maps to either format. For unmapped fields, Appendix B.2 tells the producer to use user-defined fields (CycloneDX properties) and to agree their meaning with the requester. See our CycloneDX vs SPDX guide for how the two formats compare more broadly.

Worked example: a smart thermostat HBOM

Hypothetical example for illustration: invented part numbers and companies, a three-row extract of a larger HBOM.

CISA field Main SoC Wi-Fi module Mainboard
COMP_MANUFACTURER_PN EX-SOC-210 EX-WM-6 TH-MB-03
COMP_PART_TYPE Semiconductor Radio module Printed circuit board assembly
COMP_MANUFACTURER Example Foundry, Fab 2 Example Radio Co. Example CM Ltd
COMP_MFG_LOC_CODE TW-HSZ VN-HN VN-HN
ASSY_AND_TEST_LOC_CODE MY-07 n/a n/a
COMP_VERSION Rev B HW 1.2, firmware 4.1.7 Rev 3
SUPPLIER_SOURCED_PCTG 1.0 0.6 1.0

The Wi-Fi module's 0.6 tells the buyer a second source supplies the other 40%, which matters for the availability use cases. In CycloneDX the module becomes a device with its firmware nested inside, and the location goes in a user-defined property because no standard field exists:

{
  "type": "device",
  "name": "EX-WM-6",
  "version": "1.2",
  "manufacturer": { "name": "Example Radio Co." },
  "properties": [
    { "name": "hbom:COMP_MFG_LOC_CODE", "value": "VN-HN" },
    { "name": "hbom:SUPPLIER_SOURCED_PCTG", "value": "0.6" }
  ],
  "components": [
    { "type": "firmware", "name": "EX-WM-6 firmware", "version": "4.1.7" }
  ]
}

The hbom: property prefix is this example's own convention, which is exactly what Appendix B.2 means by agreeing user-defined fields with the requester.

Is an HBOM required anywhere?

Not by CISA's name or format. M-26-05 leaves agencies free to set their own hardware assurance policies and lists the framework as a reference. The FCC's Cyber Trust Mark registry does ask about HBOMs: item (10) in paragraph 113 of the FCC's 2024 IoT labelling order requires disclosure of "whether the manufacturer maintains" an HBOM and/or an SBOM, a yes-or-no disclosure rather than publication. See our PSTI and Cyber Trust Mark guide. Most real demand comes from buyers' contracts and supply-chain questionnaires.

What are the common pitfalls?

  • One part, several names. Appendix D puts this first among its open problems: the same chip under a marketing name and a part number, or with and without hyphens. Normalise to the manufacturer part number and keep aliases.
  • One company, several names. "Example Corp" and "Example Corporation", plus subsidiaries and acquisitions. Restrictions such as NDAA section 889 extend to affiliates, so record the legal entity.
  • Stopping at the top level. A module or assembly listed as a single line hides the chips inside, which is where the compliance and fab-location questions live.
  • Treating the HBOM as permanent. The framework captures information at the time of sale; a new product version or a supplier change needs a new HBOM.
  • Dropping unmapped fields when converting to CycloneDX or SPDX. Carry them as agreed properties instead.

A workable starting point

  1. Start from what you can verify today: the main processor, any security or crypto chip, radio/connectivity modules, and the board(s) they sit on — the component types CISA's framework and CycloneDX's device type both treat as the core of a hardware inventory.
  2. Pair every hardware component with its firmware, the same device-plus-firmware pairing CISA's framework and CycloneDX's device/firmware component types both model, rather than tracking hardware and software inventories as unrelated documents.
  3. Record entity and location data for key components, not just part numbers — CISA's taxonomy devotes real weight to supplier identity and geography, the fields a buyer doing supply-chain-risk review will ask for first.
  4. Pick CycloneDX over SPDXif you need one machine-readable format that already has a named path for hardware, software and (if relevant) cryptographic and AI components in the same document — see CycloneDX vs SPDX.
  5. Treat it as voluntary but increasingly expected, not a regulatory filing — buyers and OMB guidance alike are starting to ask for it as a supply-chain-risk artifact even though no rule requires the CISA format by name today.

An HBOM only has value once it's actually populated from real procurement and bill-of-materials data, which is exactly where most device makers' hardware records are weakest — scattered across supplier POs and CAD exports rather than a structured, machine-readable document. SoftWSP covers two parts of that picture. Its firmware scan extracts an SBOM from a firmware image without source access. Its component-list analysis reads a bill of materials spreadsheet (vendor, model, firmware version) and writes each hardware row as a CycloneDX 1.6 device component with a CPE candidate and a confidence level. Both are matched against NVD, CISA KEV, FIRST EPSS and CISA's ICS advisories, with an AI-drafted, cited report for an engineer to review. SoftWSP does not fill in CISA's supplier-location or production fields; those come from your procurement records. See device firmware security and machine builders.

This guide draws on CISA's HBOM Framework PDF and press release, the CycloneDX and SPDX specifications, OMB M-26-05 and FCC 24-26. It is not a substitute for a supply-chain counsel's review of a specific procurement requirement.

Put this guide to work

Frequently asked questions

What is an HBOM, and how is it different from an SBOM?

An HBOM (Hardware Bill of Materials) is a structured inventory of the physical hardware components that make up a product — processors, chipsets, modules, boards and the firmware bound to each of them — as distinct from a [software SBOM](/guides/firmware-sbom/), which inventories code: libraries, packages and the firmware image's software contents. A device typically needs both: the SBOM tells a buyer what software and open-source components ship inside a product's firmware, while the HBOM tells them which physical parts the product is built from, who makes each one, and where. CISA's own framework explicitly scopes HBOMs to also capture the firmware associated with each hardware component, so the two documents overlap at that boundary rather than sitting in fully separate silos.

What does CISA's HBOM Framework actually define?

On 25 September 2023, CISA's Information and Communications Technology (ICT) Supply Chain Risk Management (SCRM) Task Force published "A Hardware Bill of Materials (HBOM) Framework for Supply Chain Risk Management," developed by the Task Force's HBOM Working Group. Per CISA, the framework gives vendors and purchasers "a consistent and repeatable way... to communicate about hardware components, enabling effective risk assessment and mitigation in the supply chain." It is structured in three parts: Appendix A sets out use-case categories (reported by secondary technical analysis as three categories — compliance, security and availability — covering eight total sub-cases; CISA's own PDF is the authoritative source for that breakdown); Appendix B defines a format for consistency across HBOMs; and Appendix C provides a data field taxonomy of component attributes.

How many fields does an HBOM actually have?

Per secondary technical analysis of CISA's framework PDF, the data field taxonomy groups 47 named fields into seven categories: an HBOM header, finished-good product details, entity name, entity location, component part information, component part details, and production details. CISA's own Appendix C is the authoritative source for the exact field count and category breakdown, worth checking before building a data pipeline on it.

Is filing an HBOM legally required?

No federal rule requires an HBOM by CISA's exact name or format, and CISA describes the framework as voluntary — using it does not by itself demonstrate compliance with any specific US regulation. It functions as a reference vendors and purchasers can adopt by agreement, the same voluntary role the original 2021 NTIA Minimum Elements played for software SBOMs before parts of that model were absorbed into binding rules. The framework is cited as a resource (not a mandate) in OMB's January 2026 Memorandum M-26-05 on software and hardware risk management, alongside CISA's separate [SBOM Minimum Elements](/guides/sbom-minimum-elements/) guidance — see our [attestation form guide](/guides/secure-software-development-attestation-form/) for what M-26-05 changed and left in place.

Does CycloneDX or SPDX support HBOMs directly?

CycloneDX is the format most directly aligned: its own specification repository describes CycloneDX as covering "SBOM, SaaSBOM, HBOM, AI/ML-BOM, CBOM, OBOM, MBOM, VDR, and VEX" as a single data model, and the schema has carried a `device` component type ("a hardware device such as a processor or chip-set") since CycloneDX 1.0, with a dedicated `firmware` component type ("a special type of software that provides low-level control over a device's hardware") added in CycloneDX 1.2 (May 2020). An HBOM in CycloneDX is typically modeled as a hardware `device` component with a nested `firmware` component describing the software bound to it — the same device-plus-firmware pairing CISA's framework scopes for. SPDX, by contrast, has no dedicated hardware profile as of SPDX 3.0.1, which is one reason industry commentary on CISA's framework points to CycloneDX as the more complete path to an interoperable HBOM today; per that same secondary analysis, only a minority of CISA's 47 named fields map one-to-one onto either standard's existing properties, with location-related fields in particular requiring custom extensions in both.

Sources

  1. CISA: CISA Releases Hardware Bill of Materials Framework (HBOM) for Supply Chain Risk Management (press release, 25 September 2023)
  2. CISA: A Hardware Bill of Materials (HBOM) Framework for Supply Chain Risk Management (primary PDF, ICT SCRM Task Force HBOM Working Group)
  3. CISA: HBOM Framework Fact Sheet (508-compliant PDF)
  4. CycloneDX: specification repository (GitHub) — BOM types covered, including HBOM
  5. OMB Memorandum M-26-05, Adopting a Risk-Based Approach to Software and Hardware Security (January 2026)
  6. CISA press release on the HBOM Framework, 25 September 2023 (GovDelivery bulletin)
  7. CycloneDX: Hardware Bill of Materials (HBOM) capability
  8. CycloneDX v1.6 JSON reference
  9. SPDX 3.0.1 specification: SoftwarePurpose vocabulary
  10. FCC: Report and Order, Cybersecurity Labeling for Internet of Things (FCC 24-26), registry contents, para. 113
Was this guide helpful?

In this cluster

HBOM (Hardware Bill of Materials): CISA's framework explained