Medical Device Cybersecurity: A Practical Guide for Manufacturers

Medical device cybersecurity is the work of designing, documenting and maintaining connected devices so they stay safe and effective in the face of cyber threats. For manufacturers it is now a regulatory requirement, not a best practice: the FDA can refuse to accept a submission that lacks it. This guide covers what regulators expect, the standards behind those expectations, and what a working program looks like from design through postmarket.

1. What is medical device cybersecurity?

Medical device cybersecurity protects connected devices, and the patients who rely on them, from threats that could change how a device works, expose patient data, or take it offline. It covers infusion pumps and pacemakers, imaging systems, diagnostic instruments, surgical robots, and software that is itself a medical device.

What makes it different from enterprise IT security is the stakes and the lifespan. A compromised laptop is a data problem. A compromised device can be a patient-safety problem, and the device may stay in clinical use for ten years or more, long after the software inside it was written. Security has to be designed in, documented for regulators, and maintained for the device's whole life.

2. Why it matters now

Cybersecurity moved from guidance to law. Section 524B of the Federal Food, Drug, and Cosmetic Act, added in 2023, gives the FDA explicit authority over the cybersecurity of "cyber devices": devices that include software, can connect to the internet, and could be vulnerable to cybersecurity threats. Since October 2023, the FDA can refuse to accept a premarket submission for a cyber device that lacks the required cybersecurity information.

Two other shifts raise the bar further:

  • Quality system expectations. The FDA's Quality Management System Regulation (QMSR), effective February 2, 2026, aligns US requirements with ISO 13485. Cybersecurity is expected to be part of design controls and risk management, not a document added at the end.
  • Deficiency letters. Cybersecurity is now a frequent reason for deficiency letters and additional-information requests, which add months to a review.See how to respond

3. FDA cybersecurity requirements

Section 524B requires manufacturers of cyber devices to:

  1. Submit a plan to monitor, identify and address postmarket vulnerabilities and exploits, including coordinated vulnerability disclosure.
  2. Design, develop and maintain processes that provide reasonable assurance the device and related systems are cybersecure, and make updates and patches available.
  3. Provide a software bill of materials (SBOM) covering commercial, open-source and off-the-shelf components.

The FDA's premarket cybersecurity guidance spells out the documentation reviewers expect, including:

  • A security risk management report, threat model and cybersecurity risk assessment
  • Security architecture views showing how the device connects and how it is updated
  • Security controls across authentication, authorization, cryptography, integrity, confidentiality, event detection, resiliency and updatability
  • Cybersecurity testing, including penetration testing
  • An SBOM with support status and a review of known vulnerabilities
  • Cybersecurity labeling for users and a postmarket cybersecurity management plan

4. Standards that matter

Regulators point to a small set of consensus standards. Following them is the most direct way to show reviewers your process is sound.

StandardWhat it covers
IEC 81001-5-1Security activities across the health software lifecycle: the secure development process itself
ANSI/AAMI SW96Security risk management for device manufacturers, aligned with ISO 14971 safety risk management
AAMI TIR57Principles for medical device security risk management
AAMI TIR97Postmarket security risk management
IEC 62443Security for industrial and networked systems, often used for connected device architecture
UL 2900-2-1Security testing for network-connectable healthcare components

5. Beyond the US: EU and Canada

European Union. The EU Medical Device Regulation (MDR) includes cybersecurity in its general safety and performance requirements (Annex I), covering secure design, protection against unauthorized access, and minimum IT security requirements. Guidance document MDCG 2019-16 explains how manufacturers should meet them.

Canada. Health Canada expects cybersecurity evidence in premarket applications for connected devices, including risk management, testing and a plan for postmarket monitoring.

The documentation overlaps heavily across regions. Built once and maintained in one place, the same threat model, SBOM and test evidence can support FDA, EU and Health Canada submissions.

6. Building security in: the premarket work

The cheapest time to fix a security weakness is before the device is built. Premarket cybersecurity work usually includes:

  • Threat modeling

    A structured look at how the device could be attacked and what that would mean for patients. It anchors the risk assessment reviewers read first.

    Threat modeling
  • Security architecture

    Diagrams and controls showing how data moves, how the device authenticates, and how it receives updates.

    Build security in from design
  • Cryptography and key management

    Protecting data and verifying software with keys that can be managed and rotated over the device's life.

    Harden encryption and keys
  • Penetration testing

    Independent testing that tries to break the device the way an attacker would, with findings traced back into the risk assessment.

    Medical device penetration testing

7. SBOM and vulnerability management

A software bill of materials (SBOM) lists every software component in a device: commercial, open-source and off-the-shelf. It is how a manufacturer, and a hospital, finds out whether a newly disclosed vulnerability affects a device.

Producing an SBOM for a submission is the easy part. Keeping it accurate across every release, matching components to vulnerability databases, and deciding which vulnerabilities actually matter is ongoing work. Most teams struggle with three things:

  • Matching. Components often don't map cleanly to vulnerability databases, so real issues are missed or false ones pile up.
  • Prioritization. Thousands of findings, each scored with CVSS, a scale built for IT that doesn't capture patient-safety impact.Why CVSS is flawed but still essential
  • Evidence. Showing reviewers, and later auditors, how each vulnerability was assessed and why.

8. Postmarket cybersecurity

Clearance starts the clock rather than stopping it. Once a device is in the field, manufacturers are expected to:

  • Monitor for new vulnerabilities in the device and its components, and assess whether they create patient risk.
  • Run coordinated vulnerability disclosure (CVD). A public way for researchers to report issues, with triage and communication timelines.Coordinated vulnerability disclosure
  • Respond to incidents quickly, with a plan agreed before one happens.Respond to incidents fast
  • Manage legacy devices that can no longer be fully patched, using compensating controls and clear communication to customers.Legacy device cybersecurity

9. By device type

The requirements are the same, but the threats and trade-offs differ by device.

  • Cardiac devices

    Implanted and wearable devices where availability and battery life limit which security controls fit.

    Cardiac
  • Diabetes devices

    Pumps, sensors and apps that exchange data constantly, often over Bluetooth and phones.

    Diabetes
  • IVD and diagnostics

    Lab instruments on hospital networks, where data integrity matters as much as uptime.

    IVD
  • Medical imaging

    Large systems with long service lives and many legacy components.

    Medical imaging
  • Ophthalmic devices

    Connected diagnostic and surgical systems in clinic settings.

    Ophthalmic
  • Software as a medical device (SaMD)

    Cloud and mobile software where the whole product is the attack surface.

    SaMD
  • Surgical robotics

    Complex systems where security failures can affect a procedure in real time.

    Surgical robotics

10. Choosing a partner

Most manufacturers bring in outside help for at least part of this work. Look for regulatory fluency (people who have reviewed submissions from the regulator's side), a real clearance track record, and coverage from premarket through postmarket in one system, so the threat model, SBOM and vulnerability records stay consistent.

11. Frequently asked questions

Know where you are in 1 hour.

Run the free check or talk to a human. Either way, you’ll get a clearer view of readiness without a paywall or lengthy sales call.