At a glance

  • No law covered in this guide uses the term “AI bill of materials.” Binding component-list duties come from software bill of materials (SBOM) and AI documentation rules, each reaching a defined group.
  • From December 11, 2027, the EU Cyber Resilience Act requires manufacturers of in-scope products with digital elements to draw up an SBOM “in a commonly used and machine-readable format covering at the very least the top-level dependencies of the products” (products placed earlier only if substantially modified from then). It sits in the technical documentation and goes to a market surveillance authority on a reasoned request where necessary to check compliance; publishing it to users is the manufacturer’s choice.
  • In the US, FD&C Act section 524B(b)(3) has required sponsors of premarket submissions for cyber devices to provide an SBOM, including commercial, open-source, and off-the-shelf software components, since March 29, 2023. On January 23, 2026, OMB rescinded the federal software attestation memos M-22-18 and M-23-16; agencies may still require a current SBOM on request by contract.
  • CISA’s voluntary 2026 Minimum Elements for an SBOM (July 29, 2026) cover AI software but add no AI-specific elements; those come from other voluntary sources such as the G7 Software Bill of Materials for AI – Minimum Elements (May 12, 2026), SPDX, and CycloneDX.

What is an AI bill of materials?

An AI bill of materials (AIBOM) is an inventory of what an AI system is built from: its software dependencies, its models and the models they were derived from, the datasets used to train, test, and validate them, and the licenses on each. It extends the software bill of materials, which Executive Order 14028 defines as “a formal record containing the details and supply chain relationships of various components used in building software.” No statute covered here requires a document called an AIBOM, but several require parts of one.

Cybersecurity rules (the EU Cyber Resilience Act, FDA’s cyber device statute) and some US federal contracts ask for software components so vulnerabilities can be traced. AI documentation rules (the EU AI Act, California AB 2013) ask about models and training data.

Which rules require a bill of materials for AI?

As of November 16, 2026, the binding duties are the Cyber Resilience Act (from December 11, 2027), the EU AI Act documentation rules for general-purpose models and for high-risk systems (from December 2, 2027 or August 2, 2028), FDA’s section 524B for cyber devices, and California AB 2013 for training data. US federal SBOM policy now binds only agencies, and the CISA, G7, SPDX, and CycloneDX documents are voluntary.

Component-list duties and frameworks that reach AI, as of November 16, 2026
RuleWho it reachesWhat component list it requiresBinding?Date
EU Cyber Resilience Act, Regulation (EU) 2024/2847, Annex I Part II point (1), Article 13, Annex VIIManufacturers of products with digital elements made available on the EU market whose intended purpose or reasonably foreseeable use includes a data connection; excludes, among others, products covered by the EU medical device, in vitro diagnostic, and motor vehicle general safety regulations, certified aviation products, and marine equipmentAn SBOM in a commonly used and machine-readable format covering at the very least the top-level dependencies; part of the technical documentation, kept at least 10 years or for the support period, whichever is longer; to a market surveillance authority on a reasoned requestYes; fines up to EUR 15 000 000 or 2.5% of worldwide annual turnover, whichever is higherFrom December 11, 2027; products already on the market only if substantially modified after that date
EU AI Act, Article 11 and Annex IVProviders of high-risk AI systemsPre-trained systems or tools provided by third parties and how they were used, integrated, or modified; system architecture; versions of relevant software or firmware; datasheets on training data provenance, scope, and main characteristicsYesDecember 2, 2027 (Annex III) or August 2, 2028 (Annex I Section A); a system placed on the market earlier only if its design changes significantly from then, but public-authority systems by August 2, 2030 (Article 111(2))
EU AI Act, Article 53(1)(a) and (b), Annexes XI and XIIProviders of general-purpose AI models (open-source exception for (a) and (b), not for models with systemic risk)Architecture and number of parameters, licence, type and provenance of training, testing, and validation data and curation methodologies, computational resources, energy consumption, versions of relevant softwareYesSince August 2, 2025; August 2, 2027 for models placed on the market before then
EU AI Act, Article 53(1)(d)All general-purpose AI model providers, open-source providers includedA public summary of the content used to train the model, on the AI Office templateYesSame as above
FD&C Act section 524B(b)(3)Sponsors of 510(k), PMA, PDP, De Novo, or HDE submissions for a cyber deviceAn SBOM, including commercial, open-source, and off-the-shelf software components; FDA’s guidance adds level of support and end-of-support date for each componentStatute yes; guidance nonbindingSubmissions on or after March 29, 2023
California AB 2013, Civil Code 3111Developers of generative AI systems or services released on or after January 1, 2022 and made publicly available to Californians, with the 3111(b) exemptionsA high-level summary of the training datasets, with 12 listed itemsYesOn or before January 1, 2026, and before each later release or substantial modification
Executive Order 14028, sections 4(e)(vii), 4(f), and 10(j)Directs federal agencies (NIST, Commerce, NTIA); no direct duty on vendorsNIST guidance criteria on providing a purchaser an SBOM; NTIA minimum elementsDirects agencies onlySigned May 12, 2021; the Federal Register record lists no amendment of EO 14028
OMB Memorandum M-26-05Federal agenciesAgencies may adopt contract terms requiring a current SBOM on request; for a cloud platform, an SBOM of the runtime production environmentAgency policy; the SBOM term is optionalJanuary 23, 2026; rescinded M-22-18 and M-23-16
CISA and partners, 2026 Minimum Elements for an SBOMOrganizations that produce, procure, or operate software17 data fields (for example component producer, name, version, identifiers, hash, license, dependency relationship, SBOM author and signature) plus practicesVoluntaryJuly 29, 2026; replaces the 2021 NTIA minimum elements
CISA and G7 partners, Software Bill of Materials for AI – Minimum ElementsPublic and private sector stakeholdersSupplemental minimum elements for AI, in addition to the general SBOM elements, in seven clusters: metadata, system-level properties, models, datasets, infrastructure, security properties, and key performance indicatorsVoluntary; described as “not exhaustive or mandatory”May 12, 2026
SPDX 3.0.1 AI and Dataset profiles; CycloneDX (ECMA-424, 2nd edition)Anyone who chooses to use themMachine-readable formats with fields for models, datasets, licenses, and dependenciesVoluntarySPDX 3.0.1 specification; ECMA-424 2nd edition, December 2025 (CycloneDX 1.7)

What does the EU Cyber Resilience Act require?

Annex I, Part II, point (1) requires manufacturers to “identify and document vulnerabilities and components contained in products with digital elements, including by drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies of the products.” Article 13(8) requires manufacturers to handle vulnerabilities of the product, including its components, effectively and in accordance with Part II for the support period.

The SBOM is not public by default. Annex VII point 2(b) puts it in the technical documentation, and point 8 includes it, where applicable, “further to a reasoned request from a market surveillance authority provided that it is necessary in order for that authority to be able to check compliance with the essential cybersecurity requirements set out in Annex I.” Under Annex II point 9, the user information says where the SBOM can be accessed only “if the manufacturer decides to make available the software bill of materials to the user.” Article 13(13) requires the technical documentation to be kept at least 10 years after the product is placed on the market or for the support period, whichever is longer, and Article 13(24) lets the Commission specify the SBOM’s format and elements by implementing act (none adopted as of November 16, 2026).

The Act reaches AI as software. A product with digital elements is “a software or hardware product and its remote data processing solutions, including software or hardware components being placed on the market separately” (Article 3(1)), and the Act covers those made available on the market whose intended purpose or reasonably foreseeable use includes a direct or indirect logical or physical data connection to a device or network (Article 2(1)). It applies from December 11, 2027 (Article 71(2)). Products placed on the market before that date are covered only if substantially modified afterward, except for the reporting duty, which has applied to them as well since September 11, 2026 (Articles 69 and 71). A high-risk AI system that meets the Act’s essential cybersecurity requirements is deemed to comply with AI Act Article 15 cybersecurity requirements if its declaration of conformity demonstrates it (Article 12). Breaching Annex I, Article 13, or Article 14 can draw fines of up to EUR 15 000 000 or, for an undertaking, 2.5% of total worldwide annual turnover for the preceding financial year, whichever is higher (Article 64(2)). A July 2, 2025 corrigendum makes the Article 64(10) carve-outs reach those fines too: open-source software stewards cannot be fined, and microenterprises and small enterprises cannot be fined for missing the 24-hour early warning deadlines in Article 14(2)(a) or 14(4)(a).

What does the EU AI Act add for models and training data?

For high-risk systems, Annex IV point 2(a) requires the development methods, “including, where relevant, recourse to pre-trained systems or tools provided by third parties and how those were used, integrated or modified by the provider”; point 2(c) the system architecture, “explaining how software components build on or feed into each other and integrate into the overall processing”; point 1(c) the versions of relevant software or firmware; and point 2(d), where relevant, datasheets on the training data’s provenance, scope, and main characteristics, how it was obtained and selected, labelling, and cleaning. These apply from December 2, 2027 (Annex III) or August 2, 2028 (Annex I Section A), and Article 18 requires keeping the documentation for 10 years after the system is placed on the market or put into service.

For general-purpose AI models, Annex XI Section 1 requires, among other things, the architecture and number of parameters, the licence, and information on the training, testing, and validation data, where applicable, “including the type and provenance of data and curation methodologies (e.g. cleaning, filtering, etc.), the number of data points, their scope and main characteristics,” with computational resources and known or estimated energy consumption. Annex XII gives downstream providers the versions of relevant software, where applicable, the licence, and the type and provenance of training data. For models with systemic risk, Annex XI Section 2 point 3 adds, where applicable, the system architecture. The Article 53(2) open-source exception covers Annex XI and XII, but not models with systemic risk and not the Article 53(1)(d) public training content summary, which the AI data governance guide covers.

California AB 2013 covers training data, not software: subject to the 3111(b) exemptions, Civil Code 3111 requires developers of generative AI systems or services released on or after January 1, 2022 and made publicly available to Californians to post a 12-item training data summary, on or before January 1, 2026 and before each later release or substantial modification. In X.AI LLC v. Bonta, the Central District of California denied a preliminary injunction on March 4, 2026; xAI’s appeal (Ninth Circuit No. 26-1591) was pending as of November 3, 2026, with oral argument calendared for November 18, 2026, and the law is enforceable while it proceeds.

What is left of the US federal SBOM requirements?

Executive Order 14028 (May 12, 2021) did not itself require vendors to deliver SBOMs. Section 4(e) directed NIST to issue guidance that “shall include standards, procedures, or criteria regarding,” among other things, “providing a purchaser a Software Bill of Materials (SBOM) for each product directly or by publishing it on a public website,” and section 4(f) directed Commerce and NTIA to publish SBOM minimum elements. As of November 16, 2026, the Federal Register record for EO 14028 lists no amending order. Executive Order 14306 (June 6, 2025) amended Executive Orders 14144 and 13694, not 14028.

OMB Memorandum M-26-05, signed January 23, 2026, rescinds M-22-18 and M-23-16, saying M-22-18 “imposed unproven and burdensome software accounting processes.” Agencies “shall continue to maintain a complete inventory of software and hardware,” may still use the Secure Software Development Attestation Form, and “may also choose to adopt contractual terms that require a software producer to provide a current software bill of materials (SBOM) upon request”; for a cloud platform, that term should cover the runtime production environment. A federal AI vendor’s SBOM duty to an agency now comes from its contract. The AI vendor risk assessment guide covers OMB’s AI acquisition memo, M-25-22.

What do CISA and the G7 say about SBOMs for AI?

CISA and 17 co-authoring organizations, including NSA and the FBI, published the 2026 Minimum Elements for a Software Bill of Materials on July 29, 2026. It “updates and replaces” the 2021 NTIA minimum elements, lists 17 data fields, and adds, among others, SBOM author signature, generation context, component hash, and component license. CISA says the elements apply to all software, including AI software, but the document “does not introduce additional elements for SBOMs for AI systems” and points to “model cards” or “data cards” for AI-specific information.

AI-specific elements are in Software Bill of Materials for AI – Minimum Elements, released May 12, 2026 by the G7 cybersecurity agencies, including CISA, with the European Commission. Its seven clusters, added to the general elements, run from metadata, system-level properties, and models (producer, hash, architecture, training methods, lineage, license) to datasets (provenance, sensitivity, hash, license), infrastructure, security properties, and performance indicators. It says the elements are “not mandatory” and create no requirements. Neither document binds a private company.

Does FDA require an SBOM for an AI-enabled medical device?

Yes, if it is a cyber device. Section 524B(b)(3) of the FD&C Act requires the sponsor to provide a software bill of materials, including commercial, open-source, and off-the-shelf software components. A cyber device is one that “(1) includes software validated, installed, or authorized by the sponsor as a device or in a device; (2) has the ability to connect to the internet; and (3) contains any such technological characteristics validated, installed, or authorized by the sponsor that could be vulnerable to cybersecurity threats” (section 524B(c)). The duty applies to 510(k), PMA, PDP, De Novo, and HDE submissions, including those for modifications, but not to submissions made before March 29, 2023.

FDA’s nonbinding final guidance, Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (February 3, 2026, superseding the June 27, 2025 version), recommends machine-readable SBOMs consistent with the October 2021 NTIA minimum elements plus each component’s level of support and end-of-support date, and a risk assessment of each known vulnerability, including those in CISA’s Known Exploited Vulnerabilities Catalog. Devices covered by the EU medical device regulations are outside the Cyber Resilience Act. The FDA PCCP guide covers planned model changes.

Which formats can carry an AIBOM?

No law above names a format: the Cyber Resilience Act asks for a “commonly used and machine-readable format,” and FDA says “Industry-accepted formats of SBOMs are encouraged.” Two voluntary open formats have AI fields:

  • SPDX. The SPDX 3.0.1 specification defines optional AI and Dataset profiles, with properties such as type of model, hyperparameters, energy consumption, limitations, safety risk assessment, data collection process, known bias, and anonymization method.
  • CycloneDX. CycloneDX 1.7 (October 21, 2025) is standardized as ECMA-424, 2nd edition (December 2025). It has component types for machine learning models and data, and a model card object for model components.

AIBOM fields: which field serves which rule?

This outline is a starting point and is not complete for any one law. Each field is tagged with the provisions or frameworks it helps satisfy; a tag does not mean the rule reaches your system. Check each applicable provision in full.

  1. BOM metadata: author, signature, timestamp, version, generation context, tool, format. (CISA 2026, voluntary; CRA Annex I Part II(1))
  2. Component identity: producer, name, version, identifiers, hash. (CISA 2026, voluntary; CRA Annex I Part II(1); FD&C Act 524B(b)(3); EU Annex IV 1(a))
  3. Software dependencies and relationships, at least top-level, including commercial, open-source, and off-the-shelf components. (CRA Annex I Part II(1); 524B(b)(3))
  4. Software and firmware versions and update requirements. (EU Annex IV 1(c), Annex XII 1(e))
  5. Licenses for software, models, and datasets. (EU Annex XI 1(f), Annex XII 1(h); CISA 2026, voluntary)
  6. Model identity: type, architecture, parameters, input and output modalities. (EU Annex XI 1(d) and (e), Annex XII 1(f) and (g); G7 AI, voluntary)
  7. Model lineage: pre-trained models and third-party tools, and how each was used, integrated, or modified. (EU Annex IV 2(a); G7 AI, voluntary)
  8. System architecture. (EU Annex IV 2(c); Annex XI Section 2 point 3; CRA Annex VII 2(a))
  9. Datasets: type, provenance, owner, collection period, curation, size, scope, personal or copyrighted content. (EU Annex IV 2(d), Annex XI Section 1 2(c), Annex XII 2(c); AB 2013 Civil Code 3111(a); G7 AI, voluntary)
  10. Training compute and energy. (EU Annex XI 2(d) and (e))
  11. Support status: each component’s support level and end-of-support date. (FDA guidance, nonbinding; CRA Article 13(8) support period)
  12. Known vulnerabilities and remediation status. (CRA Annex I Part II(1) and (2); FDA guidance, nonbinding)
  13. Distribution record: who received the BOM, and where users can access it if published. (CRA Annex II point 9, Annex VII point 8; OMB M-26-05, agencies only)

How do you build an AIBOM program?

  • List every AI system and model you build, buy, or sell, and record which table rows reach each
  • Generate SBOMs from the build pipeline, not by hand
  • For in-scope products with digital elements placed on the EU market from December 11, 2027, or substantially modified from that date, put an SBOM in a commonly used and machine-readable format, covering at least top-level dependencies, in the technical documentation
  • For EU high-risk systems, and general-purpose models outside the open-source exception, record pre-trained models, third-party tools, and dataset provenance in the inventory that feeds Annex IV, XI, and XII documentation
  • For cyber devices, include an SBOM with commercial, open-source, and off-the-shelf components in each premarket submission
  • If AB 2013 reaches you, keep your training data summary consistent with the AIBOM’s dataset entries
  • Ask AI vendors for a current SBOM, and for hosted services a runtime SBOM, and write delivery into the contract
  • Regenerate the AIBOM on every model or dependency change and check new vulnerabilities against it

How this fits the other guides: the AI model cards guide covers the performance and intended-use documents that sit beside an AIBOM, the EU AI Act compliance guide covers the provider duties behind Annexes IV, XI, and XII, and the AI audit guide covers the audits and conformity assessments that check technical documentation.

This guide is general information as of November 16, 2026, not legal advice. Confirm current requirements with the primary source, your regulator, or counsel before relying on it.

Common questions

Is an AI bill of materials legally required?

No law covered in this guide requires a document called an AI bill of materials, but parts of one are required. From December 11, 2027, the EU Cyber Resilience Act requires manufacturers of in-scope products with digital elements to draw up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies of the products (for products placed on the market before then, only if substantially modified from that date). The EU AI Act requires providers of high-risk AI systems, from December 2, 2027 or August 2, 2028, to document, where relevant, pre-trained systems or tools provided by third parties and how they were used, integrated or modified, and requires providers of general-purpose AI models, unless the open-source exception applies (it never covers models with systemic risk), to document, where applicable, the type and provenance of training, testing and validation data.

Must an SBOM under the Cyber Resilience Act be published?

No. The SBOM is part of the technical documentation, which must be kept for at least 10 years after the product is placed on the market or for the support period, whichever is longer, and it goes to a market surveillance authority on a reasoned request where necessary for that authority to check compliance with the essential cybersecurity requirements in Annex I. The user information must say where the SBOM can be accessed only if the manufacturer decides to make it available to the user.

Do US federal rules still require software vendors to provide SBOMs?

Not government-wide. Executive Order 14028 directed NIST guidance criteria on providing a purchaser an SBOM but imposed no direct duty on vendors, and OMB Memorandum M-26-05 of January 23, 2026 rescinded M-22-18 and M-23-16. Agencies may adopt contract terms requiring a software producer to provide a current SBOM upon request. Separately, FD&C Act section 524B(b)(3) requires sponsors of premarket submissions for cyber devices to provide an SBOM, including commercial, open-source, and off-the-shelf software components.

By industry: all 8 industry pages

Sources

  1. Regulation (EU) 2024/2847 (Cyber Resilience Act), Articles 2, 3, 12, 13, 14, 64, 69, and 71 and Annexes I, II, and VII, EUR-Lex, OJ L, 2024/2847, November 20, 2024, accessed November 16, 2026.
  2. Corrigendum to Regulation (EU) 2024/2847, Article 64(10), EUR-Lex, OJ L, 2025/90555, July 2, 2025.
  3. Regulation (EU) 2024/1689 (Artificial Intelligence Act), consolidated text as of July 27, 2026, as amended by Regulation (EU) 2026/1744, EUR-Lex, Articles 11, 18, 53, 111, and 113 and Annexes IV, XI, and XII, accessed November 16, 2026.
  4. Explanatory Notice and Template for the Public Summary of Training Content for general-purpose AI models, European Commission, July 24, 2025.
  5. Executive Order 14028, Improving the Nation’s Cybersecurity, 86 FR 26633, Federal Register, May 17, 2021, sections 4(e), 4(f), and 10(j).
  6. Executive Order 14306, Sustaining Select Efforts To Strengthen the Nation’s Cybersecurity and Amending Executive Order 13694 and Executive Order 14144, 90 FR 24723, Federal Register, June 11, 2025.
  7. Executive Order 14144, Strengthening and Promoting Innovation in the Nation’s Cybersecurity, 90 FR 6755, Federal Register, January 17, 2025.
  8. OMB Memorandum M-26-05, Adopting a Risk-based Approach to Software and Hardware Security (PDF), Office of Management and Budget, January 23, 2026.
  9. 2026 Minimum Elements for a Software Bill of Materials (SBOM), Cybersecurity and Infrastructure Security Agency, July 29, 2026.
  10. 2026 Minimum Elements for a Software Bill of Materials (SBOM) (PDF), CISA and co-authoring organizations, July 29, 2026.
  11. CISA and Partners Unveil Updated Software Bill of Materials Resource, Cybersecurity and Infrastructure Security Agency, July 29, 2026.
  12. Software Bill of Materials for AI – Minimum Elements (resource page), Cybersecurity and Infrastructure Security Agency, May 12, 2026, accessed November 16, 2026.
  13. Software Bill of Materials for AI – Minimum Elements, sections 2.1 to 2.7 (download page), G7 Cybersecurity Working Group, hosted by Germany’s Federal Office for Information Security (BSI), May 12, 2026, accessed November 16, 2026.
  14. Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions, U.S. Food and Drug Administration, February 3, 2026.
  15. Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions, final guidance (PDF), Sections V.A.4 and VII, U.S. Food and Drug Administration, February 3, 2026.
  16. Cybersecurity Resources for Medical Device Manufacturers: Guidance, Resources, and FAQs, U.S. Food and Drug Administration, content current as of November 10, 2026.
  17. AB-2013 Generative artificial intelligence: training data transparency (Chapter 817, Statutes of 2024), California Legislative Information, 2024.
  18. Court calendar: X.AI LLC v. Bonta, No. 26-1591, November 18, 2026, U.S. Court of Appeals for the Ninth Circuit, accessed November 3, 2026.
  19. SPDX Specifications, SPDX (Linux Foundation), accessed November 16, 2026.
  20. SPDX Specification 3.0.1 (PDF), clauses 4, 12, and 13 (Dataset and AI profiles), SPDX (Linux Foundation), 2024.
  21. Machine Learning Bill of Materials (AI/ML-BOM), CycloneDX (OWASP Foundation), accessed November 16, 2026.
  22. CycloneDX Specification Overview, CycloneDX (OWASP Foundation), accessed November 16, 2026.
  23. ECMA-424, CycloneDX Bill of materials specification, 2nd edition, Ecma International, December 2025.