Firmware for medical and health device startups
If your device runs software and can reach the internet, FDA expects its cybersecurity to be designed in and documented. We build the firmware and the engineering records behind that. We are not your regulatory consultant.
Key characteristics
- Current FDA guidance
- Final guidance issued February 2026
- Law behind it
- FD&C Act section 524B, in effect since March 29, 2023
- We produce
- Signed updates, SBOM per release, test records
- We are not
- A regulatory consultancy or certified to IEC 62304 or ISO 13485
Health and medical device startups have two jobs at once: build a device that works, and show the U.S. Food and Drug Administration that it was built in a controlled way. Cybersecurity is now part of that second job, and much of it lands on the firmware: how the device proves an update is genuine, how a fix reaches units already with patients, and what software is inside each release.
Please read this first. This page summarizes FDA’s published materials as we read them on November 22, 2026. It is not regulatory or legal advice. Fumbar is a firmware company, not a regulatory consultancy, and we do not hold or claim certification to IEC 62304 or ISO 13485. Your regulatory lead decides the submission strategy and the quality system; we build firmware and produce engineering records that fit it.
What FDA currently says
The current guidance. FDA’s premarket cybersecurity guidance is “Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions”, a final guidance issued in February 2026. It supersedes the version issued June 27, 2025, and was revised to align with the amendments to 21 CFR 820, the Quality Management System Regulation. If you are working from an earlier version, check what changed. FDA’s FAQ says the premarket guidance recommendations apply to all medical devices that have or are software.
Section 524B. Congress added section 524B to the Federal Food, Drug, and Cosmetic Act in 2022, and the authority took effect on March 29, 2023. It applies to “cyber devices”: devices that include software validated, installed or authorized by the sponsor, have the ability to connect to the internet, and have characteristics that could be vulnerable to cybersecurity threats. FDA’s FAQ lists Bluetooth and Bluetooth LE, Wi-Fi, cellular, other radio links, and connectors such as USB, Ethernet or a serial port among the features that count as an ability to connect, and it counts firmware as software. A device you think of as offline may still qualify.
For a cyber device, a premarket submission has to include:
- A plan to monitor, identify and address postmarket vulnerabilities and exploits in a reasonable time, including coordinated vulnerability disclosure.
- Processes that give reasonable assurance the device and related systems are cybersecure, and that make postmarket updates and patches available.
- A software bill of materials (SBOM) covering commercial, open-source and off-the-shelf components.
FDA does not test medical devices. Its FAQ says cybersecurity testing, including security requirements testing, vulnerability assessment and penetration testing, is the manufacturer’s responsibility, and FDA reviews the results in the submission.
What that means for the firmware
Most of those expectations turn into concrete engineering work with a record at the end of it.
| FDA expectation | Firmware work | Record you receive |
|---|---|---|
| Postmarket updates and patches | Signed update path with secure boot, anti-rollback and tested recovery | Update design document and update test results |
| Software bill of materials | SBOM generated from the build for every release, with support status for each component | Machine-readable SBOM per release |
| Threat modeling and security architecture | Secure boot chain, key custody, debug-port lockdown, data protection | Threat model and security architecture diagrams |
| Cybersecurity testing | Security requirement tests in CI and on hardware | Test report per release |
| Vulnerability monitoring and disclosure | Dependency monitoring and an intake and triage process | Triage log and written procedure |
For SBOMs, CISA, NSA, FBI and international partners published the 2026 Minimum Elements for a Software Bill of Materials on July 29, 2026, replacing the 2021 NTIA minimum elements. FDA’s guidance has its own SBOM recommendations, including each component’s level of support and end of support, so we generate SBOMs that can carry both.
Design controls and the record trail
Firmware for a medical device is built inside the manufacturer’s quality system, not next to it. Whatever your regulatory lead has set up for design control, the firmware work has to fit: requirements traced to tests, design reviews recorded, changes controlled, and releases that can be rebuilt from a tagged commit. We work in your repository and issue tracker, use your templates where you have them, and write down decisions as we make them. The firmware requirements worksheet is a starting point if you have none.
We do not write your submission, choose your device classification or run your quality system. We supply the engineering evidence your regulatory team asks for, in a form they can file.
Updates on a device that is in use
An update to a medical device is a change to the device, so it goes through your change control before it ships. The update path also has to keep the device safe while it runs. In practice that means the device accepts an update only in a safe state (not during therapy or an active measurement), keeps the previous image until the new one passes its self-test, and reports the outcome. Rollouts go out in stages, starting with units you can reach. See over-the-air updates for how we build and test the path, and test automation for how the tests run on every release.
One more boundary: the FCC’s U.S. Cyber Trust Mark excludes medical devices regulated by FDA. A health wearable that is not a regulated device may fall under consumer rules instead; see connected consumer products.
Where to start
Request a firmware review and, if you have one, bring your regulatory consultant’s plan. We read your schematics, code, flash layout and update plan and send back a written plan: risks ranked, the order of work, and the firmware records your submission will need. Our security practices page explains how we handle keys and client code, and the security and regulation section of Field Update covers these rules in more depth.
Send us your board and your plan.
A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.
Or email sales@fumbar.com, or call (720) 675-4202.