# SBOMs for medical devices: what the FDA expects under section 524B

URL: https://sbombox.com/blog/fda-sbom-medical-devices
By SBOMBox SBOM experts. Published 2026-11-11

> Since FDORA, cyber devices need an SBOM in premarket submissions. Which devices are covered, what the SBOM should include, and what continues after clearance.

Short answer: section 524B of the US Federal Food, Drug, and Cosmetic Act requires manufacturers of 'cyber devices' to provide an SBOM covering commercial, open-source and off-the-shelf software components in their premarket submission, and to keep managing those components' vulnerabilities after the device is on the market.

## Where the rule comes from

Section 524B was added by the Food and Drug Omnibus Reform Act (FDORA), signed on 29 December 2022. The SBOM duty is in section 524B(b)(3). FDA's guidance, 'Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions', explains what FDA expects to see; it was updated in 2026 to align with the new Quality Management System Regulation. Check the current version on fda.gov.

## Which devices are covered

A cyber device is a device that includes software, can connect to the internet, and could be vulnerable to cybersecurity threats. In practice, that covers most connected and software-driven devices, including those that connect only occasionally.

## What the SBOM should contain

- Every software component, including open-source and off-the-shelf software, not just your own code.
- A machine-readable format such as SPDX or CycloneDX, meeting CISA's [2026 minimum elements](https://sbombox.com/blog/sbom-minimum-elements), which replaced the NTIA 2021 list.
- For each component, FDA's guidance also asks for its support level and end-of-support date, and an assessment of known vulnerabilities and how they are controlled.

## It does not stop at clearance

524B also requires a plan to monitor, identify and address post-market vulnerabilities, and processes to provide updates and patches. The SBOM is how you do that: match it continuously against vulnerability feeds, record your assessment with VEX, and keep it current with every software release.

## If you also sell in the EU

Medical devices are regulated under the EU MDR rather than the Cyber Resilience Act, but connected accessories and software sold separately may not be. Build one SBOM pipeline that satisfies FDA, MDR expectations and, where relevant, the CRA.

## Practical steps

- Generate the SBOM from the build that produces the released device software.
- Add support status and end-of-support dates for third-party components.
- Run each SBOM through a quality check before submission; missing versions and suppliers are the usual gaps. The [free checker](https://sbombox.com/audit) shows them.
- Store one SBOM per release, so you can answer questions about devices already in the field, years after they shipped.
- Record a VEX decision for each matched vulnerability, so your post-market assessment is documented.

This is general information, not regulatory advice. Confirm your submission content with FDA guidance and your regulatory team.
