United States: FDA Finalizes Guidance On Postmarket Management Of Medical Device Cybersecurity

On December 28, 2016, the Food and Drug Administration (FDA) issued final guidance on the postmarket management of cybersecurity in medical devices.1 The guidance outlines nonbinding recommendations on how device manufacturers should monitor, identify, and address cybersecurity vulnerabilities. It also describes a risk-based framework to help manufacturers determine when device modifications that address cybersecurity vulnerabilities must be reported to FDA.

Device manufacturers should review this final guidance and consider how to incorporate its recommendations into their postmarket management activities. This Alert summarizes key aspects of the guidance and identifies key differences from the draft version issued in January 2016.2

I. General Principles of a Postmarket Cybersecurity Management Program

The growing use of networked medical devices has opened important new avenues for improving patient care. At the same time, these developments have increased the exposure of devices and computer networks to cybersecurity threats. Failure to maintain cybersecurity can impact device functionality and result in patient harm, loss of data, or exposure of other connected devices to security threats.

To address cybersecurity vulnerabilities during the premarket development stage, FDA has previously recommended that manufacturers consider cybersecurity during the design and software validation process for a device. FDA's recommendations are outlined in its 2014 guidance, "Content of Premarket Submissions for Management of Cybersecurity in Medical Devices," discussed in a previous Ropes & Gray Alert.

Recognizing that not all cybersecurity risks can be foreseen and mitigated solely through premarket activities, however, FDA considers it essential that manufacturers implement postmarket cybersecurity risk management programs. The final postmarket cybersecurity guidance recommends that a postmarket cybersecurity risk management program address vulnerabilities that may permit unauthorized access, modification, misuse, or denial of use of a device, or the unauthorized use of information that is stored, accessed, or transferred from a medical device to an external recipient, and that may result in patient harm. Specifically, FDA recommends that such a program include the following critical components:

  • Monitoring cybersecurity information sources for identification and detection of cybersecurity vulnerabilities and risks;
  • Maintaining robust software lifecycle processes that include mechanisms for monitoring third-party software components for new vulnerabilities and performing design validation and validation for software updates and patches used to remediate vulnerabilities;
  • Understanding, assessing and detecting vulnerabilities;
  • Establishing and communicating processes for cybersecurity vulnerability intake and handling;
  • Using threat modeling to define how to maintain safety and essential performance of a device by developing mitigations that protect, respond, and recover from a cybersecurity risk;
  • Adopting a coordinated vulnerability disclosure policy and practice; and
  • Deploying mitigations that address cybersecurity risk early and prior to exploitation.

FDA's guidance recognizes that cybersecurity is a shared responsibility between public and private stakeholders, a principle set forth in Presidential Policy Directive 21 – Critical Infrastructure Security and Resilience. FDA encourages device manufacturers to adopt the recommendations on cybersecurity set out in the voluntary "Framework for Improvement Critical Infrastructure Cybersecurity" published by the National Institute of Standards and Technology (NIST), with collective input from various government agencies and the private sector. FDA also encourages device manufacturers to look to standards, guidelines, best practices, and frameworks established by the security industry to adopt a culture of cybersecurity risk management. In addition, FDA specifically encourages device manufacturers to share cybersecurity threat information as active participants in Information Sharing Analysis Organizations (ISAOs) and to be aware of sources of cybersecurity threat information that fall outside their typical information sources, such as the U.S. Department of Homeland Security Industrial Control Systems Cyber Emergency Response Team (ICS-CERT).

II. Cybersecurity Risk Management

FDA recommends that a manufacturer establish, document, and maintain throughout the lifecycle of a device an ongoing process for identifying cybersecurity hazards, estimating and evaluating the associated risks, controlling those risks, and monitoring the effectiveness of the controls. FDA believes that this process should include risk analysis, risk evaluation, risk control, and incorporation of production and post-production information. In evaluating the risk of patient harm, FDA recommends that manufacturers take into account the exploitability of the cybersecurity vulnerability and the severity of patient harm if the vulnerability were to be exploited.

The guidance also encourages manufacturers to define, as part of their comprehensive cybersecurity risk management program, the safety and essential performance characteristics of their devices, the resulting severity of patient harm if the cybersecurity of the device is compromised, and associated risk acceptance criteria. FDA defines "patient harm" to be physical injury or damage to the health of patients. FDA emphasizes threat modeling as a tool to facilitate the understanding and assessment of the vulnerability and the potential for patient harm. Threat modeling also helps determine whether a proposed remediation can be expected to control a risk of patient harm, such that the risk is an acceptable one. FDA recommends that manufacturers consider employing a cybersecurity vulnerability assessment tool or similar scoring system for assessing vulnerabilities and determining the need for, and urgency of, the response. FDA identifies one such tool in the guidance, the Common Vulnerability Scoring System, Version 3.0, as well as a number of additional standards and guidelines that may help triage vulnerabilities.

III. Remediating and Reporting Cybersecurity Vulnerabilities

Using the risk management tools and processes described above, FDA advises manufacturers to reach a binary determination on whether a particular risk is controlled or uncontrolled. If the risk is uncontrolled, FDA recommends implementing additional remediation measures until the risk is controlled. In the guidance, FDA encourages manufacturers to engage in efficient, timely, and ongoing assessment of cybersecurity risks in marketed devices. For routine cybersecurity software updates and patches, FDA states that it will not typically require premarket review to clear or approve the software changes. In addition, when a manufacturer strengthens a device's cybersecurity to address controlled risks of patient harm (i.e., where there is already sufficiently low residual risk of patient harm to the vulnerability), FDA considers those changes to be device "enhancements," as opposed to device "corrections." As a result, such changes are not required to be reported as device corrections under 21 C.F.R. Part 806. FDA also states that changes to a device made solely to address loss of confidentiality of patient information are typically device enhancements that would not be required to be reported under 21 C.F.R. Part 806.

In contrast, when a manufacturer takes action to remediate an otherwise uncontrolled risk of patient harm (i.e., where there is unacceptable residual risk of patient harm due in the absence of additional risk mitigations), FDA states that a manufacturer should evaluate the device changes to assess the need to submit a premarket submission to the FDA (e.g., premarket approval application (PMA) supplement or a 510(k)). FDA explains that, in the absence of remediation, a device with uncontrolled risk of patient harm may be considered in violation of the Federal Food, Drug, and Cosmetic Act and be subject to enforcement action.

In addition, FDA states that remediations of uncontrolled risks would ordinarily be required to be reported to the agency as removals or corrections under 21 C.F.R. Part 806. However, through the guidance, FDA explains that it is establishing an enforcement discretion policy whereby FDA does not intend to enforce reporting requirements under 21 C.F.R. Part 806 for changes to address uncontrolled risks under certain circumstances. Specifically, FDA will not enforce reporting requirements if:

  1. There are no known serious adverse events or deaths associated with the vulnerability;
  2. Within 30 days of learning of the vulnerability, the manufacturer notifies users of the vulnerability and identifies and implements a device change to bring the residual risk to an acceptable level;
  3. No later than 60 days after learning of the vulnerability, the manufacturer validates, implements, and distributes the deployable fix to its customers; and
  4. The manufacturer is an active participating member of an Information Sharing Analysis Organization (ISAO).

Device manufacturers should consider whether to modify their procedures for correction and removal reporting under 21 C.F.R. Part 806 to reflect this FDA policy.

FDA also explains that, for both controlled and uncontrolled risks, a manufacturer's changes to address those should be submitted in a periodic report to FDA if the device is approved under a PMA.3

IV. Criteria for Defining Active Participation by a Manufacturer in an ISAO

As noted above, one of the criteria for FDA's enforcement discretion policy on the reportability of non-routine cybsecurity-related device changes is whether the manufacturer is an active participating member of an ISAO. The final guidance lays out criteria for what it means to be an active participating ISAO member. Specifically, FDA says that it will consider whether:

  • The manufacturer is a member of an ISAO that shares vulnerabilities and threats that impact medical devices;
  • The ISAO has documented policies pertaining to participant agreements, business processes, operating procedures, and privacy protections;
  • The manufacturer shares vulnerability information with the ISAO, including any customer communications pertaining to cybersecurity vulnerabilities; and
  • The manufacturer has documented processes for assessing and responding to vulnerability and threat intelligence information received from the ISAO.

FDA recommends that manufacturers maintain objective evidence to demonstrate that their participation in an ISAO meets these criteria. FDA also notes that the agency's Center for Devices and Radiological Health has entered into a Memorandum of Understanding with one ISAO, the National Health Information Sharing & Analysis Center (NH-ISAC). FDA does not, however, take the position that manufacturers must participate in the NH-ISAC to meet the agency's criteria for ISAO participation.

V. Key Differences from Draft Guidance

The final guidance differs from the draft in several important respects. Among other things, the final guidance:

  • Uses the potential for patient harm, rather than risk to the safety and effectiveness of the device itself, as the touchstone for assessing risks posed by cybersecurity vulnerabilities. This change focuses the guidance's risk management recommendations activities around risk to health, a concept with which device manufacturers are familiar from existing FDA regulations, rather than the new concept of "essential clinical performance" of a device that FDA had emphasized in the draft guidance.
  • Extends to 60 days the time that device manufacturers have to remediate an uncontrolled risk while remaining subject to FDA's enforcement discretion policy for reporting a device correction under 21 C.F.R. Part 806, provided that the manufacturer communicates interim controls to its customers and the user community within 30 days after learning of the vulnerability. The draft guidance would have provided only 30 days to identify and implement device changes or controls to bring the risk to an acceptable level.
  • Provides additional details and guidance to manufacturers on a number of subjects, including sources of guidance for performing risk management activities, the criteria for being considered an active participant in an ISAO, and additional examples of how to determine whether a risk is controlled or uncontrolled.

VI. Consequences for Medical Device Manufacturers

The increasing sophistication of software-driven and networked medical devices is delivering huge improvements in medical care, but also presents the potential for risks to patient health and privacy due to cybersecurity vulnerabilities. FDA's guidance document reflects the increasing expectations on device manufacturers to establish sophisticated, proactive cybersecurity practices and procedures that begin when a device is initially being designed and continue throughout the device lifecycle. Device manufacturers that have not already done so should consider conducting a comprehensive assessment of their cybersecurity practices and procedures, taking into account the recommendations in the FDA pre- and post-market guidance documents and third-party standards, and evaluate whether to become an active participant in an ISAO.


1. FDA Guidance, "Postmarket Management of Cybersecurity in Medical Devices" (Dec. 28, 2016).

2. FDA Draft Guidance, "Postmarket Management of Cybersecurity in Medical Devices" (Jan. 15, 2016). See Ropes & Gray's previous Alert on the draft guidance.

3. See 21 C.F.R. § 814.84.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.