Cybersecurity: FDA Risks for Medical Devices

by Sheppard Mullin Richter & Hampton LLP

On Thursday, June 13, 2013, the U.S. Food and Drug Administration (“FDA”) released a draft guidance on measures to help ensure the cybersecurity of medical devices. The draft guidance, titled “Content of Premarket Submissions for Management of Cybersecurity in Medical Devices,” proposes cybersecurity features that should be incorporated into wireless, Internet- and network-connected medical devices (“cybersecurity-vulnerable devices”), as well as information that will be requested in premarket submissions for cybersecurity-vulnerable devices. In addition to the draft guidance, FDA also issued an FDA Safety Communication to medical device manufacturers, hospitals, medical device user facilities, health care IT and procurements staff, and biomedical engineers on cybersecurity for medical devices and hospital networks.

Cybersecurity vulnerability has been an increasing concern for medical devices. A Department of Homeland Security (“DHS”) intelligence bulletin issued in May 2012 noted that “[t]hese vulnerabilities may result in possible risks to patient safety and theft or loss of medical information.” One of the issues noted by the DHS is that “system owners may be reluctant to allow manufacturers access for upgrades or updates.” This reluctance arises out of concerns about access to “sensitive or privacy information,” where the “[f]ailure to install updates lays a foundation for increasingly ineffective threat mitigation as time passes.”

The draft guidance notes that manufacturers of cybersecurity-vulnerable devices should ensure confidentiality, integrity, and availability of data. Although FDA’s draft guidance and safety communication make no mention of either the Health Insurance Portability and Accountability Act (HIPAA), or the Health Information Technology for Economic and Clinical Health Act (HITECH), compliance with HIPAA and HITECH may be one of the standards by which FDA evaluates device cybersecurity. While device manufacturers are generally not subject to HIPAA and HITECH,[1] they have become increasingly sensitive to the needs of customers that must themselves be compliant with these laws.

The draft guidance identifies a number of features that cybersecurity-vulnerable devices are recommended to incorporate. These features fall within three general categories addressing limiting access to trusted users, ensuring trusted content, and incorporating fail safe and recovery features. Some of the features include requiring authentication of users through a user ID and password, smartcard, or biometric, and using data encryption.

Along with the recommended features, the draft guidance also identifies information that should be included in a device premarket submission. This draws upon the extensive information that is already provided in submissions for medical devices that contain software. In particular, the draft guidance recommends that the hazard analysis provided in the submission include the identified cybersecurity risks and the controls put in place to mitigate those risks. The product life-cycle plan should include a discussion on how validated updates and patches to operating systems or medical device software will be provided. The instructions for use are also recommended to include information on appropriate anti-virus software and firewall settings.

One concern raised by the draft guidance and the safety communication is how to handle reporting of cybersecurity modifications to medical device software. Whenever medical device software is updated, manufacturers must address whether the update is reportable as a correction or removal under 21 C.F.R. part 806, and whether the update requires the filing of a new premarket submission with FDA. In FDA’s previous guidance on cybersecurity, “Cybersecurity for Networked Medical Devices Containing Off-the-Shelf (OTS) Software,” issued on January 14, 2005, FDA noted that manufacturers would generally not report a cybersecurity patch as a correction or removal, “because most software patches are installed to reduce the risk of developing a problem associated with a cybersecurity vulnerability and not to address a risk to health posed by the device.” Similarly, in addressing whether premarket review would be required prior to implementation of a software patch to address a cybersecurity vulnerability, FDA’s previous guidance noted that manufacturers would “[u]sually not” be required to provide a submission for review given that “review is [generally] necessary when a change or modification could significantly affect the safety or effectiveness of the medical device.”

FDA’s safety communication suggests that FDA may be in the process of reconsidering the impact that cybersecurity vulnerabilities have on device safety and effectiveness. The safety communication notes that “[c]ybersecurity incidents are increasingly likely,” and that FDA believes such “cybersecurity vulnerabilities and incidents . . . could directly impact medical devices or hospital network operations.” Despite this increased focus, FDA has not rescinded its prior guidance “Cybersecurity for Networked Medical Devices Containing Off-the-Shelf (OTS) Software,” and noted in the recent safety communication that “FDA typically does not need to review or approve medical device software changes made solely to strengthen cybersecurity.”

Manufacturers currently marketing cybersecurity-vulnerable devices should conduct a comprehensive review of their marketed devices for any potential cybersecurity threats. It is likely that the issue of cybersecurity will be a part of FDA medical device establishment inspections. Further, FDA’s recent safety communication suggests that “manufacturers should consider [developing] incident response plans that address the possibility of degraded operation and efficient restoration and recovery” caused by cybersecurity vulnerabilities.

Manufacturers currently developing cybersecurity-vulnerable devices should cover cybersecurity risks during the design control process required under 21 C.F.R. 820.30. It is possible that FDA’s draft guidance may be finalized this year. Even if the guidance remains in draft form, the recommendations may potentially be incorporated into FDA’s premarket review.

Health care facilities are recommended to take steps to evaluate network security and protect hospital networks from cybersecurity risks. This includes monitoring network activity for unauthorized use, and updating security patches and disabling all unnecessary ports and services for each individual network component.

[1] Device manufacturers may offer a service to a customer covered by HIPAA and HITECH (called “covered entities” in HIPAA), that creates a “Business Associate” relationship with the covered entity. In that situation, the device manufacturer would be subject to HIPAA and HITECH. An example of such a service may be the remote storage of protected health information collected by a medical device.


DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Sheppard Mullin Richter & Hampton LLP | Attorney Advertising

Written by:

Sheppard Mullin Richter & Hampton LLP

Sheppard Mullin Richter & Hampton LLP on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
Sign up using*

Already signed up? Log in here

*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
Privacy Policy (Updated: October 8, 2015):

JD Supra provides users with access to its legal industry publishing services (the "Service") through its website (the "Website") as well as through other sources. Our policies with regard to data collection and use of personal information of users of the Service, regardless of the manner in which users access the Service, and visitors to the Website are set forth in this statement ("Policy"). By using the Service, you signify your acceptance of this Policy.

Information Collection and Use by JD Supra

JD Supra collects users' names, companies, titles, e-mail address and industry. JD Supra also tracks the pages that users visit, logs IP addresses and aggregates non-personally identifiable user data and browser type. This data is gathered using cookies and other technologies.

The information and data collected is used to authenticate users and to send notifications relating to the Service, including email alerts to which users have subscribed; to manage the Service and Website, to improve the Service and to customize the user's experience. This information is also provided to the authors of the content to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

JD Supra does not sell, rent or otherwise provide your details to third parties, other than to the authors of the content on JD Supra.

If you prefer not to enable cookies, you may change your browser settings to disable cookies; however, please note that rejecting cookies while visiting the Website may result in certain parts of the Website not operating correctly or as efficiently as if cookies were allowed.

Email Choice/Opt-out

Users who opt in to receive emails may choose to no longer receive e-mail updates and newsletters by selecting the "opt-out of future email" option in the email they receive from JD Supra or in their JD Supra account management screen.


JD Supra takes reasonable precautions to insure that user information is kept private. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. However, please note that no method of transmitting or storing data is completely secure and we cannot guarantee the security of user information. Unauthorized entry or use, hardware or software failure, and other factors may compromise the security of user information at any time.

If you have reason to believe that your interaction with us is no longer secure, you must immediately notify us of the problem by contacting us at In the unlikely event that we believe that the security of your user information in our possession or control may have been compromised, we may seek to notify you of that development and, if so, will endeavor to do so as promptly as practicable under the circumstances.

Sharing and Disclosure of Information JD Supra Collects

Except as otherwise described in this privacy statement, JD Supra will not disclose personal information to any third party unless we believe that disclosure is necessary to: (1) comply with applicable laws; (2) respond to governmental inquiries or requests; (3) comply with valid legal process; (4) protect the rights, privacy, safety or property of JD Supra, users of the Service, Website visitors or the public; (5) permit us to pursue available remedies or limit the damages that we may sustain; and (6) enforce our Terms & Conditions of Use.

In the event there is a change in the corporate structure of JD Supra such as, but not limited to, merger, consolidation, sale, liquidation or transfer of substantial assets, JD Supra may, in its sole discretion, transfer, sell or assign information collected on and through the Service to one or more affiliated or unaffiliated third parties.

Links to Other Websites

This Website and the Service may contain links to other websites. The operator of such other websites may collect information about you, including through cookies or other technologies. If you are using the Service through the Website and link to another site, you will leave the Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We shall have no responsibility or liability for your visitation to, and the data collection and use practices of, such other sites. This Policy applies solely to the information collected in connection with your use of this Website and does not apply to any practices conducted offline or in connection with any other websites.

Changes in Our Privacy Policy

We reserve the right to change this Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our privacy policy will become effective upon posting of the revised policy on the Website. By continuing to use the Service or Website following such changes, you will be deemed to have agreed to such changes. If you do not agree with the terms of this Policy, as it may be amended from time to time, in whole or part, please do not continue using the Service or the Website.

Contacting JD Supra

If you have any questions about this privacy statement, the practices of this site, your dealings with this Web site, or if you would like to change any of the information you have provided to us, please contact us at:

- hide
*With LinkedIn, you don't need to create a separate login to manage your free JD Supra account, and we can make suggestions based on your needs and interests. We will not post anything on LinkedIn in your name. Or, sign up using your email address.