FDA section 524B: SBOMs for medical devices that ship ML models
Since March 2023, a premarket submission for a cyber device has to include an SBOM. FDA's guidance asks for more than a component list: support status for each component and an assessment of each known vulnerability.
Who it applies to
Section 524B applies to anyone submitting a 510(k), PMA, PDP, De Novo or HDE for a cyber device. FDA's FAQ summarises the statutory definition as a device that:
- includes software validated, installed or authorized by the sponsor as a device or in a device;
- has the ability to connect to the internet; and
- contains technological characteristics that could be vulnerable to cybersecurity threats.
The requirements apply to modifications too: a device change that needs one of those submissions brings section 524B with it (FDA guidance, section VII.D).
Key dates
- 29 Dec 2022
- Consolidated Appropriations Act, 2023 signed; section 3305 adds section 524B to the FD&C Act.
- 29 Mar 2023
- Section 524B takes effect for submissions sent on or after this date.
- 1 Oct 2023
- FDA's transitional refuse-to-accept policy for cyber devices ends (FDA cybersecurity FAQ).
- 3 Feb 2026
- Current premarket cybersecurity guidance issued, superseding the June 2025 version.
What the statute requires
- 524B(b)(1): a plan to monitor, identify and address postmarket vulnerabilities, including coordinated vulnerability disclosure.
- 524B(b)(2): processes that provide reasonable assurance the device and related systems are cybersecure, and postmarket updates and patches.
- 524B(b)(3): a software bill of materials, "including commercial, open-source, and off-the-shelf software components".
- 524B(b)(4): other requirements FDA may set by regulation.
What FDA's guidance recommends for the SBOM
The guidance is nonbinding, but it is what reviewers work from. For third-party software components it recommends (section V.A.4):
- A machine-readable SBOM consistent with the minimum elements in NTIA's October 2021 document Framing Software Component Transparency.
- For each component, its level of support (actively maintained, no longer maintained, abandoned) and its end-of-support date.
- All known vulnerabilities in the device and its components, including those in CISA's Known Exploited Vulnerabilities Catalog, with a safety and security risk assessment of each and the risk controls that address it.
The guidance does not name VEX or a specific SBOM format. A VEX document is one machine-readable way to record the per-vulnerability assessment; ask your reviewers what they expect to see.
Where an AI BOM helps, and where it doesn't
A device that runs a model loads weight files the rest of its SBOM may not mention. AIsbom inventories those files and the Python packages pinned beside them. It does not cover firmware, OS packages or other ecosystems. The right-hand column is our reading of the overlap, not FDA's.
| Statute / guidance item | What AIsbom records | Coverage |
|---|---|---|
| 524B(b)(3): SBOM of commercial, open-source and off-the-shelf components | Model files and pinned requirements.txt packages, as CycloneDX or SPDX JSON |
The ML portion of the device software. |
| Guidance: machine-readable, NTIA minimum elements | Component name, version, SHA-256 per model file, the generating tool and a timestamp | Partial. There is no structured supplier field; a Hugging Face repo id is recorded as a property. |
| Guidance: level of support and end-of-support date per component | Nothing | Out of scope. AIsbom cannot tell whether a model or package is still maintained. |
| Guidance: known vulnerabilities, including CISA KEV |
Dangerous-import findings in pickle-based model files; with --vex, OSV CVE lookups for
exact pins
|
Partial. The KEV catalog is not checked. |
| Guidance: risk assessment of each known vulnerability | OpenVEX or CycloneDX VEX status per finding | Records affected / not affected. The safety and security risk assessment is yours. |
| 524B(b)(1): postmarket vulnerability monitoring | On the platform, scan history per repo and alerts when a new advisory matches a connected repo | Supports monitoring. The plan, and coordinated disclosure, are yours. |
Generating the evidence
pip install aisbom-cli
# SBOM plus VEX for the model files and Python dependencies in the device software
aisbom scan ./device-software --output sbom.json --vex
# Grade how complete the document is before it goes into a submission
aisbom score sbom.json
For background on why pickle-based model formats matter, see SafeTensors vs pickle.
See which SBOM evidence your repo is missing
The readiness view breaks your latest scan down by identity, integrity, provenance and exploitability statements, and lists each gap with the item it maps to. Free on every plan.
Open the readiness view Other regulationsSources
- FDA: Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (final guidance, 3 February 2026).
- FDA: Cybersecurity in Medical Devices Frequently Asked Questions: section 524B scope, cyber device definition, effective dates.
- FDA: Cybersecurity: Consolidated Appropriations Act, 2023, section 3305.
Last reviewed 2026-10-31 against FDA's guidance of 3 February 2026. This page is general information, not legal or regulatory advice. AIsbom reports what an SBOM contains. It does not assess or attest to any device's regulatory status, and it cannot see your design controls, threat model or risk management.