{"id":4577,"date":"2016-02-01T01:27:00","date_gmt":"2016-02-01T01:27:00","guid":{"rendered":"https:\/\/www.healthlawpolicymatters.com\/?p=4577"},"modified":"2021-11-03T01:28:54","modified_gmt":"2021-11-03T01:28:54","slug":"fda-releases-draft-guidance-for-medical-device-cybersecurity","status":"publish","type":"post","link":"https:\/\/www.healthlawpolicymatters.com\/2016\/02\/01\/fda-releases-draft-guidance-for-medical-device-cybersecurity\/","title":{"rendered":"FDA Releases Draft Guidance for Medical Device Cybersecurity"},"content":{"rendered":"\n<p>It seems that everything in our life is getting&nbsp;connected to the Internet. We now live in an age where&nbsp;<a href=\"http:\/\/www.cnet.com\/news\/samsungs-super-fridge-packs-everything-but-the-kitchen-sink\/\">household items&nbsp;like refrigerators<\/a>&nbsp;have&nbsp;Internet-connected LCD screens and privacy experts talk about the so-called \u201cInternet of Things.\u201d Medical devices are increasingly becoming connected as well,&nbsp;and like any connected device, they are at risk of getting hacked. &nbsp;In 2014,&nbsp;the U.S. Food and Drug Administration (\u201cFDA\u201d) released final guidance recommending that device manufacturers consider cybersecurity risks when designing and developing their devices. Last month, FDA released separate&nbsp;<a href=\"http:\/\/www.fda.gov\/downloads\/MedicalDevices\/DeviceRegulationandGuidance\/GuidanceDocuments\/UCM482022.pdf\" target=\"_blank\" rel=\"noreferrer noopener\">draft guidance<\/a>&nbsp;with recommendations for how companies should address the cybersecurity of medical devices after they are released into the market.<\/p>\n\n\n\n<p><em>Principles of a Postmarket Cybersecurity Management Program<\/em><\/p>\n\n\n\n<p>The cornerstone of FDA\u2019s cybersecurity guidance for industry \u2014 in both the premarket and postmarket context \u2014&nbsp; is the development of a risk management program. In its new guidance,&nbsp;the FDA identifies a number of critical components that should be included in the device manufacturer\u2019s postmarket&nbsp;risk management program. These include:<\/p>\n\n\n\n<ul><li>Monitoring cybersecurity information sources for identification and detection of cybersecurity vulnerabilities and risk;<\/li><li>Understanding, assessing, and detecting presence and impact of a vulnerability;<\/li><li>Establishing and communicating processes for vulnerability intake and handling;<\/li><li>Clearly defining essential clinical performance to develop mitigations that protect, respond, and recover from the cybersecurity risk;<\/li><li>Adopting a coordinated vulnerability disclosure policy and practice; and<\/li><li>Deploying mitigations that address cybersecurity risk early and prior to exploitation.<\/li><\/ul>\n\n\n\n<p><em>Essential Clinical Performance<\/em><\/p>\n\n\n\n<p>The fourth component mentioned above&nbsp;introduces a&nbsp;concept that is central to the guidance: \u201cessential clinical performance.\u201d As noted by FDA, the majority of actions taken by manufacturers to address cybersecurity vulnerabilities and exploits are considered \u201ccybersecurity routine updates or patches.\u201d In these cases, the FDA&nbsp;would not require advance notification, premarket review or reporting under its regulations. However, a small subset of vulnerabilities and exploits may, according to the draft guidance, compromise the&nbsp;<strong>essential clinical performance<\/strong>&nbsp;of a device and thus present a reasonable probability of serious adverse health consequences or death. In these circumstances, FDA would require the manufacturer to notify the agency. FDA defines essential clinical performance as \u201cperformance that is necessary to achieve freedom from unacceptable clinical risk, as defined by the manufacturer.\u201d<\/p>\n\n\n\n<p>According to the draft guidance, manufacturers should define the essential clinical performance of their device, the resulting severity outcomes if compromised, and the risk acceptance criteria. Manufacturers should conduct this analysis in an objective manner by considering two factors:<\/p>\n\n\n\n<ol><li>The exploitability of the cybersecurity vulnerability; and<\/li><li>The severity of the health impact to patients if the vulnerability were to be exploited.<\/li><\/ol>\n\n\n\n<p>FDA acknowledges that objectively assessing the exploitability of a device is&nbsp;difficult, especially if there is&nbsp;an&nbsp;absence of data. Instead of using conventional medical device risk management approaches, FDA suggests that manufacturers consider using a cybersecurity vulnerability assessment tool or similar scoring system, such as the Common Vulnerability Scoring System.&nbsp;In terms of objectively assessing the severity of the health impact, moreover, FDA recommends that manufacturers&nbsp;use the qualitative severity levels described in the International Standard Organization\u2019s Standard for the application of risk management to medical devices.<\/p>\n\n\n\n<p><em>Controlled vs. Uncontrolled Risks<\/em><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter\"><img decoding=\"async\" src=\"https:\/\/web.archive.org\/web\/20160415132733im_\/https:\/\/www.healthlawpolicymatters.com\/wp-content\/uploads\/sites\/8\/2016\/01\/controlled_uncontrolled.jpg\" alt=\"controlled_uncontrolled\" class=\"wp-image-7708\"\/><\/figure><\/div>\n\n\n\n<p>According to FDA, a key purpose of conducting the above assessment is to evaluate whether the risk to essential clinical performance of the device is controlled (acceptable) or uncontrolled (unacceptable). One method of assessing the acceptability of risk to essential clinical performance is by indicating in a matrix which combinations of \u201cexploitability\u201d and \u201cseverity impact to health\u201d represent risks that are controlled or uncontrolled. The draft guidance&nbsp;contains&nbsp;an example of an approach that could be used to assess the risk to the device\u2019s essential clinical performance: &nbsp;<\/p>\n\n\n\n<p>As is apparent from the matrix above, not every assessment will yield a black or white result. FDA acknowledges this grey area, but nevertheless recommends that manufacturers make a binary determination that a vulnerability is either controlled or uncontrolled. The result of this binary determination is crucial:&nbsp;if a manufacturer concludes&nbsp;that there is uncontrolled risk to their device\u2019s essential clinical performance, FDA expects the manufacturer to report these vulnerabilities to FDA according to 21 C.F.R. 806 (mandatory reports of product corrections or removals). &nbsp;At the same time,&nbsp;the FDA has also decided to exercise discretion in this area, and it does not intend to enforce these reporting requirements if:<\/p>\n\n\n\n<ol><li>There are no known serious adverse events or deaths associated with the vulnerability;<\/li><li>Within 30 days of learning of the vulnerability, the manufacturer identifies and implements device changes and\/or compensating controls to bring the residual risk to an acceptable level and notifies users; and<\/li><li>The manufacturer is a participating member of an Information Sharing Analysis Organization (\u201cISAO\u201d), such as the National Health Information Sharing &amp; Analysis Center.<\/li><\/ol>\n\n\n\n<p>The fact that FDA makes participation in an ISAO a condition of the agency\u2019s&nbsp;discretionary enforcement sends a strong message to device manufacturers that cooperation across the industry is a critical component of postmarket cybersecurity. To this end, the agency recently held a&nbsp;<a href=\"http:\/\/www.fda.gov\/MedicalDevices\/NewsEvents\/WorkshopsConferences\/ucm474752.htm\" target=\"_blank\" rel=\"noreferrer noopener\">public worksho<\/a>p to discuss these issues,&nbsp;which we plan to highlight in a future blog post.&nbsp; In the meantime, interested parties can submit comments on the new cybersecurity draft guidance until April 21, 2016.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It seems that everything in our life is getting&nbsp;connected to the Internet. We now live in an age where&nbsp;household items&nbsp;like refrigerators&nbsp;have&nbsp;Internet-connected LCD screens and privacy experts talk about the so-called \u201cInternet of Things.\u201d Medical devices are increasingly becoming connected as well,&nbsp;and like any connected device, they are at risk of getting hacked. &nbsp;In 2014,&nbsp;the U.S. &#8230; <a title=\"FDA Releases Draft Guidance for Medical Device Cybersecurity\" class=\"read-more\" href=\"https:\/\/www.healthlawpolicymatters.com\/2016\/02\/01\/fda-releases-draft-guidance-for-medical-device-cybersecurity\/\" aria-label=\"More on FDA Releases Draft Guidance for Medical Device Cybersecurity\">Read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_generate-full-width-content":"","footnotes":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.healthlawpolicymatters.com\/wp-json\/wp\/v2\/posts\/4577"}],"collection":[{"href":"https:\/\/www.healthlawpolicymatters.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.healthlawpolicymatters.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.healthlawpolicymatters.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.healthlawpolicymatters.com\/wp-json\/wp\/v2\/comments?post=4577"}],"version-history":[{"count":3,"href":"https:\/\/www.healthlawpolicymatters.com\/wp-json\/wp\/v2\/posts\/4577\/revisions"}],"predecessor-version":[{"id":4580,"href":"https:\/\/www.healthlawpolicymatters.com\/wp-json\/wp\/v2\/posts\/4577\/revisions\/4580"}],"wp:attachment":[{"href":"https:\/\/www.healthlawpolicymatters.com\/wp-json\/wp\/v2\/media?parent=4577"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.healthlawpolicymatters.com\/wp-json\/wp\/v2\/categories?post=4577"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.healthlawpolicymatters.com\/wp-json\/wp\/v2\/tags?post=4577"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}