FDA Recommends that Manufacturers Seeking Medical Device Approval Submit Cyber Security Plans

by Baker Donelson
Contact

Last week, the FDA took steps to address a quietly growing concern regarding cyber security and medical devices. Specifically, the agency issued Draft Guidance requiring the submission of cyber security materials as part of any premarket submissions [PDF] and a Safety Communication explaining in more plain terms the scope of the cyber security issues addressed and the FDA’s recommended actions. While the Draft Guidance may only apply to manufacturers who intend to submit premarket materials for approval, the Safety Communication is also targeted to, and should be reviewed by, hospitals that rely on medical devices and information networks threatened by malicious software (malware).

The Safety Communication

The latest Safety Communication echoes concerns that the FDA first enunciated in a November 2009 Communication. In essence, the new Communication expands on the previous Communication, and provides more specific guidance to users, purchasers, providers and manufacturers of medical devices. The guidance notes that the FDA has "recently" become aware of security risks to medical devices (and therefore to hospital operations). Specifically:

  • Network connected or configured medical devices being affected by malware;
  • The presence of malware on mobile electronics (including smartphones and tablets) used to access patient information, monitoring systems, and implanted devices;
  • “Uncontrolled” distribution of passwords (including “hard-coded” passwords);
  • Failure to provide timely security and similar software and firmware updates (and address security issues in older devices); and
  • Security vulnerabilities in off-the-shelf software solutions designed to prevent unauthorized device or network access.

Although not specifically discussed in the Communication, the Communication was released on the same day as a Wall Street Journal article publicizing a series of infections at VA hospitals (subscription may be required), some of which were serious enough to impact hospital operations and even disable equipment. That article also noted at least one event in which the Office of Civil Rights was asked to investigate a GE radiology device at Beth Israel Deaconess Medical Center that had become infected and was apparently transferring patient information to a server outside of the hospital. (The server was never located.) It seems likely that the FDA’s actions are meant to combat what appears to be a growing problem of cyber security and connected (or simply connectable) medical devices.

The Communication speaks to both manufacturers and health care facilities. For manufacturers (in addition to the Draft Guidance, discussed below) the Communication encourages the adoption of steps that will limit unauthorized device access (particularly for life-sustaining devices), protect medical devices and their components (including upgrading and patching existing security as necessary), provide designs that preserve core functions even during an attack and provide methods to recover and restore compromised devices. For facilities, the Communication recommends:

  • Restricting unauthorized access to facility networks and networked devices;
  • Ensuring that all security software is up to date;
  • Monitoring network activity (for suspicious movement, such as a radiology device communicating with an outside server seemingly on its own initiative);
  • Regularly reviewing security, updating as necessary, and disconnecting devices that do not require connections;
  • Reaching out to manufacturers, the FDA, or DHS ICS-CERT where a vulnerability or problem is found; and
  • Developing strategies to preserve critical functions during adverse conditions.

The Draft Guidance

The FDA’s Draft Guidance applies to Premarket Notification (510(k)) including Traditional, Special, and Abbreviated 510(k) submissions; De novo petitions; Premarket Approval Applications (PMA); Product Development Protocols (PDP); and Humanitarian Device Exemption (HDE) submissions relating to medical devices that contain software, firmware, or programmable logic. In short, the guidance intends to ensure that medical devices will maintain information confidentiality, integrity and availability – even when infected with malware. To achieve these goals, the Draft Guidance recommends that manufacturers “consider cybersecurity during the design phase of the medical device, as this can result in more robust and efficient mitigation of cybersecurity risks.” Specifically, manufacturers, as part of the risk analysis required in a pre-market submission, should define and document:

  • An identification of assets, threats and vulnerabilities;
  • An impact assessment of the threats and vulnerabilities on device functionality;
  • An assessment of the likelihood of a threat and of a vulnerability being exploited;
  • A determination of risk levels and suitable mitigation strategies; and
  • A residual risk assessment and risk acceptance criteria.

The Draft Guidance goes on to address the security capabilities it expects to be described in premarket submissions and the documentation it recommends be used to evidence the existence of necessary security considerations.

Security Capabilities

The Draft Guidance acknowledges that the identification of appropriate security measures will be heavily dependent on context – how and where the device will be used, what features it offers, how it is accessed or maintained, etc. The Draft Guidance also notes an understanding that security features could compromise usability (especially, for instance, in an emergency) and that careful consideration of an appropriate balance is necessary. With these caveats in mind, however, the Draft Guidance recommends that premarket submissions include justification for the use (or exclusion) of certain security features, including (but not limited to):

  • Requiring device access authentication (such as passwords, smart cards, or biometric identifiers);
  • Automated timed log-offs;
  • Providing support for layered authorizations (providing different users different levels of access);
  • Requiring multi-factor authentication for privileged users (such as technicians who may alter software or firmware configurations);
  • Avoiding “hard-coded” passwords (passwords that are the same for each device and difficult to change);
  • Providing physical locks on both the device itself and its communication ports;
  • Requiring user access authentication prior to permitting updates or other software modification;
  • Restricting software modification to authenticated code, issued by the manufacturer and confirmed using that manufacturer’s authentication system;
  • Provide procedures for authorized users to download version-identifiable software and firmware from the manufacturer;
  • Provide for secure data transfer to and from the device, using encryption technology as appropriate;
  • Provide for “fail-safe” device features that protect the device’s critical functionality, even when the device’s security has been compromised;
  • Provide features that allow for the recognition of an security breach (such as an infiltration of malware or other unwelcome code), logging, and corrective action;
  • Provide methods of data and device recovery by an authenticated administrative user.

Documentation

In a premarket submission, the Draft Guidance recommends that manufacturers provide the following:

  • An analysis of hazards posed, mitigations, and design consideration related to cyber security risks associated with the device (including “specific” listings of all risks that were considered during device design and all cyber security controls (and their justifications) established for the device);
  • A “traceability matrix” linking security controls established with those that were considered;
  • The systematic plan for providing validated software and firmware updates and patches;
  • “Appropriate” documentation that the device will be provided to purchasers free of malware; and
  • Device instructions and product specifications regarding recommended security environment steps (such as anti-virus software, firewall configuration and the like).

As always, the FDA’s guidance is not legally binding – these steps are recommended, but not required. The guidance, however, provides clear insight into the agency’s thoughts on appropriate manufacturer responses to cyber security threats and should not be ignored.

Ober|Kaler's Comments

That our increased dependence on networked, connected, and connectible devices requires increased vigilance comes as no surprise, but, many providers may be surprised to learn of the vulnerably of even “off-the-grid” devices. It is essential for enterprise security to remember that viruses and other malware (such as the now infamous STUXNET code) do not require an internet or intranet connection to spread – a single infected USB storage device, used to install updates, for instance, or to transfer or back-up patient data can easily become a digital Typhoid Mary, wreaking havoc throughout an organization without actually showing any signs of infection itself. The new FDA Draft Guidance raises the issue, but, especially for hospitals and other providers, an analysis of the risks presented by malware infection (and the potential for such infections to seriously compromise the confidentiality of protected health information), is already likely required under the HIPAA Privacy and Security Rules. Both manufacturers and end users, including providers, should review their policies and procedures to ensure that they properly account for the risks identified by the FDA.

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.

© Baker Donelson | Attorney Advertising

Written by:

Baker Donelson
Contact
more
less

Baker Donelson 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.
Privacy Policy (Updated: October 8, 2015):
hide

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.

Security

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 info@jdsupra.com. 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: info@jdsupra.com.

- 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.