FDA Issues Draft Guidance Document for Postmarket Management of Cybersecurity in Medical Devices (Part 4 of 4)
The Proper Elements of an Effective Postmarketing Cybersecurity Program
The most practical portion of the FDA’s proposed guidelines is found in the Appendix. In this Section, the agency attempts to bring together all of the concepts from their recommendations into a cohesive summary of the necessary components of a proper cybersecurity program. The section discusses five broad concepts drawn from the NIST Framework: (1) Identify; (2) Protect; (3) Detect; (4) Respond and (5) Recover. All of these concepts are essential to a company’s cybersecurity program.
The first issue is how to properly identify threats. As a medical device manufacturer, this process is rooted in having a solid definition of “essential clinical performance.” As you will recall from Part One, “essential clinical performance” is the “performance that is necessary to achieve freedom from unacceptable clinical risk.” The manufacturer determines the potential severity outcomes if the device is compromised and also the risk acceptance criteria. This allows the manufacturer to properly “triage” potential vulnerabilities for remediation. The concept of essential clinical performance is the main criteria in determining whether or not particular cybersecurity vulnerability requires immediate mitigation or some lesser level of response. It is not enough that the manufacturer simply respond to cybersecurity threats in the field. Manufacturers need to actively engage in identifying cybersecurity signals and handle such vulnerability information in a way that reduces risk.
The second issue is protecting against potential and known threats. This requires a manufacturer to conduct a proper vulnerability characterization and assessment. When measuring the potential exploitability of a known vulnerability, the company should look at “remote exploitability, attack complexity, threat privileges, actions required by the user, exploit code maturity and report confidence.” Using a scorings system, such as CVSS (“Common Vulnerability Scoring System”) gives additional guidance as to how to quantify the risk and protect against the threat. This is used in risk analysis and threat modeling. “Threat modeling” is an important concept, in that it is a procedure that identifies vulnerabilities and then designs countermeasures to mitigate or eliminate the risk, prior to any actual threat taking place.
The third issue is detecting potential threats in the “real” world. Depending on the sophistication of the device, there may be very little internal ability to detect cybersecurity threats in real time. Networked devices are largely reliant (and dependent) on the security features of the parent network. Non-networked devices face different threats and are often even more vulnerable to threats that evade detection. Manufacturers are encouraged to incorporate design features that “establish or enhance” a device’s ability to detect and capture evidence of a cyberattack. In addition, the company should also have a procedure in place to assess the impact of a cyberattack across the entire device lineup.
The fourth issue is responding to threats. In order to reduce the risk to essential clinical performance, compensating controls must be implemented and provided to users to prevent harm. These remediations include everything from official and permanent fixes to temporary fixes and work-arounds. The company must respond appropriately to threats, while endeavoring to keep important medical devices functional and safe.
The final issue, which is the device manufacturer’s ability to recover following a cyberattack, is really an outgrowth of following the above guidelines. If the company has properly assessed the risk of a particular vulnerability, then the company should develop a response that is appropriate based on the risk to essential clinical performance. If the risk is mitigated, then the device continues to benefit the public, protected from cyberthreats.
In the end, the proposed FDA guidelines are fairly common sense adoptions of accepted cybersecurity principles. Most of the guidelines are industry-led, and the agency leaves manufacturers significant leeway in developing their own cybersecurity policies within the framework of known and accepted industry standards. We will continue to track changes to these recommendations as they are further revised by the agency, with input from both industry and citizen groups.
Read "Part 1 - Background and Overview of Essential Concepts" here; "Part 2 - Risk Assessment and Management in a Dangerous World" here; and "Part 3 -
related services

Cybersecurity Check-Up: Always A Good Time To Prepare to Protect ...

All Claims Means ALL: The PREP Act Provides Immunity in COVID-19 Vaccination Case ...
About Drug / Device Law Blog
Baker Sterchi's Drug / Device Law Blog examines topics and legal developments of interest to the drug and device industry. Learn more about the editor, Paul Penticuff, and our Drug and Device practice.
Subscribe via email
Subscribe to rss feeds
RSS FeedsABOUT baker sterchi blogs
Baker Sterchi Cowden & Rice LLC (Baker Sterchi) publishes this website as a service to our clients, colleagues and others, for informational purposes only. These materials are not intended to create an attorney-client relationship, and are not a substitute for sound legal advice. You should not base any action or lack of action on any information included in our website, without first seeking appropriate legal or other professional advice. If you contact us through our website or via email, no attorney-client relationship is created, and no confidential information should be transmitted. Communication with Baker Sterchi by e-mail or other transmissions over the Internet may not be secure, and you should not send confidential electronic messages that are not adequately encrypted.
The hiring of an attorney is an important decision, which should not be based solely on information appearing on our website. To the extent our website has provided links to other Internet resources, those links are not under our control, and we are not responsible for their content. We do our best to provide you current, accurate information; however, we cannot guarantee that this information is the most current, correct or complete. In addition, you should not take this information as a promise or indication of future results.
Disclaimer
The Drug / Device Law Blog is made available by Baker Sterchi Cowden & Rice LLC for educational purposes only as well as to give you general information and a general understanding of the law, not to provide specific legal advice. Your use of this blog site alone creates no attorney client relationship between you and the firm.
Confidential information
Do not include confidential information in comments or other feedback or messages related to the Drug / Device Law Blog, as these are neither confidential nor secure methods of communicating with attorneys. The Drug / Device Law Blog should not be used as a substitute for competent legal advice from a licensed professional attorney in your state.