1. Home
  2. |Insights
  3. |Cybersecurity in Medical Devices: FDA Guidance and Product Liability Considerations

Cybersecurity in Medical Devices: FDA Guidance and Product Liability Considerations

Client Alert | 3 min read | 11.17.23

The number of medical devices with wireless and network-connected capabilities continues to grow. At the same time, by some reports the number of ransomware attacks on health care facilities has more than doubled in recent years.[1] Recent cyberattacks and/or ransomware attacks on healthcare systems have resulted in stolen patient data, emergency room closures, diversion of ambulances, and cancellation of surgeries and other appointments. Given the potential disruptions in patient care in connection with these incidents, the cybersecurity of medical devices with wireless and network-connected capabilities becomes increasingly important to avoid and mitigate these possible impacts.

Against this backdrop, the Federal Food and Drug Administration (FDA) recently published its final guidance on “Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions.”[2] This guidance sets forth FDA’s recommendations regarding cybersecurity controls to help ensure device safety and effectiveness, both pre- and post-market. And while FDA’s guidance does not have the force of law, adherence to the guidance will help medical device manufacturers and sponsors meet regulatory expectations with respect to cybersecurity.

Among numerous highly-detailed technical recommendations, FDA’s new cybersecurity guidance highlights the overarching general principles that FDA uses to frame its regulatory approach:

  1. Cybersecurity is part of device safety and the quality system regulations. Under the broadly-applicable quality systems requirements, 21 CFR Part 820, all device manufacturers and sponsors must establish and follow quality systems to help ensure that their products consistently meet applicable requirements and specifications. FDA’s guidance shows—and provides examples of—how documentation that may be relevant to a device manufacturer or sponsor’s compliance with the quality systems requirements can also be used to show how it is addressing cybersecurity considerations for the device.
  2. Designing for security. FDA recommends that going forward, device manufacturers and sponsors include information in their premarket submissions regarding how FDA’s security objectives—such as authenticity, authorization, and confidentiality—are addressed by the device’s design.
  3. FDA recognizes that a lack of cybersecurity information for device users has the potential to impact the safety and effectiveness of a device throughout its lifespan. Accordingly, FDA recommends that cybersecurity information be included in the device labeling.
  4. Submission documentation. FDA also recognizes that the necessary cybersecurity submission documentation will likely be tailored to the cybersecurity risk of each specific device. This means that for device cybersecurity, manufacturers and sponsors of more complex devices will be expected to provide more detailed and thorough submissions that reflect more rigorous testing.

While FDA’s guidance is primarily prospective, its existence and the realities it is intended to confront highlight potential uses for the guidance in the event of product liability litigation. For example:

  • Where a device is approved though FDA’s pre-market approval process, compliance with FDA’s cybersecurity guidance may support the pre-emption of certain legal claims regarding the device’s design, labeling and warnings.
  • Maintaining the type of robust documentation that FDA recommends in the guidance may be helpful in defending a product liability suit.
  • Abiding by FDA’s recommendations in this new guidance may make available to device manufacturers or sponsors a regulatory compliance defense to a products liability claim that is available under the common law of certain states.

At bottom, medical device manufacturers and sponsors should familiarize themselves with the technical and broader implications of FDA’s guidance and take steps to ensure compliance. Though we are unaware of extensive product liability litigation concerning cybersecurity of a medical device at present, we will report on new developments in what could be a burgeoning area of the law.

Insights

Client Alert | 5 min read | 12.12.25

Eleventh Circuit Hears Argument on False Claims Act Qui Tam Constitutionality

On the morning of December 12, 2025, the Eleventh Circuit heard argument in United States ex rel. Zafirov v. Florida Medical Associates, LLC, et al., No. 24-13581 (11th Cir. 2025). This case concerns the constitutionality of the False Claims Act (FCA) qui tam provisions and a groundbreaking September 2024 opinion in which the United States District Court for the Middle District of Florida held that the FCA’s qui tam provisions were unconstitutional under Article II. See United States ex rel. Zafirov v. Fla. Med. Assocs., LLC, 751 F. Supp. 3d 1293 (M.D. Fla. 2024). That decision, penned by District Judge Kathryn Kimball Mizelle, was the first success story for a legal theory that has been gaining steam ever since Justices Thomas, Barrett, and Kavanaugh indicated they would be willing to consider arguments about the constitutionality of the qui tam provisions in U.S. ex rel. Polansky v. Exec. Health Res., 599 U.S. 419 (2023). In her opinion, Judge Mizelle held (1) qui tam relators are officers of the U.S. who must be appointed under the Appointments Clause; and (2) historical practice treating qui tam and similar relators as less than “officers” for constitutional purposes was not enough to save the qui tam provisions from the fundamental Article II infirmity the court identified. That ruling was appealed and, after full briefing, including by the government and a bevy of amici, the litigants stepped up to the plate this morning for oral argument....