FDA section 524B

SBOMs for connected medical devices

Section 524B of the FD&C Act requires manufacturers of cyber devices to provide an SBOM and to monitor and address post-market vulnerabilities. SBOMBox gives you a complete, scored SBOM for each release and keeps watching it after the device ships.

The problem

What makes this hard today

How SBOMBox helps

Evidence, not just a file

Generate SBOMs where your code lives

The sbombox CLI and CI action generate CycloneDX or SPDX SBOMs in your environment. Only the SBOM and its provenance are uploaded, never source code.

Check against recognised minimum elements

Every SBOM is scored against NTIA and CISA minimum elements, which FDA guidance references, plus BSI TR-03183-2.

Monitor for new vulnerabilities

Stored SBOMs are matched against OSV, GitHub Security Advisories, NVD and CISA KEV, so a newly exploited component shows up against the releases that contain it.

Record VEX decisions

Mark findings as not affected, affected, fixed or under investigation, with a justification, and keep that decision with the release it applies to.

Keep signed, per-release history

Every release's SBOM is stored immutably with its score and findings, so you can show what shipped in a version from two years ago.

Export when you need it

Export SBOMs in CycloneDX or SPDX for submissions and customer requests.

Getting started

How teams roll it out

  1. One project per device softwareTrack each independently released software unit separately.
  2. Generate from the release buildProduce the SBOM from the build that becomes the device software.
  3. Close gaps before submissionFix missing versions, suppliers and identifiers flagged by the score.
  4. Monitor post-marketKeep matching every fielded release against new vulnerabilities and record your assessment.
Common questions

Medical devices (FDA): questions we hear

Does SBOMBox have an FDA-specific profile?

No. SBOMs are scored against NTIA, CISA, BSI TR-03183-2 and CRA readiness checks. FDA-specific content such as support level and end-of-support dates remains your responsibility.

Which devices need an SBOM?

Cyber devices: devices that include software, can connect to the internet and could be vulnerable to cybersecurity threats.

Can we keep the data private?

Yes. Source code never leaves your environment, and SBOMs are only shared when you choose to.

Book a demo

See it with your own SBOM.

A 30-minute walkthrough focused on Medical devices (FDA). Bring a CycloneDX or SPDX file and we will score it live against BSI TR-03183-2, CISA, NTIA and CRA checks.