FDA cybersecurity

What does FDA expect in a premarket cybersecurity submission?

Short answer

FDA's current guidance, "Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions", issued February 3, 2026, recommends that your submission show cybersecurity as part of design: a threat model kept current throughout the design process, a cybersecurity risk assessment, a Software Bill of Materials (SBOM) with support information for each third-party component, and testing documentation. FDA recommends traceability between those four. These are FDA's recommendations, set out in guidance.

2-minute read · Published

This guide follows FDA's final guidance "Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions", issued February 3, 2026, FDA's current premarket cybersecurity guidance. Section numbers below point to that document.

1. A threat model, kept current through design

FDA recommends threat modeling be performed throughout the design process (guidance §V.A.1). A threat model written once, early, and never revised will not match the software you submit.

In practice: revise the threat model whenever the architecture changes, and date each revision so the link between design change and threat model change is visible.

2. A cybersecurity risk assessment that stays up to date

FDA says manufacturers should update their security risk management documentation as new information becomes available, such as new threats, vulnerabilities, assets, or adverse impacts found during development and after the device is released (guidance §V.A.6).

The guidance notes that, when maintained throughout the device lifecycle, this documentation (for example the threat model and the cybersecurity risk assessment) can be used to quickly identify vulnerability impacts once a device is released.

3. An SBOM with support information for each third-party component

For each third-party software component, the guidance lists two items among the information to provide (guidance §V.A.4.b):

  • The level of support provided through monitoring and maintenance from the software component manufacturer.
  • The software component's end-of-support date.

If your SBOM lists component names and versions only, add these two items for each one.

4. Traceability between the four pieces

FDA recommends traceability between the threat model, the cybersecurity risk assessment, the SBOM, and the testing documentation (guidance §V.A). Each security test should trace back to a threat and a risk it addresses.

Also plan for how updates reach fielded devices

The guidance points out that "if an update is not applied automatically for all fielded devices, then there will likely be different risk profiles for differing software configurations of the device" (guidance §V.A.6). Your risk documentation should account for the configurations that will exist in the field.

Who owns which piece

These four pieces usually sit with different people: architecture with development, the risk assessment with the security lead, test evidence with the test team. The work that slips is the handoff between them. Two handoffs matter most here:

  • Testing to cybersecurity: do your security tests trace back to your threat model and cybersecurity risk assessment?
  • Cybersecurity to development: does your threat model change when your architecture changes?

Where MedDev Solutions fits

We prepare the cybersecurity documentation with your team: threat modeling, cybersecurity risk analysis, SBOM creation and upkeep, the premarket cybersecurity plan and report, security architecture views, and documentation of the evidence from your security testing. The work is designed to support compliance with IEC 81001-5-1. Your company remains the manufacturer and keeps responsibility for its design controls and submission.

Questions we get

Related questions

Answer

MedDev Solutions

No. FDA recommends threat modeling be performed throughout the design process, according to its February 3, 2026 premarket cybersecurity guidance (§V.A.1). Revise the threat model when the architecture changes.

MedDev Solutions

For each third-party software component, FDA's February 3, 2026 guidance lists the supplier's level of support through monitoring and maintenance, and the component's end-of-support date, among the information to provide (§V.A.4.b).

MedDev Solutions

FDA recommends traceability between the threat model, the cybersecurity risk assessment, the Software Bill of Materials (SBOM), and the testing documentation (February 3, 2026 guidance, §V.A).

Something else? Ask us directly on a 30-minute call

Keep going

Where to go next.

  • Service

    FDA Medical Device Cybersecurity

    Threat modeling, cybersecurity risk analysis, SBOM, and premarket cybersecurity documentation for SaMD, built with your dev team.

  • Free checklist

    Five handoffs to own before your FDA submission

    Development, quality, regulatory, testing, and cybersecurity each own a piece of your submission. This checklist covers the handoffs between them.

Next step

Bring us your program, wherever it stands.

In 30 minutes, we'll look at where your program stands and which handoffs need an owner.