Skip to content
All posts

What Is an AIBOM (AI Bill of Materials)? Why It Matters

August 23, 2026 · Team PlayCISO
TL;DR · the short version

An AIBOM (AI Bill of Materials) is a machine-readable inventory of everything an AI system is built from, each component tagged with license, version and provenance, extending the SBOM to model weights and training data it omits. You need one because enterprise buyers, the EU AI Act, NIST AI RMF and ISO/IEC 42001 expect documented provenance, and because a non-commercial or copyleft model or dataset in a paid product is an unmanageable license trap. The practical format is CycloneDX (its ML-BOM extension), generated from manifests you already have.

Put it into practice
MCP Guard
Audit an MCP / agent configuration for plaintext secrets, unpinned installs, shell pipes and over-broad roots.
Open the tool →

An AIBOM (AI Bill of Materials) is a machine-readable inventory of everything an AI system is built from — every model, dataset, and software dependency, each tagged with its license, version, and provenance. It is the SBOM idea extended to the parts of the stack a traditional software bill of materials never captured: the weights and the training data. If you ship anything with a model in it, someone is going to ask you for one. To produce one from your manifests, use the AIBOM generator; to see exactly where an AIBOM, an SBOM and an ML-BOM differ, read SBOM vs AIBOM vs MLBOM; and for the model-and-dataset core on its own, see ML-BOM (machine learning bill of materials) explained.

What is an AIBOM?

A Software Bill of Materials (SBOM) answers a simple question: what is in this software? It lists the packages, versions, and licenses so that when a vulnerability like Log4Shell lands, you can tell in minutes whether you are exposed. An AI Bill of Materials answers the same question for an AI product — but an AI product has components an SBOM was never designed to describe. The base model, the fine-tuning datasets, the embeddings, the inference framework, and the licenses attached to each of those are all part of the real supply chain, and none of them show up in a package.json.

So an AIBOM is best understood as an SBOM plus the AI-specific layers: models, datasets, and their licenses and lineage, sitting alongside the ordinary code dependencies. The point is the same as an SBOM — answer “what is in this thing, and can I trust each piece” — for a system where the riskiest components are no longer just code.

Why an AIBOM matters now

  • Customer due diligence. Enterprise buyers and their security teams have started asking vendors, in writing, “what model, trained on what data, under what license?” Answering that in a Google Doc works until you have ten models and fifty datasets; then it breaks, and the gaps become the finding in someone else’s audit.
  • License traps. This is the one that quietly costs money. A model or dataset released under a non-commercial or research-only license (many of the best open weights are) can poison a paid product if it slips into production. A copyleft dataset can create obligations you never agreed to. You cannot manage a license risk you have never inventoried.
  • Regulation. The EU AI Act requires technical documentation of high-risk systems, including data and model provenance. NIST’s AI Risk Management Framework and ISO/IEC 42001 both push toward documented, auditable AI supply chains. An AIBOM is the artifact that makes those requirements answerable instead of aspirational.
  • Incident response. When a model or dataset is later found to be poisoned, backdoored, or trained on leaked data, the AIBOM is what tells you — fast — which of your products inherited the problem. Without it you are grepping through memory.

What goes into an AIBOM

  • Models — base models, fine-tunes, and adapters, with version/commit, source (Hugging Face, internal registry), and license.
  • Datasets — training, fine-tuning, and evaluation data, with source and license, flagged for non-commercial / research-only terms. The AIBOM data section shows what to record for each one.
  • Software dependencies — the inference framework, orchestration libraries, and the ordinary package tree that an SBOM/package scan already covers.
  • Licenses and provenance — the connective tissue: for every component above, where it came from and what you are allowed to do with it.

Which of these fields you own depends on your job. The two-minute AIBOM role quiz picks the six that matter for your role and gives you a reading path.

Useful next, if this was relevant to you

Showing 1 of 3: AI Security Risk Mapper

AIBOM vs SBOM

An AIBOM does not replace your SBOM — it extends it. The cleanest way to think about it: an SBOM inventories the code; an AIBOM inventories the code plus the models and data, because in an AI product the model and its training data are dependencies with licenses and risk, exactly like an npm package is. If you already produce SBOMs in CI, an AIBOM is the same discipline applied to two component types your existing tooling ignores. Not sure whether the BOM you already produce qualifies as a real AIBOM? The AIBOM vs SBOM analyzer tells you what is missing.

Formats: CycloneDX

You do not need a bespoke format. CycloneDX — the OWASP-backed SBOM standard — added machine-learning support (ML-BOM: model cards, datasets, and considerations) precisely so that models and datasets can be represented as first-class components alongside code. Emitting your AIBOM as CycloneDX JSON (pretty-print and validate it here) means it drops into the same tools, registries, and vulnerability workflows your SBOMs already flow through, instead of living in a spreadsheet only one person understands. Convert a plain model/dataset list into CycloneDX with the ML-BOM converter, then lint the result with the AIBOM validator before you ship it. For a complete file, field by field, see CycloneDX ML-BOM: fields and a worked example; for SPDX 3.0 and Croissant as alternatives, see AIBOM standards and templates compared.

How to generate an AIBOM

You can build one by hand, but it rots the moment a dependency changes. The practical path is to generate it from the manifests you already have. PlayCISO’s AI Bill of Materials generator (part of PlayCISO Pro) does exactly this in your browser: paste a package.json, a requirements.txt, or a small { models, datasets } manifest, and it returns a CycloneDX-flavored inventory with a per-component license-risk verdict — ok / review / conflict / unknown — and commercial-use conflict detection, downloadable as JSON. Nothing leaves the request. For the model side specifically, pair it with a behavioral model audit so the inventory sits next to evidence the model itself behaves. Check a specific component's terms with the model license checker, and once you regenerate on each build, diff successive inventories with the AIBOM drift detector to catch a new license conflict the moment it appears.

Building one step by step? Follow the guide to building an AI Bill of Materials, check every field against the AIBOM parameters checklist, compare generators and platforms in AIBOM tools and vendors compared, and see the three inventories side by side in the SBOM vs AIBOM vs MLBOM comparison.

A starting checklist

  • Inventory once, manually, today — list every model and dataset in one product. The gaps you find are the point.
  • Generate a CycloneDX AIBOM from that product’s manifests and read the license-risk column before anything else.
  • Resolve the conflicts — any non-commercial or copyleft component in a paid product is a decision, not a footnote.
  • Wire it into CI so the AIBOM regenerates on every build and a new license conflict fails the pipeline, the same way an SBOM does.
  • Keep the provenance — when a model or dataset is later found compromised, the lineage is what makes your blast-radius answer take minutes instead of days.
Generate one now. The AI Bill of Materials generator turns a manifest into a CycloneDX AIBOM with license-risk flags in seconds. Pair it with the package supply-chain scanner for the dependency side and a model behavioral audit for the models themselves.

Frequently asked questions

What is an AIBOM (AI Bill of Materials)?

An AIBOM is a machine-readable inventory of every component an AI system is built from — base models, fine-tunes and adapters, training/fine-tuning/evaluation datasets, and the ordinary software dependencies — each tagged with its version, source and license. It is the SBOM (Software Bill of Materials) idea extended to the two component types an SBOM was never designed to describe: the model weights and the data they were trained on.

What is the difference between an AIBOM and an SBOM?

An SBOM inventories the code — packages, versions and licenses. An AIBOM inventories the code plus the models and datasets, because in an AI product the model and its training data are dependencies with licenses and risk, exactly like an npm package. An AIBOM does not replace your SBOM; it extends the same discipline to two component types your existing tooling ignores.

What format should an AIBOM use?

CycloneDX — the OWASP-backed SBOM standard — added machine-learning support (ML-BOM: model cards, datasets and considerations) so models and datasets can be represented as first-class components alongside code. Emitting your AIBOM as CycloneDX JSON means it flows through the same tools, registries and vulnerability workflows your SBOMs already use.

Why do I need an AIBOM now?

Four drivers: enterprise buyers increasingly ask, in writing, "what model, trained on what data, under what license?"; a non-commercial or copyleft model/dataset in a paid product is a license trap; the EU AI Act, NIST AI RMF and ISO/IEC 42001 push toward documented, auditable AI supply chains; and when a model or dataset is later found poisoned or backdoored, the AIBOM is what tells you which products inherited the problem.

How do I generate an AIBOM?

Generate it from the manifests you already have rather than maintaining it by hand. PlayCISO's AIBOM generator (part of PlayCISO Pro) turns a package.json, requirements.txt or a { models, datasets } manifest into a CycloneDX AIBOM with a per-component license-risk verdict, in your browser. The AIBOM suite (ML-BOM converter, validator, diff, license checker, AIBOM-vs-SBOM analyzer) covers converting, validating and maintaining it.

Take this with you
What is an AIBOM? · Why an AIBOM matters now · What goes into an AIBOM · AIBOM vs SBOM · Formats: CycloneDX · How to generate an AIBOM

Ready to practise the decisions these articles describe?

Run your first Cyber War Room free →

Pro