InsightsFDA & medical devices
FDA cybersecurity for medical devices: what a 510(k) submission needs

Key takeaways
- Cybersecurity is a legal requirement for "cyber devices" in 510(k), De Novo and PMA submissions.
- FDA expects a threat model, risk assessment, architecture, SBOM, testing and a postmarket plan.
- Start during design. Retrofitting security late can cost months.
If your medical device runs software and connects to anything, cybersecurity is now part of what FDA reviews before it will clear the device. For many device teams, especially those moving from a research prototype to a first submission, this is the part of the 510(k) they are least prepared for. Done late, it can delay a submission by months. Done early, it becomes part of normal design work.
What changed
Since 2023, Section 524B of the Federal Food, Drug, and Cosmetic Act has made cybersecurity a legal requirement for "cyber devices," not just a recommendation. In June 2025, FDA issued updated final guidance, Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions, which explains what FDA expects to see. The requirements apply to 510(k), De Novo and PMA submissions alike, and FDA can refuse to accept a submission for a cyber device that leaves this information out.
Is your product a cyber device?
In plain terms, a device is a cyber device if it includes software, can connect to the internet, and has characteristics that could be vulnerable to cybersecurity threats. The definition is broad. A device that connects through a phone app, a hub or a hospital network, or that receives software updates, should be treated as in scope unless your regulatory advisor tells you otherwise.
The three things the law requires
- A plan to monitor and address vulnerabilities after launch, including how outside researchers can report a vulnerability to you (coordinated vulnerability disclosure).
- Processes that provide reasonable assurance the device and its related systems are cybersecure, including the ability to deliver updates and patches after the device is on the market.
- A software bill of materials (SBOM) listing the commercial, open-source and off-the-shelf software components in the device.
What FDA expects to see in the submission
The guidance turns those requirements into documentation. A complete cybersecurity section usually includes:
- Secure development process. Evidence that security is part of your design controls and quality system, not a separate exercise at the end.
- Threat model. How the device and the systems around it (apps, cloud services, hospital networks) could be attacked.
- Cybersecurity risk assessment. Each threat, its potential effect on safety and effectiveness, and the controls that reduce it. This is related to, but separate from, your safety risk analysis.
- Security architecture. Diagrams and descriptions showing how data flows, where trust boundaries are, and how authentication, encryption and updates work.
- SBOM with support status. Each component's version, whether it is still supported, and how you will track its known vulnerabilities.
- Security testing. Results of testing such as vulnerability scanning, penetration testing and fuzzing, with any open findings explained.
- Labeling. Information customers need to use the device securely, such as recommended network settings and how updates are delivered.
- Postmarket plan. How you will watch for new vulnerabilities, assess them, and ship fixes, with timelines.
Where teams get stuck
- Starting at submission time. Threat modeling and architecture decisions are cheap during design and expensive after it. Retrofitting update mechanisms or encryption late can mean redesign and retesting.
- Forgetting the system around the device. The phone app, the cloud backend and the update server are part of the medical device system, and FDA will ask about them.
- An SBOM nobody maintains. Generating a component list once is easy. FDA wants to know you will keep tracking those components for vulnerabilities for the life of the device.
- Testing without context. A penetration test report alone is not enough. Reviewers want to see how the testing ties back to your threat model and risk assessment.
- No owner for postmarket security. Someone has to receive vulnerability reports, decide what to patch, and keep the documentation current after clearance.
Where to start
If you are 6 to 18 months from a submission, start with a threat model and a security architecture review now, while design changes are still cheap. Then build the SBOM process, plan your security testing, and draft the postmarket plan alongside your other design documentation. If you are closer than that, a gap review of your current documentation against the guidance will show what is missing before FDA does.
How Sollucio can help
Sollucio's FDA Readiness Advisory works with medical device and digital health teams on the cybersecurity portion of premarket submissions: threat modeling, risk assessment, architecture documentation, SBOM processes and postmarket vulnerability plans. We work alongside your regulatory and engineering teams so the security documentation fits the rest of your submission.
Next step
Have an FDA submission on the horizon?
We will review where your cybersecurity documentation stands.


