Securing Wireless Infusion Pumps

In Healthcare Delivery Organizations

Volume B:

Approach, Architecture, and Security Characteristics


Gavin O’Brien

National Cybersecurity Center of Excellence

Information Technology Laboratory

Sallie Edwards

Kevin Littlefield

Neil McNab

Sue Wang

Kangmin Zheng

The MITRE Corporation

McLean, VA

May 2017



Certain commercial entities, equipment, products, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST or NCCoE, nor is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose.

National Institute of Standards and Technology Special Publication 1800-8B Natl. Inst. Stand. Technol. Spec. Publ. 1800-8B, 90 pages, (May 2017), CODEN: NSPUE2


You can improve this guide by contributing feedback. As you review and adopt this solution for your own organization, we ask you and your colleagues to share your experience and advice with us.

Comments on this publication may be submitted to:

Public comment period: May 8, 2017 through July 7, 2017

All comments are subject to release under the Freedom of Information Act (FOIA).

National Cybersecurity Center of Excellence
National Institute of Standards and Technology
100 Bureau Drive
Mailstop 2002
Gaithersburg, MD 20899


The National Cybersecurity Center of Excellence (NCCoE), a part of the National Institute of Standards and Technology (NIST), is a collaborative hub where industry organizations, government agencies, and academic institutions work together to address businesses’ most pressing cybersecurity issues. This public-private partnership enables the creation of practical cybersecurity solutions for specific industries or broad, cross-sector technology challenges. Working with technology partners—from Fortune 50 market leaders to smaller companies specializing in IT security—the NCCoE applies standards and best practices to develop modular, easily adaptable example cybersecurity solutions using commercially available technology. The NCCoE documents these example solutions in the NIST Special Publication 1800 series, which maps capabilities to the NIST Cyber Security Framework and details the steps needed for another entity to recreate the example solution. The NCCoE was established in 2012 by NIST in partnership with the State of Maryland and Montgomery County, Md.

To learn more about the NCCoE, visit To learn more about NIST, visit


NIST Cybersecurity Practice Guides (Special Publication Series 1800) target specific cybersecurity challenges in the public and private sectors. They are practical, user-friendly guides that facilitate the adoption of standards-based approaches to cybersecurity. They show members of the information security community how to implement example solutions that help them align more easily with relevant standards and best practices and provide users with the materials lists, configuration files, and other information they need to implement a similar approach.

The documents in this series describe example implementations of cybersecurity practices that businesses and other organizations may voluntarily adopt. These documents do not describe regulations or mandatory practices, nor do they carry statutory authority.


Medical devices, such as infusion pumps, were once standalone instruments that interacted only with the patient or medical provider. But today’s medical devices connect to a variety of health care systems, networks, and other tools within a healthcare delivery organization (HDO). Connecting devices to point-of-care medication systems and electronic health records can improve healthcare delivery processes, however, increasing connectivity capabilities also creates cybersecurity risks. Potential threats include unauthorized access to patient health information, changes to prescribed drug doses, and interference with a pump’s function.

The NCCoE at NIST analyzed risk factors in and around the infusion pump ecosystem using a questionnaire-based risk assessment to develop an example implementation that demonstrates how HDOs can use standards-based, commercially available cybersecurity technologies to better protect the infusion pump ecosystem, including patient information and drug library dosing limits.

This practice guide will help HDOs implement current cybersecurity standards and best practices to reduce their cybersecurity risk, while maintaining the performance and usability of wireless infusion pumps.


authentication; authorization; digital certificates; encryption; infusion pumps; Internet of Things; IoT; medical devices; network zoning; pump servers; questionnaire-based risk assessment; segmentation; VPN; Wi-Fi; wireless medical devices


We are grateful to the following individuals for their generous contributions of expertise and time.

Name Organization
Arnab Ray Baxter Healthcare Corporation
Pavel Slavin Baxter Healthcare Corporation
Phillip Fisk Baxter Healthcare Corporation
Raymond Kan Baxter Healthcare Corporation
Tom Kowalczyk B. Braun Medical Inc.
David Suarez Becton, Dickinson and Company (BD)
Robert Canfield Becton, Dickinson and Company (BD)
Rob Suarez Becton, Dickinson and Company (BD)
Robert Skelton Becton, Dickinson and Company (BD)
Rich Curtiss Clearwater Compliance
Peter Romness Cisco
Kevin McFadden Cisco
Darin Andrew DigiCert
Kris Singh DigiCert
Mike Nelson DigiCert
Chaitanya Srinivasamurthy Hospira Inc., a Pfizer Company (ICU Medical)
Joseph Sener Hospira Inc., a Pfizer Company (ICU Medical)
Chris Edwards Intercede
Won Jun Intercede
Dale Nordenberg MDISS
Jay Stevens MDISS
Carlos Aguayo Gonzalez PFP Cybersecurity
Thurston Brooks PFP Cybersecurity
Colin Bowers Ramparts
Bill Hagestad Smiths Medical
Axel Wirth Symantec Corporation
Bryan Jacobs Symantec Corporation
Bill Johnson TDi Technologies, Inc.
Barbara De Pompa Reimers The MITRE Corporation
Sarah Kinling The MITRE Corporation
Marilyn Kupetz The MITRE Corporation
David Weitzel The MITRE Corporation
Mary Yang The MITRE Corporation

The technology vendors who participated in this build submitted their capabilities in response to a notice in the Federal Register. Companies with relevant products were invited to sign a Cooperative Research and Development Agreement (CRADA) with NIST, allowing them to participate in a consortium to build this example solution. We worked with:

Technology Partner/Collaborator Build Involvement
Baxter Healthcare Corporation
  • Sigma Spectrum LVP, version 8
  • Sigma Spectrum Wireless Battery Module, version 8
  • Sigma Spectrum Master Drug Library, version 8
  • CareEverywhere Gateway Server, version 14
B. Braun Medical Inc.
  • Infusomat® Space Infusion System/ Large Volume Pumps
  • DoseTrac® Infusion Management Software/ Infusion Pump Software
Becton, Dickinson and Company (BD)
  • Alaris® 8015 PC Unit v9.19.2
  • Alaris® Syringe Module 8110
  • Alaris® LVP Module 8100
  • Alaris® Systems Manager v4.2
  • Alaris® System Maintenance (ASM) v 10.19
  • Access Point (AIR-CAP1602I-A-K9)
  • Wireless LAN Controller
  • Cisco ISE
  • Cisco: ASA
  • Catalyst 3650 Switch
Clearwater Compliance Clearwater: IRM | Pro
DigiCert CertCentral management account / Certificate Authority
Hospira Inc., a Pfizer Company (ICU Medical)
  • Plum 360™ Infusion System, version 15.10
  • LifeCare PCA™ Infusion System, version 7.02
  • Hospira MedNet™, version 6.2
Intercede MyID
PFP Cybersecurity Device Monitor
Ramparts Risk Assessment
Smiths Medical
  • Medfusion® 3500 V5 syringe infusion system
  • PharmGuard® Toolbox v1.5
  • Medfusion 4000® Wireless Syringe Infusion Pump
  • CD, PHARMGUARD® TOOLBOX 2, V3.0 use with Medfusion® 4000 and 3500 V6 (US)
  • PharmGuard® Server Licenses, PharmGuard® Server Enterprise Edition, V1.1
  • CADD®-Solis Ambulatory Infusion Pump
  • CADD™-Solis Medication Safety Software
Symantec Corporation
  • Endpoint Protection (SEP)
  • Advanced Threat Protection: Network (ATP:N)
  • Server Advanced - DataCenter Security (DCS:SA):
TDi Technologies, Inc. ConsoleWorks

List of Figures

Figure 4‑1: Tiered Risk Management Approach (NIST SP 800-37)

Figure 4‑2: Relationship between Security and Safety Risks (AAMI TIR 57)

Figure 5‑1: Basic System

Figure 5‑2: Network Architecture with Segmentation

Figure 5‑3: Wi-Fi Management

Figure 5‑4: Wi-Fi Authentication

Figure 5‑5: Wi-Fi Device Access

Figure 5‑6: Network Access Control

Figure 5‑7: Remote Access VPN

Figure 5‑8: Remote Access

Figure 5‑9: External

Figure 5‑10: Pump Server Protection

Figure 5‑11: Target Architecture

Figure 6‑1: Asset Life Cycle

List of Tables

Table 4‑1: Security Characteristics and Controls Mapping - NIST Cyber Security Framework

Table 4‑2: Products and Technologies

1. Summary

Medical devices, such as infusion pumps, were once standalone instruments that interacted only with the patient or medical provider [1]. With technological improvements designed to enhance patient care, these devices now connect wirelessly to a variety of systems, networks, and other tools within a healthcare delivery organization (HDO) – ultimately contributing to the Internet of Medical Things (IoMT).

In addition to managing interconnected medical devices, HDOs oversee complex, highly technical environments, from back-office applications for billing and insurance services, supply chain and inventory management, and staff scheduling to clinical systems such as radiological and pharmaceutical support. In this intricate healthcare environment, HDOs and medical device manufacturers that share responsibility and take a collaborative, holistic approach to reducing cybersecurity risks of the wireless infusion pump ecosystem can better protect healthcare systems, patients, PHI, and enterprise information.

The National Cybersecurity Center of Excellence (NCCoE) at the National Institute of Standards and Technology (NIST) developed an example implementation that demonstrates how HDOs can use standards-based, commercially available cybersecurity technologies to better protect the wireless infusion pump ecosystem, including patient information and drug library dosing limits.

The NCCoE’s project has resulted in a NIST Cybersecurity Practice Guide, Securing Wireless Infusion Pumps, that addresses how to manage this challenge in clinical settings with a reference design and example implementation. Our example solution starts with two types of risk assessments: an industry analysis of risk and a questionnaire-based-risk assessment. With the results of that assessment, we then used a defense-in-depth strategy to secure the pump, server components, and surrounding network to create a better protected environment for wireless infusion pumps.

The solution and architectures presented here are built upon standards-based, commercially available products and represent one of many possible solutions and architectures. The example implementation can be used by any organization that is deploying wireless infusion pump systems and is willing to perform their own risk assessment and implement controls based on their risk posture.

For ease of use, here is a short description of the different sections of this volume.

Section 1: Summary presents the challenge addressed by the NCCoE project, with an in-depth look at our approach, the architecture, and the security characteristics we used; the solution demonstrated to address the challenge; benefits of the solution; and the technology partners that participated in building, demonstrating, and documenting the solution. The Summary also explains how to provide feedback on this guide.

Section 2: How to Use This Guide explains how readers like you—business decision makers, program managers, information technology (IT) professionals (e.g., systems administrators), and biomedical engineers—might use each volume of the guide.

Section 3: Approach offers a detailed treatment of the scope of the project, describes the assumptions on which the security platform development was based, the risk assessment that informed platform development, and the technologies and components that industry collaborators gave us to enable platform development.

Section 4: Risk Assessment and Mitigation highlights the risks we found, along with the potential response and mitigation efforts that can help lower risks for HDOs.

Section 5: Architecture describes the usage scenarios supported by project security platforms, including Cybersecurity Framework functions supported by each component contributed by our collaborators.

Section 6: Life Cycle Cybersecurity Issues discusses cybersecurity considerations from a product life cycle perspective including: procurement, maintenance, end of life.

Section 7: Security Characteristics Analysis provides details about the tools and techniques we used to perform risk assessments pertaining to wireless infusion pumps.

Section 8: Functional Evaluation summarizes the test sequences we employed to demonstrate security platform services, the Cybersecurity Framework functions to which each test sequence is relevant, and the NIST SP 800-53-4 controls that applied to the functions being demonstrated.

Section 9: Future Build Considerations is a brief treatment of other applications that NIST might explore in the future to further support wireless infusion pump cybersecurity.

Appendices provide acronym translations, references, a mapping of the wireless infusion pump project to the Cybersecurity Framework Core (CFC), and a list of additional informative security references cited in the CFC.

1.1. Challenge

The Food and Drug Administration (FDA) defines an external infusion pump as a medical device that delivers fluids into a patient’s body in a controlled manner, using interconnected servers or via a standalone drug library-based medication delivery system [1]. In the past, infusion pumps were standalone instruments that interacted only with the patient and the medical provider. Now, connecting infusion pumps to point-of-care medication systems and electronic health records (EHRs) can help improve healthcare delivery processes, but using a medical device’s connectivity capabilities can also create cybersecurity risk, which could lead to operational or safety risks.

Wireless infusion pumps are challenging to protect for several reasons. They can be infected by malware, which can cause them to malfunction or operate differently than originally intended. And traditional malware protection could negatively impact the pump’s ability to operate efficiently. In addition, most wireless infusion pumps contain a maintenance default passcode. If HDOs do not change the default passcodes when provisioning pumps, nor periodically change the passwords after pumps are deployed, this creates a vulnerability. This can make it difficult to revoke access codes when a hospital employee resigns from the job, for example. Furthermore, information stored inside infusion pumps also must be properly secured, including data from drug library systems, infusion rates and dosages, or protected health information (PHI) [2], [3], [4], [5], [6].

Additionally, like other devices with operating systems and software that connect to a network, the wireless infusion pump ecosystem creates a large attack surface (i.e., the different points where an attacker could get into a system, and where they could exfiltrate data out), primarily due to vulnerabilities in operating systems, subsystems, networks or default configuration settings that allow for possible unauthorized access [6], [7], [8]. Because many infusion pump models can be accessed and programmed remotely through a healthcare facility’s wireless network, this vulnerability could be exploited to allow an unauthorized user to interfere with the pump’s function, harming a patient through incorrect drug dosing or the compromise of that patient’s PHI.

These risk factors are real, exposing the wireless pump ecosystem to external attacks, compromise or interference [6], [8], [9]. Digital tampering, intentional or otherwise, with a wireless infusion pump’s ecosystem (the pump, the network, and data in and on the pump) can expose a healthcare delivery organization (HDO) to critical risk factors, such as malicious actors; loss of data; a breach of PHI; loss of services; loss of health records; the potential for downtime; and damage to an HDO’s reputation, productivity, and bottom-line revenue.

This practice guide helps you address your assets, threats, and vulnerabilities by demonstrating how to perform a questionnaire-based risk assessment survey. After you complete the assessment, you can apply security controls to the infusion pumps in your area of responsibility to create a defense-in-depth solution to protect them from cybersecurity risks.

1.2. Solution

The NIST Cybersecurity Practice Guide Securing Wireless Infusion Pumps shows how biomedical engineers, networking engineers, security engineers and IT professionals, using commercially available, open source tools and technologies that are consistent with cybersecurity standards, can help securely configure and deploy wireless infusion pumps within HDOs.

In addition, the security characteristics of wireless infusion pump ecosystem are mapped to currently available cybersecurity standards and the Health Insurance Portability and Accountability Act (HIPAA) Security Rule. In developing our solution, we used standards and guidance from:

  • NIST Framework for Improving Critical Infrastructure Cybersecurity (commonly known as the NIST CSF) [10]
  • NIST Risk Management Framework (RMF) [11], [12], [13]
  • NIST SP 800-53rev4 Security and Privacy Controls for Federal Information Systems and Organizations [14]
  • Association for the Advancement of Medical Instrumentation (AAMI) Technical Information Report (TIR) 57 [9]
  • International Electrotechnical Commission (IEC) 80001 and 80002 risk management for IT networks incorporating medical devices [15], [16], [17], [18], [19]
  • Food and Drug Administration’s (FDA) Postmarket Management of Cybersecurity in Medical Devices for building block standards for any medical device cybersecurity solution.

Ultimately, this practice guide:

  • maps security characteristics to standards and best practices from NIST and other standards organizations, to the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Security Rule [10], [14], [20], [21], [22]
  • provides a detailed architecture and capabilities that address security controls
  • provides a how-to for implementers and security engineers to recreate the reference design
  • is modular and uses products that are readily available and interoperable with existing IT infrastructure and investments.

Your organization may choose to adopt this example solution, or one that adheres to these guidelines, or you may refer to this guide as a starting point for tailoring and implementing specific parts that best suit your organization’s needs. Although the NCCoE used a suite of commercially available tools and technologies to address wireless infusion pump cybersecurity challenges, this guide does not endorse any specific products, nor does it guarantee compliance with any regulatory initiatives. Refer to your organization’s information security experts to identify solutions that will best integrate with your organization’s current tools and IT system infrastructure.

1.3. Benefits

The example solution presented in this practice guide offers several benefits, including:

  • illustrating cybersecurity standards and best practice guidelines to better secure the wireless infusion pump ecosystem, such as the hardening of operating systems, segmenting the network, white listing, code-signing, and using certificates for both authorization and encryption, maintaining the performance and usability of wireless infusion pumps
  • reducing risks from the compromise of information, including the potential for breach or loss of protected health information (PHI), as well as not allowing these medical devices to be used for anything other than the intended purposes
  • documenting a defense-in-depth strategy to introduce layers of cybersecurity controls that avoid a single point of failure and provide strong support for availability. This strategy may include a variety of tactics: using network segmentation to isolate business units and user access; applying firewalls to manage and control network traffic; hardening and enabling device security features to reduce zero-day exploits; and implementing strong network authentication protocols and proper network encryption, monitoring, auditing and intrusion detection and prevention services (IDS/IPS).
  • highlighting best practices for procurement of wireless infusion pumps by including the need for cybersecurity features at the point of purchase
  • calling upon industry to create new best practices for healthcare providers to consider when on-boarding medical devices, with a focus on elements such as asset inventory, certificate management, device hardening and configuration, and a clean-room environment to limit the possibility of zero-day vulnerabilities.

2. How to Use This Guide

This NIST Cybersecurity Practice Guide demonstrates a standards-based reference design and provides users with the information they need to replicate NCCoE’s questionnaire-based risk assessment and deployment of a defense in depth strategy. This reference design is modular and can be deployed in whole or in parts.

This guide contains three volumes:

  • NIST SP 1800-8A: Executive Summary
  • NIST SP 1800-8B: Approach, Architecture, and Security Characteristics – what we built and why (you are here)
  • NIST SP 1800-8C: How-To Guides – instructions for building the example solution.

Depending on your role in your organization, you might use this guide in different ways:

  • Business decision makers, including chief security and technology officers will be interested in the Executive Summary (NIST SP 1800-8A), which describes the:

    • challenges enterprises face in securing the wireless infusion pump ecosystem
    • example solution built at the NCCoE
    • benefits of adopting the example solution.
  • Technology or security program managers concerned with how to identify, understand, assess, and mitigate risk will be interested in this part of the guide, NIST SP 1800-8B, which describes what we did and why. The following sections will be of particular interest:

You might share the Executive Summary, NIST SP 1800-8A, with your leadership team to help them understand the significant risk of unsecured IoMT and the importance of adopting standards-based, commercially available technologies that can help secure the wireless infusion pump ecosystem.

IT professionals who want to implement an approach like this will find the whole practice guide useful. You can use the How-To portion of the guide, NIST SP 1800-8C, to replicate all or parts of the example implementation that we built in our lab. The How-To guide provides specific product installation, configuration, and integration instructions for implementing the example solution. We do not recreate the product manufacturers’ documentation, which is generally widely available. Rather, we show how we incorporated the products together in our environment to create an example solution.

This guide assumes that IT professionals have experience implementing security products within the enterprise. While we have used a suite of commercial products to address this challenge, this guide does not endorse any products. Your organization can adopt this solution or one that adheres to these guidelines in part or in whole. Your organization’s security experts should identify the products that will best integrate with your existing tools and IT system infrastructure. We hope you will seek products that are congruent with applicable standards and best practices. Section 4.4, Technologies lists the products we used and maps them to the cybersecurity controls provided by this reference solution.

A NIST Cybersecurity Practice Guide does not describe the solution, but rather a possible solution. This is a draft guide. We seek feedback on its contents and welcome your input. Comments, suggestions, and success stories will improve subsequent versions. Please contribute your thoughts by sending them to

2.1. Typographical Conventions

The following table presents typographic conventions used in this volume.

Typeface/Symbol Meaning Example

filenames and pathnames

references to documents that are not hyperlinks, new terms, and placeholders

For detailed definitions of terms, see the NCCoE Glossary.
Bold names of menus, options, command buttons and fields Choose File > Edit.
command-line input, on-screen computer output, sample code examples, status codes
Monospace Bold
command-line user input contrasted with computer output
service sshd start
blue text link to other parts of the document, a web URL, or an email address All publications from NIST’s National Cybersecurity Center of Excellence are available at

3. Approach

Medical devices have grown increasingly powerful, offering patients improved, safer healthcare options with less physical effort for providers. To accomplish this, medical devices now contain operating systems and communication hardware that allow them to connect to networks and other devices. The connected functionality responsible for much of the improvement of medical devices poses challenges not formerly seen with standalone instruments.

Clinicians and patients rely on infusion pumps for safe and accurate administration of fluids and medications. However, the FDA has identified problems that can compromise the safe use of external infusion pumps [2], [3], [7]. These issues can lead to over- or under-infusion, missed treatments, or delayed therapy. The NCCoE initiated this project to help healthcare providers develop a more secure wireless infusion pump ecosystem, which can be applied to similarly connected medical devices. The wireless infusion pump was selected as a representative medical device. Throughout the remainder of this guide, the focus will be on the secure operation of the wireless infusion pump ecosystem. Both the architecture and security controls may be applied to increase the security posture for other types of medical devices. However, any application should be reviewed and tailored to the specific environment in which the medical device will operate.

Throughout the wireless infusion pump project, we collaborated with our Healthcare Community of Interest (COI) and cybersecurity vendors to identify infusion pump threat actors, define interactions between the actors and systems, review risk factors, develop an architecture and reference design, identify applicable mitigating security technologies, and design an example implementation. This practice guide highlights the approach used to develop the NCCoE reference solution. Elements include risk assessment and analysis, logical design, build development, test and evaluation and security control mapping. The practice guide seeks to help the healthcare community evaluate the security environment surrounding infusion pumps deployed in a clinical setting.

3.1. Audience

This guide is primarily intended for professionals implementing security solutions within an HDO. It may also be of interest to anyone responsible for securing non-traditional computing devices (i.e., the Internet of Things, or IoT).

More specifically, Volume B of the practice guide is designed to appeal to a wide range of job functions. This volume offers cybersecurity or technology decision makers within HDOs a view into how they can make the medical device environment more secure to help improve their enterprise’s security posture and reduce enterprise risk. It offers technical staff guidance on architecting a more secure medical device network and instituting compensating controls.

3.2. Scope

The NCCoE project focused on securing the environment of the medical device and not re-engineering the device itself. To do this, we reviewed known vulnerabilities in wireless infusion pumps and examined how the architecture and component integration could be designed to increase the security of the device. The approach considered the life cycle of a wireless infusion pump from planning the purchase, to decommissioning, with a concentration on the configuration, use, and maintenance phases.

3.2.1. Assumptions

Considerable research, investigation, and collaboration went into the development of the reference design in this guide. The actual build and example implementation of this architecture occurred in a lab environment at the NCCoE. Although the lab is based on a clinical environment, it does not mirror the complexity of an actual hospital network. It is assumed that any actual clinical environment would represent additional complexity.

3.2.2. Security

We assume that those of you who plan to adopt this solution or any of its components have some degree of network security already in place. As a result, we focused primarily on new vulnerabilities that may be introduced if organizations implement the example solution. Section 4, Risk Assessment and Mitigation, contains detailed recommendations on how to secure the core components highlighted in this practice guide.

3.2.3. Existing Infrastructure

This guide may help you design an entirely new infrastructure. However, it is geared toward those with an established infrastructure, as that represents the largest portion of readers. Hospitals and clinics are likely to have some combination of the capabilities described in this reference solution. Before applying any measures addressed in this guide, we recommend that you review and test them for applicability to your existing environment. No two hospitals or clinics are the same, and the impact of applying security controls will differ.

3.2.4. Technical Implementation

The guide is written from a how-to perspective. Its foremost purpose is to provide details on how to install, configure, and integrate components, and how to construct correlated alerts based on the capabilities we selected.

3.2.5. Capability Variation

We fully understand that the capabilities presented here are not the only security options available to the healthcare industry. Desired security capabilities may vary considerably from one provider to the next.

4. Risk Assessment and Mitigation

NIST SP 800-30, Risk Management Guide for Information Technology Systems, states, “Risk is the net negative impact of the exercise of a vulnerability, considering both the probability and the impact of occurrence. Risk management is the process of identifying risk, assessing risk, and taking steps to reduce risk to an acceptable level” [11].

We recommend that any discussion of risk management, particularly at the enterprise level, begin with a comprehensive review of NIST SP 800-37, A Guide for Applying the Risk Management Framework to Federal Information Systems [12].NIST’s Risk Management Framework (RMF) guidance has provided invaluable advice in providing a baseline to assess risks, from which the NCCoE developed the project, the security characteristics of the solution, and this guide.

It is important to understand what constitutes the definition of risk as it relates to non-traditional information systems such as wireless infusion pumps. NIST SP 800-37 presents three tiers in the risk management hierarchy (Figure 4-1):

  1. Organization
  2. Business Processes
  3. Information Systems

Figure 4-1: Tiered Risk Management Approach (NIST SP 800-37)


This guide focuses on the Tier 3 application of risk management but incorporates other industry risk management and assessment standards and best practices for the context of networked medical devices in HDOs. Relevant standards and best practices include:

  • International Electrotechnical Commission (IEC) 80001-1 (2010): Application of risk management for IT-networks incorporating medical devices—Part 1: Roles, responsibilities, and activities [23]
  • International Electrotechnical Commission/ Technical Report (IEC/TR) 80001-2: Application of risk management for IT networks incorporating medical devices [16], [17], [18], [19]
  • International Standards Organization (ISO) 14971:2007 Medical devices—Application of risk management to medical devices [24]
  • Association for the Advancement of Medical Instrumentation (AAMI) Technical Information Report (TIR) 57: 2016 Principles for medical device security—risk management [9]
  • Food and Drug Administration (FDA) Postmarket Management of Cybersecurity in Medical Devices [3].

For this NCCoE project, it was extremely important to understand the complexity of networked medical devices in a system-of-systems environment. Additionally, we felt it necessary to understand where security risks may have safety implications. The AAMI TIR57 was particularly useful in this regard, as it specified elements of medical device security using NIST’s RMF, IEC 80001-1, IEC/TR 80001-2 and ISO 14971 [9], [11], [12], [13], [15], [16], [17], [18], [19], [23], [24]. Also, the Venn diagram in Figure 4-2 illustrates the relationship between security and safety risks (AAMI TIR57). As seen in this diagram, there are cybersecurity risks that may have safety impacts. For HDOs, these risks should receive special attention from both security and safety personnel.

Figure 4-2: Relationship between Security and Safety Risks (AAMI TIR 57) [7]


4.1. Risk Assessments

For this NCCoE project, we performed two types of risk assessments: (1) industry analysis of risk and (2) questionnaire-based risk assessment.

4.1.1. Industry Analysis of Risk

The first assessment was an industry analysis of risk performed while developing the initial use case. This industry analysis provided insight into the challenges of integrating medical devices into a clinical environment containing a standard IT network. Completion of the industry analysis narrowed the objective of our use case to helping HDOs secure medical devices on an enterprise network, with a specific focus on wireless infusion pumps.

Activities involved in our industry analysis included reaching out to our COI and other industry experts through workshops and focus group discussions. After receiving feedback on the NCCoE’s use case publication through a period of public comment, NCCoE adjudicated the comments and clarified a project description. These activities were instrumental to identifying primary risk factors as well as educating our team on the uniqueness of cybersecurity risks involved in protecting medical devices in healthcare environments.

4.1.2. Questionnaire-based Risk Assessment

For the second type of risk assessment, we conducted a formal questionnaire-based risk assessment, using tools from two NCCoE Cooperative Research and Development Agreement (CRADA) collaborators. We conducted this questionnaire-based risk assessment to gain greater understanding of the risks surrounding the wireless infusion pump ecosystem. The tool identifies the risks and maps them to the security controls. This type of risk assessment is considered appropriate for Tier 3: Information Systems, per NIST’s RMF. One tool focuses on medical devices and the surrounding ecosystem. The other tool focuses on the HDO enterprise. Both questionnaire-based risk assessment tools leverage guidance and best practices including the NIST RMF and CSF and focus on built-in threats, vulnerabilities, and controls [10], [11], [12], [13]. The assessment results measure likelihood, severity, and impact of potential threats.

All risk assessment activities provide an understanding of the challenges and risks involved when integrating medical devices, in this case wireless infusion pumps, into a typical IT network. Based on this analysis, this project has two fundamental objectives for this project:

  • to protect the wireless infusion pumps from cyberattacks;
  • to protect the healthcare ecosystem, should a wireless infusion pump be compromised.

Per AAMI’s TIR57, “To assess security risk, several factors need to be identified and documented,” [9].

Based on our risk assessments and additional research, we identified primary threats, vulnerabilities, and risks that should be addressed when using wireless infusion pumps in HDOs.

4.1.3. Assets

Defining the asset is the first step in establishing the asset-threat-vulnerability construct necessary to properly evaluate or measure risks, per NIST’s RMF [11], [12], [13]. An information asset is typically defined as a software application or information system that uses devices or third-party vendors for support and maintenance. For the NCCoE’s purposes, the information asset selected is a Wireless Infusion Pump System. A risk assessment of this asset would include an evaluation of the cybersecurity controls for the pump, pump server, end-point connections, network controls, data storage, remote access, vendor support, inventory control, and any other associated elements.

4.1.4. Threats

Below are some potential known threats in HDOs that use network-connected medical devices, such as wireless infusion pumps. Refer to Appendix A for a description of each threat.

  • Targeted attacks
  • Advanced Persistent Threats (APTs)
  • Disruption of Service – Denial of Service (DoS) and Distributed Denial of Service (DDoS) attacks
  • Malware infections
  • Theft or loss of assets
  • Unintentional misuse
  • Vulnerable systems or devices directly connected to the device (e.g., via USB or other hardwired, non-network connections).

It is important to understand that the threat landscape is constantly evolving and unknown threats exist and may be unavoidable, which need to be identified and remediated as they are found.

4.1.5. Vulnerabilities

Vulnerabilities afflict wireless infusion pump devices, pump management applications, network applications and even the physical environment and personnel using the device or associated systems. Within a complex system-of-systems environment, vulnerabilities may be exploited at all levels. There are multiple information resources available to keep you informed about potential vulnerabilities. This guide recommends that security professionals turn to the National Vulnerability Database (NVD). The NVD is the U.S. government repository of standards-based vulnerability management data [].

Here is a list of typical vulnerabilities that may arise when using wireless infusion pumps. Refer to Appendix B for a description of each vulnerability.

  • Lack of asset inventory

  • Long useful life

  • Information/Data Vulnerabilities

    • Lack of encryption on private/sensitive data-at-rest
    • Lack of encryption on transmitted data
    • Unauthorized changes to device calibration or configuration data
    • Insufficient data backup
    • Lack of capability to de-identify private/sensitive data
    • Lack of data validation
  • Device/Endpoint (Infusion Pump) Vulnerabilities

    • Debug-enabled interfaces
    • Use of removable media
    • Lack of physical tamper detection and response
    • Misconfiguration
    • Poorly protected and patched devices
  • User or Administrator Accounts Vulnerabilities

    • Hard-coded or factory default passcodes
    • Lack of role-based access and/or use of principles of least privilege
    • Dormant accounts
    • Weak remote access controls
  • IT Network Infrastructure Vulnerabilities

    • Lack of malware protection
    • Lack of system hardening
    • Insecure network configuration
    • System complexity.

To mitigate risk factors, HDOs should also strive to work closely with medical device manufacturers and follow FDA’s post-market guidance, as well as instructions from the U.S. Department of Homeland Security’s Industrial Control System-Cyber Emergency Response Team (ICS-CERT).

4.1.6. Risks

NIST SP 800-30, A Guide for Conducting Risk Assessments, defines risk as, “a measure of the extent to which an entity is threatened by potential circumstance or event, and is typically a function of: (i) the adverse impacts that would arise if the circumstance or event occurs; and (ii) the likelihood of occurrence” [11]

NIST SP 800-30 further notes within a definition of risk assessment that, “assessing risk requires careful analysis of threat and vulnerability information to determine the extent to which circumstances or events could adversely impact an organization and the likelihood that such circumstances or events will occur.”

Based on the above guidance from NIST SP 800-30, several risks endanger medical devices:

  • Infusion pumps and server components may be leveraged for APTs and serve as pivot points to cause adverse conditions throughout a hospital’s infrastructure.
  • Infusion pumps may be manipulated to prevent the effective implementation of safety measures, such as the drug library.
  • Infusion pump interfaces may be used for unintended or unexpected purposes, with those conditions leading to degraded performance of the pump.
  • PHI may be accessed remotely by unauthorized individuals.
  • PHI may be disclosed to unauthorized individuals should the device be lost, stolen, or improperly decommissioned.
  • Improper third party vendor connections.

Although these risks may persist in infusion pumps and server components, HDOs should perform appropriate due diligence in determining the extent of the business impact and likelihood of each risk factor.

Vulnerabilities may be present in infusion pumps and their server components since these devices often include embedded operating systems on the endpoints. Infusion pumps are designed to maintain a prolonged period of useful life, and, as such, may include system components (e.g., an embedded operating system) that may either reach end-of-life or reach a period of degraded updates prior to the infusion pump being retired from service. Patching and updating may become difficult over the course of time.

Infusion pumps may not allow for the addition of third-party mechanisms, such as antivirus or anti-malware controls. Should limitations be identified in embedded operating systems used by an infusion pump, vulnerabilities, weaknesses, and deficiencies may become known to malicious actors who may seek to leverage those deficiencies to install malicious or unauthorized software on those devices.

Malicious software, or malware, may cause adverse conditions on the pump, degrading the performance of the pump, or rendering the device unable to perform its function (e.g., ransomware). Malware may also be used to convert the infusion pump into an access point for malicious actors to subsequently access or disrupt the operations of other hospital systems.

As noted above, infusion pumps may allow for the manipulation of configurations or safety measures implemented through the drug library (e.g., adjusting dosage or flow rates). This risk may be instantiated through local access, such as an interface or port on the device with either no or weak authentication or access control in place. Further, infusion pumps may be reachable across a hospital’s network, which provides an avenue for a malicious actor to cause an adverse event.

Pumps may implement local ports, such as USB ports serial interfaces, Bluetooth, radio frequency, or other mechanisms that allow for close proximity connection to the pump. These ports may be implemented with the intent to facilitate technical support; however, they also pose a risk by providing a pathway for actors to cause adverse conditions to the pump.

Modern infusion pumps and server components may include PHI, such as a patient’s name, medical record number (MRN), procedure coding, and medication or treatment. Through similar deficiencies that would allow configuration or use manipulation as noted above, this PHI may then be viewed, accessed, or removed by unauthorized individuals. Also, individuals who have direct access to the infusion pump may be able to extract information through unsecured ports or interfaces [2], [3], [7], [17], [25].

Common vulnerabilities and control deficiencies that enable these risks may include:

  • The implementation of default credentials and passwords: Weak authentication, and default passwords, or not implementing authentication or access control, may be discovered by malicious actors who would seek to cause adverse conditions. Malicious actors may leverage this control deficiency for risk factors that span from installing malware on the infusion pump, to manipulating configuration settings, or to extract information such as PHI from the device.
  • The use of unsecured network ports, such as Telnet or FTP: Telnet and FTP are internet protocols that do not secure or encrypt network sessions. Telnet and FTP may be used nominally for technical support interfaces; however, malicious actors may attempt to leverage these to access the infusion pump. Telnet and FTP may include deficiencies that allow for compromise of the protocol itself, and, since the network session is not encrypted, malicious actors may implement mechanisms to capture network sessions, including any authentication traffic, or to identify sensitive information such as credentials, configuration information, or any PHI stored on the device.
  • Local interfaces with limited security controls: Local interfaces, such as USB ports, serial ports, Bluetooth, radio frequency, or other ports may be used for device technical support. These ports, however, allow for malicious actors within close proximity to the device to access the device, manipulate configuration settings, access or remove data from the device, or install malware on the device. These ports may exist on the pump for support purposes, but use of the ports for unauthorized or unexpected purposes, such as recharging a mobile device such as a smart phone or tablet, may cause a disruption to the pump’s standard operation.

4.1.7. Recommendations and Best Practices

The recommendations in Appendix C address additional security concerns which, although not as pressing as those listed above, are worthy of consideration. If applied, these additional recommendations will likely reduce risk factors or prevent them from becoming greater risks. Associated best practices for reducing the overall risk posture of infusion pumps are also included in Recommendations and Best Practices list.

4.2. Risk Response Strategy

Risk mitigation is often confused with risk response. Per NIST SP 800-30, risk mitigation is defined as “prioritizing, evaluating, and implementing the appropriate risk-reducing controls/countermeasures recommended from the risk management process.”

Risk mitigation is a subset of risk response. Risk response is defined by NIST SP 800-30 as: accepting; avoiding; mitigating; sharing, or transferring risks. When considering risk response, your organization should recommend to a corporate risk management board ways that the Information Risk Manager or equivalent should treat risk.

4.2.1. Risk Mitigation

Organizations must determine their tolerance or appetite for risk, the response to which will drive risk remediation or risk mitigation for identified risks. This tolerance should be codified in a Risk Management Plan. Such a plan will include regulatory requirements and guidance, industry best practices, and security controls. Organizations should set an appropriate risk tolerance based on the factors noted above with the intent to remediate those risks above the established risk tolerance (i.e., critical or high risks.)

These remediation responses can take the form of administrative, physical, and technical controls, or an appropriate mix. Section 4.1.7 of this guide identifies several mitigation recommendations regarding specific risk. Additional compensating safeguards, countermeasures, or controls are noted below:

  • Physical security controls, including standard tamper-evident physical seals, which can be applied to hardware to indicate unauthorized physical access [10], [26].
  • Ensuring implementation of a physical asset management program that manages and tracks unique, mobile media such as removable flash memory devices (e.g., SD cards, thumb drives) used by pump software hosted on an endpoint client. Consider encryption of all portable media used in such a fashion [10], [26], [27], [28].
  • Following procedures for clearing wireless network authentication credentials on the endpoint client if the pump is to be removed or transported from the facility. These procedures can be found in pump user manuals but should be referenced in official HDO policies and procedures [29], [30], [31], [32].
  • Changing wireless network authentication credentials regularly and, if there is evidence of unauthorized access to a pump system, immediately changing network authentication credentials [10], [26].
  • Ensuring all wireless network access is minimally configured for WPA2 PSK encryption and authentication. All pumps should be set to WPA2 encryption [33], [34], [35], [36].
  • All pumps and pump systems should include cryptographic modules that have been validated as meeting NIST FIPS 140-2 [37].
  • All ports are disabled except when in use, and the device has no listening ports [3], [9], [10], [25], [26].
  • Employing mutual transport layer security (TLS) encryption in transit between the client and server [38].
  • Employing individual pump authentication with no shared key for all pumps [10], [26].
  • Certificate-based authentication for a pump server [29], [30], [31], [32].

4.3. Security Characteristics and Controls Mapping

As described in the previous sections, we derived the security characteristics by analyzing risk in collaboration with our healthcare sector stakeholders as well as our participating vendor partners. In the risk analysis process, we used IEC/TR 80001-2-2 as our basis for wireless infusion pump capabilities in healthcare environments [16]. Table 4‑1 presents the desired security characteristics of the use case in terms of the CSF subcategories [10], [14]. Each subcategory is mapped to relevant NIST standards, industry standards, controls, and best practices. In our example implementation, we did not observe any security characteristics that mapped to the Respond or Recover subcategories of the CSF.

Table 4-1: Security Characteristics and Controls Mapping - NIST CyberSecurity Framework

Cybersecurity Framework (CSF) v1.1 Sector-Specific Standards & Best Practices
Function Category Subcategory SP800-53R4 IEC TR 80001-2-2 HIPAA Security Rule 45 [39] ISO/IEC 27001:2013
IDENTIFY (ID) Asset Management (ID.AM) ID.AM-1: Physical devices and systems within the organization are inventoried CM-8 CNFS C.F.R. §§ 164.308(a)(1)(ii)(A), 164.310(a)(2)(ii), 164.310(d) A.8.1.1, A.8.1.2
    ID.AM-5: Resources (e.g., hardware, devices, data, time, and software) are prioritized based on their classification, criticality, and business value CP-2, RA-2, SA-14 DTBK C.F.R. § 164.308(a)(7)(ii)(E) A.8.2.1
  Business Environment (ID.BE) ID.BE-4: Dependencies and critical functions for delivery of critical services are established CP-8, PE-9, PE-11, PM-8, SA-14 DTBK C.F.R. §§ 164.308(a)(7)(i), 164.308(a)(7)(ii)(E), 164.310(a)(2)(i), 164.312(a)(2)(ii), 164.314(a)(1), 164.314(b)(2)(i) A.11.2.2, A.11.2.3, A.12.1.3
  Risk Assessment (ID.RA) ID.RA-1: Asset vulnerabilities are identified and documented CA-2, CA-7, CA-8, RA-3, RA-5, SA-5, SA-11, SI-2, SI-4, SI-5 RDMP C.F.R. §§ 164.308(a)(1)(ii)(A), 164.308(a)(7)(ii)(E), 164.308(a)(8), 164.310(a)(1), 164.312(a)(1), 164.316(b)(2)(iii) A.12.6.1, A.18.2.3
PROTECT (PR) Identity Management and Access Control (PR.AC) (note: not directly mapped in CSF) AC-1, AC-11, AC-12 ALOF    
    PR.AC-1: Identities and credentials are issued, managed, revoked, and audited for authorized devices, users, and processes AC-2, IA Family AUTH, CNFS, EMRG, PAUT C.F.R. §§ 164.308(a)(3)(ii)(B), 164.308(a)(3)(ii)(C), 164.308(a)(4)(i), 164.308(a)(4)(ii)(B), 164.308(a)(4)(ii)(C ), 164.312(a)(2)(i), 164.312(a)(2)(ii), 164.312(a)(2)(iii), 164.312(d) A.9.2.1, A.9.2.2, A.9.2.4, A.9.3.1, A.9.4.2, A.9.4.3
    PR.AC-2: Physical access to assets is managed and protected PE-2, PE-3, PE-4, PE-5, PE-6, PE-9 PLOK, TXCF, TXIG C.F.R. §§ 164.308(a)(1)(ii)(B), 164.308(a)(7)(i), 164.308(a)(7)(ii)(A), 164.310(a)(1), 164.310(a)(2)(i), 164.310(a)(2)(ii), 164.310(a)(2)(iii), 164.310(b), 164.310(c), 164.310(d)(1), 164.310(d)(2)(iii) A.11.1.1, A.11.1.2, A.11.1.4, A.11.1.6, A.11.2.3
    PR.AC-3: Remote access is managed AC‑17, AC-19, AC-20 NAUT, PAUT C.F.R. §§ 164.308(a)(4)(i), 164.308(b)(1), 164.308(b)(3), 164.310(b), 164.312(e)(1), 164.312(e)(2)(ii) A.6.2.2, A.13.1.1, A.13.2.1
    PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties AC-2, AC-3, AC-5, AC-6, AC-16 AUTH, CNFS, EMRG, NAUT, PAUT C.F.R. §§ 164.308(a)(3), 164.308(a)(4), 164.310(a)(2)(iii), 164.310(b), 164.312(a)(1), 164.312(a)(2)(i), 164.312(a)(2)(ii) A.6.1.2, A.9.1.2, A.9.2.3, A.9.4.1, A.9.4.4
    PR.AC-5: Network integrity is protected, incorporating network segregation where appropriate AC-4, SC-7 NAUT C.F.R. §§ 164.308(a)(4)(ii)(B), 164.310(a)(1), 164.310(b), 164.312(a)(1), 164.312(b), 164.312(c), 164.312€ A.13.1.1, A.13.1.3, A.13.2.1
  Data Security (PR.DS) PR.DS-1: Data-at-rest is protected SC-28 IGAU, STCF C.F.R. §§ 164.308(a)(1)(ii)(D), 164.308(b)(1), 164.310(d), 164.312(a)(1), 164.312(a)(2)(iii), 164.312(a)(2)(iv), 164.312(b), 164.312(c), 164.314(b)(2)(i), 164.312(d) A.8.2.3
    PR.DS-2: Data-in-transit is protected SC-8 IGAU, TXCF C.F.R. §§ 164.308(b)(1), 164.308(b)(2), 164.312(e)(1), 164.312(e)(2)(i), 164.312(e)(2)(ii), 164.314(b)(2)(i) A.8.2.3, A.13.1.1, A.13.2.1, A.13.2.3, A.14.1.2, A.14.1.3
    PR.DS-4: Adequate capacity to ensure availability is maintained AU-4, CP-2, SC-5 AUDT, DTBK C.F.R. §§ 164.308(a)(1)(ii)(A), 164.308(a)(1)(ii)(B), 164.308(a)(7), 164.310(a)(2)(i), 164.310(d)(2)(iv), 164.312(a)(2)(ii) A.12.3.1
    PR.DS-6: Integrity checking mechanisms are used to verify software, firmware, and information integrity SI-7 IGAU C.F.R. §§ 164.308(a)(1)(ii)(D), 164.312(b), 164.312(c)(1), 164.312(c)(2), 164.312(e)(2)(i) A.12.2.1, A.12.5.1, A.14.1.2, A.14.1.3
  Information Protection Processes and Procedures (PR.IP) PR.IP-1: A baseline configuration of information technology/industrial control systems is created and maintained incorporating appropriate security principles (e.g. concept of least functionality) CM-2, CM-3, CM-4, CM-5, CM-6, CM-7, CM-9, SA-10 CNFS, CSUP, SAHD, RDMP C.F.R. §§ 164.308(a)(8), 164.308(a)(7)(i), 164.308(a)(7)(ii) A.12.1.2, A.12.5.1, A.12.6.2, A.14.2.2, A.14.2.3, A.14.2.4
    PR.IP-4: Backups of information are conducted, maintained, and tested periodically CP-4, CP-6, CP-9 DTBK C.F.R. §§ 164.308(a)(7)(ii)(A), 164.308(a)(7)(ii)(B), 164.308(a)(7)(ii)(D), 164.310(a)(2)(i), 164.310(d)(2)(iv) A.12.3.1, A.17.1.2, A.17.1.3, A.18.1.3
    PR.IP-6: Data is destroyed according to policy MP-6 DIDT C.F.R. §§ 164.310(d)(2)(i), 164.310(d)(2)(ii) A.8.2.3, A.8.3.1, A.8.3.2, A.11.2.7
    PR.MA-2: Remote maintenance of organizational assets is approved, logged, and performed in a manner that prevents unauthorized access MA-4 CSUP C.F.R. §§ 164.308(a)(3)(ii)(A), 164.310(d)(1), 164.310(d)(2)(ii), 164.310(d)(2)(iii), 164.312(a), 164.312(a)(2)(ii), 164.312(a)(2)(iv), 164.312(b), 164.312(d), 164.312(e), 164.308(a)(1)(ii)(D) A.11.2.4, A.15.1.1, A.15.2.1
DETECT (DE) Anomalies and Events (DE.AE) DE.AE-1: A baseline of network operations and expected data flows for users and systems is established and managed AC-4, CA-3, CM-2, SI-4 AUTH, CNFS C.F.R. §§ 164.308(a)(1)(ii)(D), 164.312(b) none
  Security Continuous Monitoring (DE.CM) DE.CM-1: The network is monitored to detect potential cybersecurity events AC-2, AU-12, CA-7, CM-3, SC-5, SC-7, SI-4 AUTH, CNFS, EMRG, MLDP C.F.R. §§ 164.308(a)(1)(ii)(D), 164.308(a)(5)(ii)(B), 164.308(a)(5)(ii)(C), 164.308(a)(8), 164.312(b), 164.312(e)(2)(i) none
    DE.CM-3: Personnel activity is monitored to detect potential cybersecurity events AC-2, AU-12, AU-13, CA-7, CM-10, CM-11 AUTH, CNFS, EMRG, MLDP C.F.R. §§ 164.308(a)(1)(ii)(D), 164.308(a)(3)(ii)(A), 164.308(a)(5)(ii)(C), 164.312(a)(2)(i), 164.312(b), 164.312(d), 164.312€ A.12.4.1
    DE.CM-4: Malicious code is detected SI-3 IGAU, MLDP, TXIG C.F.R. §§ 164.308(a)(1)(ii)(D), 164.308(a)(5)(ii)(B) A.12.2.1
    DE.CM-6: External service provider activity is monitored to detect potential cybersecurity events CA-7, PS-7, SA-4, SA-9, SI-4 RDMP C.F.R. § 164.308(a)(1)(ii)(D) A.14.2.7, A.15.2.1
  Detection Processes (DE.DP) DE.DP-3: Detection processes are tested CA-2, CA-7, PE-3, PM-14, SI-3, SI-4 IGAU C.F.R. § 164.306€ A.14.2.8
RESPOND (RS)            
RECOVER (RC)            

4.4. Technologies

Table 4‑2 lists all of the technologies used in this project and map the generic application term to the specific product we used and the security control(s) we deployed. Refer to Table 4‑1 for an explanation of the CSF Subcategory codes [10].

The reference architecture design in Section 5 is vendor agnostic such that any Wireless Infusion Pump (WIP) system can be integrated safely and securely into a hospital’s IT infrastructure. Therefore, for the infusion pump device, infusion pump server and wireless infusion pump ecosystem, we captured the most common security features among all the products we tested in this use case. A normalized view of the list of functions and NIST CSF Subcategories are presented in the table below.

Please note, some of the CSF Subcategory codes require people, and process controls, not solely technical controls.

Table 4-2: Products and Technologies

Component Specific Product Function CSF Subcategories
Infusion Pump Device Baxter: Sigma Spectrum LVP, Version 8
  • requires passcode to access the bio-medical engineering mode (on device or connect to device) for configuring and setting up the devices
  • provides the capability to change the manufacture default passcode
  • supports IEEE 802.11i enterprise wireless encryption/authentication standards, including WPA2-EAP-TLS for protecting data exchange
  • restricted access to the server, application and stored data
  • closes/disables all communication ports that are not required for the intended use
  • closes/disables all services that are not required for intended use
  • provides an integrity checking mechanism to verify information
  • supports baseline configuration
  • supports removing/destroying data from the device
  • few models have a tamper-resist switch, with tamper-evident seals
PR.AC-1, PR.AC-2, PR.DS-2, PR.DS-6, PR.IP-1, PR.IP-6
  Baxter: Sigma Spectrum Wireless Battery Module, version 8    
  BBraun: Space Infusomat Infusion Pump (LVP) – s/w U    
  BD: Alaris® 8015 PC Unit v9.19.2    
  BD: Alaris® Syringe Module 8110    
  BD: Alaris® LVP Module 8100    
  Hospira: Plum 360 version15.10    
  Hospira: PCA version 7.02    
  Smiths Medical: Medfusion® 3500 V5 syringe infusion system    
  Smiths Medical: Medfusion 4000® Wireless Syringe Infusion Pump    
  Smiths Medical: CADD®-Solis Ambulatory Infusion Pump    
Infusion Pump Server Baxter: CareEverywhere Gateway Server, version 14
  • with appropriate configuration, discovers and identifies devices connected to the pump server via wired, wireless, and virtual private networks, to aid in building and maintaining accurate physical device inventories
  • supports role-based authentication and password rules and policies
  • supports the use of a HDO’s Active Directory/LDAP solution
  • supports auto-logoff, data encryption/obscuration
  • can be accessed remotely via VPN (or like) tools
  • a few models support FIPS 140-2
  • operates on manufacturer-supported OS, DB Server and Web Server (allows software patches)
  • supports secure protocols, such as TLS
  • supports co-existence with firewall, anti-virus, backup software, and other types of security safeguard products
  • maintains different types of audit/log records for preventing
  • unauthorized access
ID.AM-1, PR.AC-1, PR.AC-3, PR.AC-4, PR.DS-1, PR.DS-2, PR.MA-2
  BBraun: Space Online Suite Software, version AP 2.0.1    
  BD: Alaris® Systems Manager v4.2    
  Hospira: MedNet 6.2    
  Smiths Medical: PharmGuard® Server Enterprise Edition, V1.1    
Infusion Pump Ecosystem Baxter: Sigma Spectrum Master Drug Library, version 8    
  BBraun: Space DoseTrace and Space DoseLink software – Eng version available for testing    
  BD: Alaris® System Maintenance (ASM) v 10.19    
  Smiths Medical: PharmGuard® Toolbox v1.5    
  Smiths Medical: CADD™-Solis Medication Safety Software    
Access Point (AP) Cisco: Access Point (AIR-CAP1602I-A-K9
  • authenticates and connects infusion pumps to the Wi-Fi
  • supports Wireless Network Standards: IEEE 802.11a/b/g/n/ac
  • supports Security Protocols: IEEE 802.11i (WPA2), EAP-TLS
  • AP joins a WLC to form a Control and Provisioning of Wireless Access Points protocol (CAPWAP) tunnel
  • uses ISE as the authentication service
  • provides message authentication and encryption in data transmission
PR.AC-5, PR.DS-1, PR.DS-2, DE.CM-1, DE.CM-3
Wireless LAN Controller (WLC) Cisco: Wireless LAN Controller
Identity Services Engine (ISE) Cisco ISE
  • discovers and identifies devices connected to wired, wireless, and virtual private networks. It gathers this information based on what’s accurate connecting to the network, a key step toward building and maintaining accurate physical device inventories
  • provides advanced network access controls by connecting user identity with device profiling and access policy
  • provides log audit of events which can be monitored for the network traffic
ID.AM-1, PR.AC-1, PR.AC-4, PR.DS-1, PR.DS-2, DE.CM-1, DE.CM-3
Firewall/Router Cisco: ASA
  • delivers network integrity protection
  • used as external firewall for connecting to the internet for guest network
  • used as internal firewall for all other network zones with rules and policies
PR.AC-5, PR.DS-1, PR.DS-2, DE.CM-1, DE.CM-3


Catalyst 3650 Switch

  • provides port-level controls, port blocking, VLAN segmentation
PR.AC-5, PR.DS-1, PR.DS-2, DE.CM-1, DE.CM-3
Endpoint Protection Symantec: Endpoint Protection (SEP)
  • provides intrusion prevention, URL, and firewall policies
  • provides application behavioral controls
  • provides device control to restrict access
  • provides anti-virus file protection
  • Provides behavioral monitoring
  • Provides file reputation analysis
DE.CM-1, DE.CM-3, DE.CM-4, PR.DS-1, PR.DS-2, DE.AE-1
Network Advanced Threat Protection Symantec: Advanced Threat Protection: Network (ATP:N)
  • monitors internal inbound and outbound internet traffic
  • uncovers advanced attacks
  • automatically prioritizes critical events
  • searches for known indicators-of-compromise (IoC) across the entire environment
  • blacklists or whitelists files and URLs once they are identified as malicious
  • can be integrated with third-party security information and events management (SIEM) tool
DE.CM-1, DE.CM-4, PR.DS-1, PR.DS-2, DE.AE-1
DataCenter Security Symantec: Server Advanced - DataCenter Security (DCS:SA):
  • out-of-the-box host intrusion detection system (IDS) and intrusion prevention systems (IPS) policies
  • provides sandboxing and Process Access Control (PAC) to prevent a new class of threats
  • hosts firewall to control inbound and outbound network traffic to and from servers
  • compensating host intrusion prevention system (HIPS) controls restrict application and operating system behavior using policy-based least privilege access control
  • prevents file and system tampering
  • provides application and device control by locking down ‘configuration’ settings, file systems, and use of removable media
DE.CM-1, DE.CM-4, PR.DS-1, PR.DS-2, DE.AE-1
Secure Remote Management and Monitoring TDi Technologies: ConsoleWorks
  • authenticates system managers
  • provides role-based access control of system management functions
  • implements a protocol break between the system manager and the managed assets
  • records all system management actions
  • performs remote configuration management and monitoring of devices
PR.AC-3, PR.AC-4, PR.MA-2, PR.PT-1, PR.PT-3, DE.CM-1, DE.CM-3, DE.CM-4, DE.CM-6
Physics-based integrity assessment PFP: Device Monitor
  • detects device behavior
  • detects cyberattacks in hardware and software
  • detects tiny anomalies in power patterns to instantly catch attacks, thereby providing an early warning that a device has been tampered with
  • integrity assessment uses side channel
Certificate Authority Service DigiCert: Certificate Authority
  • provides certificate authority service

Access Control (PR.AC)


Certificate Management / Provisioning Intercede:MyID
  • serves as device provisioner
Risk Assessment Clearwater: IRM | Pro
  • provides tool for conducting risk assessments that focus on healthcare compliance and cyber risk management
  • provides tool for conducting risk assessments that focus on medical devices

5. Architecture

Wireless infusion pumps are no longer standalone devices. They now include pump servers for managing the pumps, drug libraries, networks allowing for interoperability with other hospital systems, and VPN tunnels to outside organizations for maintenance. While interconnectivity, enhanced communications, and safety measures on the pump have added complexity to infusion pumps, these components can help improve patient outcomes and safety.

As infusion pumps have evolved, one safety mechanism development was the invention of the “drug library.” The drug library is a mechanism that is applied to an infusion pump that catalogs medications, fluids, dosage, and flow rates. While hospital pharmacists may be involved in the maintenance of the drug library, continuous application of the drug library to the infusion pump environment tends to be managed through a team of biomedical engineers. Initially, the drug library file may be loaded onto the pump through a communication port. When the drug library file is updated, all infusion pumps need to be updated to ensure that they adhere to the current rendition of that drug library. Drug library distribution, which may require that staff manually adjust individual pumps, may become onerous for the biomedical staff in HDOs that use thousands of pumps [1], [40].

Manufacturers provide wireless communications on some pumps and use a pump server to manage the drug library file, capture usage information on the pumps, and provide pump updates.

Medical devices manufacturers are subject to regulatory practices by the Food & Drug Administration (FDA), and may tend to focus on the primary function of the pump (i.e., assurance that the pump delivers fluids of a certain volume and defined flow rates, consistent with needs that providers may have to ensure safe and appropriate patient care). Technology considerations, such as cybersecurity controls, may not be primarily addressed in the device design and approval process. As such, infusion pumps may include technology that does not lend itself to the same controls that an HDO may implement on standard desktops, laptops, or workstations used for productivity [9], [18].

As technology has evolved, cybersecurity risk has expanded, both in visibility and in the number of threats and vulnerabilities. This expansion has led to a heightened concern, from manufacturers, as well as the FDA, and work has been established to identify measures to better respond to cybersecurity risk [7], [9], [25]. In Section 5.1, we describe the wireless infusion pump ecosystem by defining the components. Section 5.2 discusses the data flow, and Section 5.3 explains the set of controls we use in our example implementation, including those for networks, pumps, pump servers, and enterprise. Section 5.4 describes the target architecture for our example implementation.

5.1. Basic System

A basic wireless infusion pump ecosystem includes a wireless infusion pump, a pump server, a network consisting of an access point, a wireless LAN controller, a firewall, and a VPN to a manufacturer.

Figure 5-1: Basic System


5.2. Data Flow

The flow of data between a wireless infusion pump and its corresponding server falls into the following transaction categories:

  • modifying the drug library
  • performing software updates
  • remotely managing the devices
  • auditing the data flow processes.

Infusion pumps may also include other advanced features such as auto-programming to receive patient prescription information and record patient treatment information to the patient’s electronic health record.

5.3. Cybersecurity Controls

This section discusses security controls by their location, either on the network, pump, or pump server. We also describe controls implemented in the NCCoE lab, and depict the controls implemented in our final architecture.

In general, we recommend that a clinically focused network be designed to protect information used in HDOs, whether that information is at-rest or in-transit. As described in Cisco Medical-Grade Network (MGN) 2.0-Wireless Architectures, no single architecture can be designed to meet the security requirements of all organizations [41]. However, many cybersecurity best practices can be applied by HDOs to meet regulatory compliance standards.

Our reference architecture uses Cisco’s solution architecture as the baseline. This baseline demonstrates how the network can be used to provide multi-tiered protection for medical devices when exchanging information via a network connection. The goal of our reference architecture is to provide countermeasures to deal with challenges identified in the assessment process. For our use case solution, we use segmentation and defense-in-depth as security models to build and maintain a secure device infrastructure. This section provides additional details on how to employ security strategies to achieve specific targeted protections when securing wireless infusion pumps.

We used the following cybersecurity controls:

  • network controls
  • pump controls
  • pump server controls
  • enterprise level controls

5.3.1. Network Controls

Proper network segmentation or network zoning is essential to developing a strong cybersecurity posture [33], [34], [35], [36], [42]. Segmentation uses network devices such as switches and firewalls to split a large computer network into subnetworks, each referred to as a network segment [41]. Network segmentation not only enhances network management, but also improves cybersecurity, allowing the separation of networks based on network security requirements driven by business needs or asset value.

The architecture designed for this build uses Cisco’s solution architecture as the baseline for demonstrating how the network can be used to provide a multi-tiered protection for medical devices when exchanging information with the outside world during the operation involving network communication. The goal of this architecture design is to provide countermeasures to mitigate challenge areas identified in the assessment process. In our use case solution, segmentation and defense-in-depth are the security models we used as security measures to build and maintain secure device infrastructure. This section provides additional details on how to employ security strategies to achieve the target security characteristics for securing wireless infusion pumps. Segmentation/Zoning

Our network architecture uses a zone-based security approach. By using different local networks for designated purposes, networked equipment identified for a specific purpose can be put together on the same network segment and protected with an internal firewall. The implication is that there is no inherent trust between network zones and that trust limitations are enforced by properly configuring firewalls to protect equipment in one zone from other, less trusted zones. By limiting access from other, less trusted areas, firewalls can more effectively protect the enterprise network.

For discussion purposes, we include some generic components of a typical HDO in our network architecture examples. A given healthcare facility may be simpler or more complex and may contain different subcomponents. The generic architecture contains several functional segments, including the following elements:

  • core network
  • guest network
  • business office
  • database server
  • enterprise services
  • clinical server
  • biomedical engineering
  • medical devices with wireless LAN
  • remote access for external vendor support

At a high level, each zone is implemented as a virtual local area network (VLAN) with a combination firewall/router Cisco Adaptive Security Appliance (ASA) device connecting it to the rest of the enterprise through a backbone network, referred to as the core network [43], [44], [45]. Segments may consist of physical or virtual networks. We implemented sub-nets that correspond exactly to VLANs for simplicity and convenience. The routing configuration is the same for each, but the firewall configuration may vary depending on each zone’s specific purpose. An external router/firewall device is used to connect the enterprise and guest network to the internet. Segmentation is implemented via a VLAN using Cisco switches. A short description of each segment and the final network architecture follow. Core Network

Our reference architecture implements a core network zone that consists of the equipment and systems used to establish the backbone network infrastructure. The external firewall/router also has an interface connected to the core enterprise network, just like other firewall/router devices in the other zones. This zone serves as the backbone of the enterprise network and consists only of routers connected by switches. The routers automatically share internal route information with each other via authenticated Open Shortest Path First (OSPF) to mitigate configuration errors as zones are added or removed. Guest Network Zone

Hospitals often implement a guest network that allows visitors or patients to access internet services during their visit. As shown in Figure 5‑2:, network traffic here tends not to be clinical in nature but is offered as a courtesy to hospital visitors and patients to access the internet. Refer to Section, External Access for additional technical details. Business Office Zone

A business office zone is established for systems dedicated to hospital office productivity and does not include direct patient-facing systems. This zone consists of traditional clients on an enterprise network, such as workstations, laptops, and possibly mobile devices. Within the enterprise, the business office zone will primarily interact with the enterprise services zone. This zone may also include Wi-Fi access. Database Server Zone

A database server zone is established to house server components that support data persistence. The database server zone may include data stores that aggregate potentially sensitive information, and, given the volume, require safeguards. Databases may include PHI, so HIPAA privacy and security controls are applicable. This zone consists of servers with databases. Ideally, applications in the enterprise services zone and biomedical engineering zone use these databases instead of storing information on application servers. This type of centralization allows for simplified management of security controls to protect the information stored in databases. Enterprise Services Zone

The enterprise services zone consists of systems that support hospital staff productivity. Enterprise services may not be directly patient specific systems, but rather support core office functions found in a hospital. This zone consists of traditional enterprise services, such as DNS, Active Directory, Identity Service System, and asset inventory that probably lives in a server room or data center. These services must be accessible from various other zones in the enterprise. Clinical Services Zone

The clinical services zone consists of systems that pertain to providing patient care. Examples of systems that would be hosted in this zone include the electronic health record (EHR) system, pharmacy systems, health information systems, and other clinical systems to support patient care. Biomedical Engineering Zone

The biomedical engineering zone establishes a separate area that enables a biomedical engineering team to manage and maintain systems such as medical devices as shown in Figure 5‑2:. This zone consists of all equipment needed to provision and maintain medical devices. In the case of wireless infusion pumps, this is where the pump management servers are hosted on the network. Medical Device Zone

The medical device zone provides a network space where medical devices may be hosted. Infusion pumps would be deployed in this zone. Infusion pump systems are designed so that all external connections to EHR systems or vendor maintenance operations can be completed through an associated pump server that resides in the biomedical engineering network zone. Access to the rest of the network and internet is blocked. This zone contains a dedicated wireless network to support the wireless infusion pumps, as explained in Section, Medical Device Zone’s Wireless LAN. Remote Access Zone

The remote access zone provides a network segment that extends external privileged access so that vendors may access their manufactured components and systems on the broader HDO network. Refer to Section, Remote Access for additional technical details. Final Network Architecture

Figure 5-2 shows the interconnection of all components and zones previously described. It also illustrates the connection to vendor and cloud services via the internet. VLAN numbers shown are VLAN identifiers used in the lab, but may vary on actual healthcare enterprise networks.

Figure 5-2: Network Architecture with Segmentation

../_images/fig5-2.png Medical Device Zone’s Wireless LAN

The Wi-Fi management network is different in that it does not have a firewall/router that connects directly to the core network as shown in Figure 5‑3:. This is a completely closed network used for the management and communication between the Cisco Aironet wireless Access Point (AP) and the Cisco Wireless LAN Controller (WLC). The WLC is the central point where wireless Service Set Identifiers (SSIDs), Virtual LANs (VLANs), and Wi-Fi Protected Access version 2 (WPA2) security settings are managed for the entire enterprise [8], [17], [33], [34], [35], [36], [42], [46], [47], [48], [49].

Two SSIDs were defined, IP_Dev and IP_Dev Cert. IP_Dev uses WPA2-PSK, and IP_Dev Cert uses WPA2-Enterprise protocols. In an actual HDO, two WLCs should be configured for redundancy. Initially, the wireless access points configure themselves for network connectivity like any other device using Dynamic Host Configuration Protocol (DHCP) from the switch DHCP server (see the green line in Figure 5‑3:). The switch also sends DHCP option 43, which provides the IP address of the WLC. The AP then connects to the WLC to automatically download firmware updates and wireless configuration information. Finally, the Control and Provisioning of Wireless Access Points (CAPWAP) tunnel and encrypt wireless traffic (see the black line in Figure 5‑3:). The traffic is then routed to the enterprise network via the WLC [28], [37], [44], [50].

Figure 5-3: Wi-Fi Management


When a device first connects to the Wi-Fi network, it needs to authenticate with either the agreed-upon pre-shared key or certificate. The authentication process is tunneled from the AP back to the WLC as shown in Figure 5-4. In the case of a pre-shared key, the WLC verifies that the client key matches (see green line). In the case of a certificate, the authentication process is passed from the WLC to the Cisco identity service engine (ISE) for validation using remote authentication dial-in user service (RADIUS) protocol (yellow line). Upon successful authentication, the device negotiates an encryption key and is granted link layer network access.

Figure 5-4: Wi-Fi Authentication


Once authentication is complete, typical network client activity is allowed. Figure 5-5 shows how Dynamic Host Configuration Protocol (DHCP) is used to contact the router to obtain network configuration information for the device (see red line). Once the network is configured, the infusion pump will attempt to connect to its provisioned pump server address on the enterprise network in the biomedical zone (see green line).

Figure 5-5: Wi-Fi Device Access


Using an enterprise-grade Wi-Fi system can simplify transitions to more secure protocols by decoupling Wi-Fi SSIDs and security parameters from the Wi-Fi spectrum and physical Ethernet connections. First, every AP only needs to broadcast on a single Wi-Fi channel (in each band) and can broadcast multiple SSIDs. This helps avoid interference due to multiple independent wireless systems trying to use the same frequencies. Second, each SSID can be tied to its own VLAN. This means logical network separation can be maintained in Wi-Fi without having to use additional spectrum. Third, multiple SSIDs can be tied to the same VLAN or standard Ethernet network. Each SSID can have its own security configuration as well. For example, in our use case, we have two different authentication mechanisms for granting access to the same network, one configured for WPA2-PSK and another for so-called enterprise certificates. This can be particularly useful for gradual transitions from old security mechanisms (e.g., WEP, WPA) or old Pre-Shared Keys (PSKs) to newer ones instead of needing to transition all devices at one time. In our case, to determine which devices may need reconfiguration to use certificates, we used the WLC to identify exactly which devices are using old PSK SSIDs. Once this number is reduced to an acceptable level, the old PSK SSID can be turned off and only certificate-based authentication will be allowed. Network Access Control

This section describes how network access control using a wireless LAN, as shown above, is applied to the wireless infusion pumps.

Before we describe network access controls, it’s important to discuss each pump’s wireless protection protocol. There are three available wireless protection protocols (WEP, WPA, and WPA2). We also describe in-depth options for WPA2-PSK. Finally, we describe options for WPA2 across the HDO enterprise. Many of the infusion pumps used in this NCCoE project are newer models, capable of supporting various wireless protocols. For HDOs, WPA2 is the recommended wireless protocol to use. WEP and WPA are considered insufficient for appropriately securing wireless network sessions. Our architecture is designed to support multiple levels of access control for different groups of users. The architecture is configured to use WPA2-PSK and WPA2-Enterprise security protocols for secure wireless connections to accommodate the best available security mechanisms depending on which vendor products your organization uses. Please note that a wireless infusion pump manufactured prior to 2004 may not be able to support these newer wireless security protocols [41].

The WPA2-PSK is often referred to as pre-share key mode. This protocol is designed for small office networks and does not require an external authentication server. Each wireless network device encrypts the network traffic using a 256-bit key. All pumps used in our example implementation support this wireless security mode, and each pump performed properly using this mode. However, because all devices share the same key in a pre-shared key mode using WPA2-PSK, if credentials are compromised, significant manual reconfiguration and change management will be required.

WPA2 enterprise security uses 802.1x/EAP. By using 802.1x, an HDO can leverage the existing network infrastructure’s centralized authentication services such as remote authentication dial-in use service, or RADIUS, authentication server to provide a strong client authentication. Cisco recommends that WPA2 Enterprise, which uses the AES (Advanced Encryption Standard) cypher for optimum encryption, be used for wireless medical devices, if available. We implemented WPA2-Enterprise with EAP-TLS security mode on several of our pumps to demonstrate that these pumps can leverage the public key infrastructure (PKI) to offer strong endpoint authentication and the strongest encryption possible for highly secure wireless transmissions. In this mode, pumps were authenticated to the wireless network with a client certificate issued by DigiCert Certificate Authority. During the authentication process, the pump’s certificates are validated against a RADIUS authentication server using Cisco ISE. Automatic logoff features allow the system to terminate the endpoints from the network after a predetermined time of inactivity. Organizations manage and control the client certificates via the certificate authority. With this capability, organizations may revoke and renew certificates as needed.

Once WPA2 is selected as the appropriate wireless protection protocol, certificates may be issued to authenticate infusion pumps using 802.1x/EAP-TLS mode, as illustrated Figure 5‑6: [28], [29], [30], [31], [32], [33], [34], [35], [36], [37], [38], [42], [46], [47], [48], [49], [50].

Certificate issuance involves the following three stages, denoted by shaded boxes in Figure 5-6:

  1. Certificate Registration

    Step 1: Request a certificate from the DigiCert Certificate Authority, which is a Certificate Register Manager. Request pump certificates through a standalone computer connected to the internet using DigiCertUtil, a certificate request tool, on behalf a pump.

    Step 2: The approved certificates are exported to the pumps using the specific tools provided by pump vendors. Typically, this activity is performed by a biomedical engineer.

    Step 3: Install the certificate into the Cisco ISE application.

  2. Authentication

    Authentication is performed by the Cisco ISE application to validate the pump certificate under the 802.1x/EAP-TLS. During the network access authentication procedure, the AP will pass the certification information to ISE server for validation. Once passed, the connection between the pump and the pump server will be established, and the data transmitted between the pump and AP is encrypted.

  3. Certificate Management

    Certificate management will provide services to revoke certificates when they are no longer in use, and will also manage the certificate revocation list, along with any related processes for renewing old certificates.

Figure 5-6: Network Access Control


The detailed process for setting up the 802.1x network authentication for pump and pump server communication is documented in Volume C of the How-to guide. Remote Access

Many medical devices and their back-end management systems required access by manufacturers for device repairs, configuration, software, and firmware patching and updates, or maintenance. A vendor network segment (VendorNet) is designed to provide external privileged access for vendors to their manufactured components and systems that reside within an HDO’s architecture. In the NCCoE lab, a VendorNet is implemented using TDi ConsoleWorks. ConsoleWorks is a vendor-agnostic interface that gives organizations the ability to manage, monitor, and record virtually any activities in the IT infrastructure that come from external vendors.

Communication using TDi ConsoleWorks for vendor access to products does not require the installation of software agents to establish connections for managing and monitoring targeted components. Established connections are persistent to facilitate IT operations, enforce security, and maintain comprehensive audit trails. All information collected by ConsoleWorks is time-stamped and digitally signed to ensure information accuracy, empower oversight, and meet compliance requirements. Through a standard web browser, ConsoleWorks can be securely accessed from any geographical location, eliminating the need for administrators and engineers to be locally present to perform their work.

Remote access is only allowed through a specific set of security mechanisms. This includes using a VPN at the network layer as shown in Figure 5-7 client, for vendors to authenticate to the VPN server [43], [44], [51].

Figure 5-7: Remote Access VPN


After the VPN connection is established at the application layer, the security proxy will restrict who can access certain resources within the enterprise network, as depicted in Figure 5‑8:. Vendors also authenticate to the HTTPS-based security proxy (see red line). Based on the vendor’s role, the security proxy will facilitate a Remote Desktop Protocol (RDP) connection to equipment in the biomedical engineering zone via the vendor support network (see green line). The credentials used to authenticate the RDP connection are stored by the security proxy and not disclosed to the vendor.

The remote access firewall/router is configured so that direct access between the VPN and vendor support is denied and the only allowed path is through the security proxy (see stop sign). Additionally, the firewall/router can further restrict what is accessible at the network layer from the security proxy. The security proxy is granted access to the internet to support patching and email alerts. The public IP address of the external firewall is configured to forward VPN traffic to the IP address of the VPN server [43], [44], [46], [47], [49], [51], [52], [53].

Figure 5-8: Remote Access

../_images/fig5-8.png External Access

A guest network allows visitors or patients to access internet services during their visit. As explained in the previous section (Guest Network Zone), the work traffic tends not to be of a clinical nature, but is offered as a courtesy to hospital visitors and patients to access the internet. The external firewall marks the boundary between the enterprise and the internet. As shown in Figure 5‑9:, this is the only point in the network where network address translation (NAT) is used. Additionally, the guest network for personal devices connects to the internet though the external firewall. The guest network is configured such that traffic cannot go between the enterprise and guest networks – only out to the internet. This is denoted by the stop sign. The external firewall is configured to provide the necessary services for guest users to use the internet, such as DHCP, which allows dynamic addressing for anyone. Typically, consumer equipment is connected here, such as smart phones, tablets, and personal entertainment systems (Figure 5-9) [52].

Figure 5-9: Remote External


5.3.2. Pump Controls

Wireless infusion pumps have the following controls:

  • endpoint protection
  • hardening
  • data protection. Endpoint Protection

Traditional security relies on the network border to provide security protection to its internal nodes, using security technologies such as application firewalls, proxy gateways, centralized virus scan, network intrusion detection, and prevention systems. This is no longer considered a best practice. The nodes, such as networked medical devices, should participate in their own security. Otherwise, the device can become the weakest element in the enterprise and present a risk to the entire HDO network.

To avoid the single point of failure caused by an unsecured node, every system should have an appropriate combination of local protections applied to it. These protections include code signing, anti-tampering, encryption, access control, white listing, and others. Hardening

Wireless infusion pumps and their servers are considered computing endpoints when it comes to hardening the software contained within these devices. Medical devices usually contain third-party commercial, off-the-shelf (COTS) products, including proprietary or commercial embedded operating systems, network communication modules, runtime environments, web services, or databases. Because these products can contain vulnerabilities, medical devices may also inherit these vulnerabilities just by using the products [2], [3], [7], [9], [25]. Therefore, it is important to identify all software applications used on medical devices, implement securing and hardening procedures recommended by the manufacturers, and apply timely patches and updates to guard against any newly discovered threats.

Hardening may include the following:

  • disabling unused or unnecessary communication ports and services
  • changing manufacturer default administrative passwords
  • securing remote access points if there are any
  • confirming the firmware version is up to date
  • ensuring hashes or digital signatures are valid

However, please note that most infusion pumps do not have the same level of storage resources and CPU processing capability as those provided for personal computers and servers. Data Protection

The two primary reasons for data protection are confidentiality and integrity. Medical devices may contain patient data such as patient name, medical record number, gender, age, height, weight, procedure number, medication and treatment information, or other identifiers that may constitute PHI. PHI must be appropriately protected, for example, through encryption or other safeguard measures that would prevent unauthorized disclosure of such information.

Infusion pumps may also contain configuration data such as drug libraries specifying dosage and threshold limits. This data must be protected against compromises as well. Our defense-in-depth approach for data integrity involves sandboxing the critical system files stored in pump servers using Symantec Advanced Data Center Security and encrypting messages when communicating between a medical infusion pump and the backend infusion management system, via Internet Protocol Security or secure sockets layer encryption (e.g., https, TLS).

5.3.3. Pump Server Controls

Pump server features vary. Usually, a pump server can be used to distribute firmware, the drug library, other software updates used inside the devices, or as a tool for providing services such as reporting and device asset management. Data collected by the infusion pump server is valuable for further analysis to provide reports on trends, compliance checking, and to measure infusion safety.

Because pump servers connect to infusion pumps to deliver and receive infusion-related information, it is also important to secure the infusion pump server, its associate applications, databases and communication channels as well. User Account Controls

Access to the pump server typically implements user name/password authentication. After the pump server is installed, an initial step is to define the password policy that applies to users accessing the pump server. When managing user accounts for a pump server, common cybersecurity hygiene should include the following:

  • changing factory default passwords
  • enforcing password policies
  • assigning each user’s access level using the least privilege principle
  • if supported, using centralized access management, such as LDAP for user account, management at the enterprise level
  • configuring auto logout Communication Controls

Pump servers interface with many other systems or components such as: databases, web services, and web portals. Communications between different systems can be configured. Pump servers might provide choices for selecting unsecure or secure TCP/IP ports for communication. We recommend using secure (e.g., stateful, encrypted network sessions) ports for message communication or for package download.

There may be a default setting for the communication interval, in number of seconds, for communication attempts between the server and the pump. Be sure to set this idle time-out setting properly. Application Protection

Application protection refers to software applications running on the pump servers. Most of the software application security concerns and security controls used on traditional personal computers and servers may also be applied to pump servers to protect data integrity and confidentiality. These control measures may include:

  • trusted applications
  • stronger access control mechanisms for pumps and pump servers
  • better key management
  • application white listing
  • sandboxing applications
  • performing code-signing verification for newly installed software
  • applying the latest patches and software updates
  • encrypting message data in-transit, or at rest

Server security baseline integrity is achieved via the use of three Symantec cybersecurity products on an enterprise network with a specific focus on wireless infusion pumps:

  • Symantec Data Center Security: Server Advanced (DCS:SA)
  • Symantec Endpoint Protection (SEP)
  • Symantec Advanced Threat Protection: Network (APT:N)

Each of these products provide protections for components in the enterprise systems in different levels. With pre-built policies, the Data Center Security Server installed can provide out-of-the-box host Intrusion IDS and IPS by monitoring and preventing suspicious server activities on pump servers. The use of DCS also provides the host firewall service for controlling inbound and outbound network traffic to and from a protected server. Using DCS, the configuration settings, file, and file systems in the pump server can be locked down using policy-based least privilege access controls to restrict application and operating system behavior and prevent file and system tampering.

Like DCS, Symantec’s Endpoint Protection (SEP) provides similar protection for endpoint devices and servers. SEP features in-memory exploit mitigation and anti-virus file protection to block malware from infecting protected endpoint servers. This will reduce the possibility of zero-day exploits on popular software that may not have been properly patched or updated. To protect endpoint servers, an SEP agent must be installed on servers.

Advanced Threat Protection: Network (ATP:N) can provide network-based protection of medical device subnets by monitoring internal inbound and outbound internet traffic. It can also be used as a dashboard to gain visibility to all devices and all network protocols. In addition, if ATP:N is integrated with the SEP, ATP can then monitor and manage all network traffic from the endpoints and provide threat assessments for dangerous activity to secure medical devices on an enterprise network. The use of these Symantec security products is depicted in Figure 5-10 below.

Figure 5-10: Pump Server Protection


5.3.4. Enterprise Level Controls Asset Tracking and Inventory Control

Medical asset management includes asset tracking and asset inventory control. Asset tracking is a management process used to maintain oversight of the equipment, using anything from simple methods such as pen and paper to record equipment, to more sophisticated IT asset management platforms. HDOs can use asset tracking to verify that a device is still in the possession of the assigned, authorized users. Some more advance tracking solutions may provide service for locating missing or stolen devices.

Inventory management is also important throughout a medical device’s life cycle. Inventory tracking should not be limited to hardware inventory management. It should also be expanded to include software, software versions, data stored and accessed in the devices, for security purpose. HDOs can use this type of inventory information to verify compliance with security guidelines and check for exposure of confidential information to unauthorized entities. Monitoring and Audit Controls

Logging, monitoring, and auditing procedures are essential security measures that can be used to help HDOs prevent incidents and provide an effective response when a security breach occurs. Logging records events to various logs; monitoring oversees the events for abnormal activities, such as scanning, compromises, malicious code, and denial of services in real time; and auditing reviews and checks these recorded events to find abnormal situations or evaluate if the applied security measures are effective. By combining the logging, monitoring, and auditing features, an organization will be able to track, record, review and respond to abnormal activities and provide historical records when needed.

Many malware and virus infections can be almost completely avoided by using properly configured firewalls or proxies with regularly updated knowledge databases and filters to prevent connections to known malicious domains. It is also important to review your firewall logs for blocked connection attempts so that you can identify the attached source and remedy infected devices if needed.

In our example implementation, user audit controls—simple audits—are in place. Although additional security incident and event managers (SIEM) and centralized log aggregation tools are recommended to maximize security event analysis capabilities, aggregation and analytics tools like these are considered out of scope for this project iteration.

Each system is monitored for compliance with a secure configuration baseline. Each system is also monitored for risks to known good, secure configurations by vulnerability scanning tools. In our project, the AP provided by Cisco, the Cisco ISE as Radius authentication server, VendorNet provided by TDI, and the pump servers from each vendor are all equipped with proper monitoring and logging capabilities. Real-time monitoring for events happening within these systems can be analyzed and compared to the baseline. If any abnormal behavior occurs, it can be detected. The auditing of data was considered out of scope for this reference design because the absence of an actual data center made auditing behavior impractical.

5.4. Final Architecture

The target architecture, depicted in Figure 5-11 , indicates the implementation of network segmentation and controls as described by this practice guide. Segmentation identified nine zones, ranging from the guest network to the medical device zone, and includes zones for Wi-Fi infrastructure, and core network infrastructure. The zoned concept implements firewall/router devices to enforce segmentation, with the firewall enforcing limited trust relationships between each zone. Noted in the diagram are processes that have impact on the overall architecture. Security controls are implemented to enforce encryption on network sessions. For Wi-Fi, leveraging standard protocols such as WPA2- PSK and WPA2-Enterprise created a secure channel for the pumps to communicate with the (AP)s, and to use TLS to secure the communication channel from the pumps to the server.

Figure 5-11: Target Architecture


6. Life Cycle Cybersecurity Issues

Configuration management throughout a device’s life cycle is a key process that is necessary for the support and maintenance of medical devices [3]. NIST SP 1800-5: IT Asset Management for the Financial Services Sector discusses IT Asset Management (ITAM), and, although the focus of the document pertains to financial services, similar challenges exist in healthcare [54]. Establishing a product life cycle management program addresses a few of the risks noted in previous sections of this guide, and should be considered as part of a holistic program for managing risks associated with infusion pump deployments.

Figure 6-1 illustrates a typical life cycle for an asset, and this model can be applied to medical devices. The sections below will take specific phases of the asset life cycle and discuss essential cybersecurity activities that should occur during those phases.

Figure 6-1: Asset Life Cycle [55]


6.1. Procurement

Asset life cycle management typically begins with Strategy, Plan, and Design phases, which lead into procurement. These phases are opportunities for hospitals to define requirements and identify where security controls may be implemented on infusion pumps or other devices that the hospital intends to acquire.

Phases leading into procurement enable the HDO, reseller, or manufacturer to ensure that the equipment that the HDO will deploy offers the appropriate combination of security and functionality required to render patient care. These phases also enable the hospital to implement appropriate security controls to safeguard the device and the information that it may store or process.

Purchasers at HDOs may request manifests or architectural guidance on secure deployment of the equipment and may perform research on products and the manufacturers that they have selected. While performing the research, HDOs may begin a risk assessment process to ensure that risks are mitigated.

Manufacturers maintain a document referred to as the MDS2 (Manufacturer Disclosure Statement for Medical Devices) that an HDO may review, enabling the HDO to determine possible vulnerabilities and risks [56]. Hospital purchasers may also determine if vulnerabilities exist in the proposed equipment by reviewing the FDA-hosted MAUDE database (Manufacturer and User Facility Device Experience).

Hospitals should also obtain any necessary training, education, and awareness material from the manufacturer and educate staff about the deployment, operation, maintenance, and security features available on their equipment. HDOs might consider writing user-friendly documentation to ensure that staff can use the equipment with confidence and competence.

Performing research and risk analysis during the phases leading into procurement will allow HDOs to make informed decisions. For further reference, we note that the Mayo Clinic has produced a best practice document that discusses procurement.

6.2. Operation

After procuring their equipment, hospitals onboard it during the Operation and Maintenance phases. Equipment purchasers should apply asset management processes (e.g., asset tagging and entry into a configuration management database or some other form of inventory tracking), and have standard baseline configurations implemented. Wireless infusion pumps may need to be configured to connect to a hospital’s Wi-Fi network (Medical Device zone, as depicted in the architecture section of this document; see Section, Medical Device Zone’s Wireless LAN and implement digital certificates to allow for device authentication.)

As noted above, hospitals should implement some type of configuration management database or asset inventory that captures granular information about the device. Implementing an ITAM mechanism enables the hospital to have visibility into their infusion pump deployment, with captured information that describes the make/model, firmware, OS, and software versions, a general description of the applied configuration along with change history, and physical location within the hospital. Regular maintenance of the ITAM would reduce risks, for example, that may emerge based on loss/theft, as well as provide a central knowledge repository that allows the hospital to coordinate any required maintenance or refresh.

As part of deployment, hospitals should apply practices noted by the manufacturer (e.g., regarding access control and authentication). As noted above, digital certificates should be installed to allow for device authentication to Wi-Fi, but engineers should implement access control and auditing mechanisms where applicable.

6.3. Maintenance

Pump manufacturers have two types of systems that require updating: the pumps and the pump servers. Pumps may implement control systems in firmware (writeable, non-volatile storage that may include an embedded operating or other control system). Control systems may be maintained through an update process that involves replacing all or parts of the operating or control system. Server components may be implemented on more conventional IT systems, using commercial operating systems (e.g., Windows or Linux variants).

Another aspect of configuration management that HDOs will want to pursue is that of patching. Patching, known colloquially as bug fixing, does not require a full replacement of software and is generally performed on pump servers. The patch frequency that manufacturers generally adhere to is monthly for patches and yearly for updates. This observation on timing comes from industry, not NIST—and is considered standard practice, rather than advice.

In addition to identifying patch frequency, organizations must be aware of likely vulnerabilities and the risks they introduce into the enterprise, and then decide whether a patch should be applied. NIST SP 800-40 Guide to Enterprise Patch Management Technologies discusses the importance of patch management and the challenges.

6.4. Disposal

The Dispose phase of the ITAM life cycle comes into play when products reach their end of life and are removed from hospital service. Wireless infusion pumps have increased in sophistication and information that each device may use, process, or store. The information found on pumps and related equipment may include sensitive information or information that may be regarded as PHI. As such, hospitals should seek to implement mechanisms to ensure that any sensitive information is removed from all storage areas that a pump or its system components may maintain. Practices to remove that information may be found in NIST SP 800-88 Guidelines for Media Sanitation [27].

7. Security Characteristics Analysis

We identified the security benefits of the reference design, how they map to NIST Cybersecurity Framework (CSF) subcategories, and the mitigating steps to secure the reference design against potential new vulnerabilities [10], [14].

7.1. Assumptions and Limitations

Our security analysts reviewed the reference architecture and considered if the integration described in this guide would meet security objectives. The analysts purposely avoided testing products, and readers should not assume any endorsement or diminution of the value of any vendor products. Although we have aimed to be thorough, we counsel those following this guide to evaluate their own implementation to adequately gauge risks particular to their organizations.

7.2. Application of Security Characteristics

Using the CSF subcategories to organize our analysis allowed us to systematically consider how well the reference design supports specific security activities and provides additional confidence that the reference design addresses our use case security objectives. The remainder of this subsection discusses how the reference design supports each of the identified CSF subcategories [10].

7.2.1. Supported CSF Subcategories

The reference design focuses primarily on the Identify and Protect function areas (i.e., subcategories) of the CSF. Specifically, the reference design supports:

  • three activities in the CSF Identify function area: Asset Management, Business Environment, and Risk Assessment
  • activities from each category of the CSF Protect function area, except for Awareness and Training

We discuss these CSF subcategories in the following subsections. ID.AM-5: Resources (e.g., Hardware, Devices, Data, Time, and Software) are Prioritized Based on Their Classification, Criticality, and Business Value

To address this subcategory of the Identify function, we conducted an asset inventory as part of the risk management process. For this project, we identified assets and entered them into the Clearwater Compliance IRM|Analysis™ tool. This risk analysis tool categorized project resources into types of assets. Additionally, it characterized the system, enabling us to address the criticality of our resources. Our project only partially satisfies the Resources subcategory as we focused on technical solutions and did not write a business impact assessment or business continuity plan. ID.BE-1: The Organization’s Role in the Supply Chain is Identified and Communicated

Organizations who may be using this guide are the end users of medical devices. NIST SP 800-53, control SA-12, most directly applies to such end users because it directs users to define which security safeguards to employ to protect against supply chain threats [45]. Our implementation uses network segmentation to limit exposure to the wireless infusion pump from other areas within a hospital network. This is done because if a vulnerability is identified in a device, segmentation and access control will help safeguard the medical device until the vulnerability can be properly addressed. ID.RA-1: Asset Vulnerabilities are Identified and Documented

Given a reasonably long life cycle, even the best designed electronic asset will eventually be impacted by a vulnerability. Medical devices can have a long product life cycle, per TIR57, “Device or platform used for decades” [9], [25]. Identifying vulnerabilities in an asset may occur via various means. Some may be identified through onsite testing; however, often the manufacturer or a researcher will find the vulnerability. An effective risk management program is essential to reduce the likelihood that an identified vulnerability will be exploited. This implementation uses a combination of risk analysis tools and methods to help reduce the impact a vulnerability may have on the build. PR.AC-1: Identities and Credentials are Issued, Managed, Revoked, and Audited for Authorized Devices, Users, and Processes

Following the segmentation approach used to separate hospital networks into zones, our implementation employs role-based security, which limits access based on who actually need to access the pump. HDO users with no business need are not permitted access to pumps, pump servers, or related components. Most users, including biomedical staff, are granted access via active directory. Although our NCCoE lab did not use single-sign-on (SSO), using SSO can make pump access seamless to an end user. How to manage credentials of clinicians who operate the pump directly is beyond the scope of this guide.

Remote access is necessary to maintain proper functionality of infusion pumps, but the mechanism for gaining and controlling remote access varies depending on the user type. Hospital staff such as biomedical engineers remotely access pumps through a VPN and hardened gateway at the application layer. Such users are considered trusted HDO staff with access to other network resources throughout the enterprise.

Pump manufacturers who may need to reach a device for maintenance or troubleshooting can gain access into a VendorNET zone only, from which they can access pumps and pump servers, but not other zones in the enterprise. Our example implementation uses ConsoleWorks for authentication, role-based access control, and recording system management actions of remote vendor activity. PR.AC-4: Access Permissions and Authorizations are Managed, Incorporating the Principles of Least Privilege and Separation of Duties

This CSF subcategory is supported for the pumps and pump servers with Data Center Security (DCS). The configuration settings, file, and file systems in the pump server are restricted, thereby implementing policy-based least privilege access control. DCS restricts application and operating system behavior and prevents unauthorized users from tampering with files and systems.

Least privilege is also addressed via the network design itself. By limiting user access to the zones where a user has a business need for access, the architecture seeks to enforce the concept of least privilege and separation of duties. PR.AC-5: Network Integrity is Protected, Incorporating Network Segregation Where Appropriate

Network segmentation is a key function of this reference design. Segregating Guest, Business Office, Database, Enterprise Services, Clinical Server, and Biomedical Engineering networks from the Medical Device zone reduces the risk of medical devices being negatively impacted from malware or an exploit in another zone. Using a combination firewall/router device to segregate the zones also limits risk to the enterprise should a vulnerability be exploited within the medical device zone. PR.DS-2: Data-In-Transit is Protected

Data-in-transit occurs when data travels from the drug library on a pump server to an infusion pump. The information being passed most frequently will be types of drugs and dosage range. This information is not PHI; however, the availability and integrity of this information are important. This project uses WPA2-AES, which authenticates pumps to the wireless network with client certificate issued by DigiCert Certificate Authority. PR.DS-6: Integrity Checking Mechanisms are Used to Verify Software, Firmware, and Information Integrity

This CSF subcategory is supported with server and agent products to monitor and lock-down configuration settings, files, and file systems in the pump server using the policy-based least privilege access control. This limits application and operating system to expected behavior and reduces the likelihood of system from digital tampering. PR.IP-1: A Baseline Configuration of Information Technology/Industrial Control Systems is Created and Maintained Incorporating Appropriate Security Principles (e.g., Concept of Least Functionality)

A mature cybersecurity program follows a documented secure baseline for traditional information technology components and medical devices. This NCCoE project has implemented hardening for each component used in the build and documented the steps taken. This initial step produces a secure baseline configuration. Because this project uses five different types of wireless infusion pumps, the baseline is of limited use; however, in a healthcare organization with many medical devices and multiple biomedical and information technology professionals, it is essential to develop and implement a baseline configuration for vulnerability management. PR.MA-2: Remote Maintenance of Organizational Assets is Approved, Logged, and Performed in a Manner that Prevents Unauthorized Access

We controlled remote access to pump vendors by implementing ConsoleWorks, a software tool that records all the actions performed over a connection; thereby providing an audit trail that documents vendor activity. PR.PT-1: Audit/Log Records are Determined, Documented, Implemented, and Reviewed in Accordance with Policy

Our example implementation supports this CSF subcategory by enabling logging on all devices in two ways: with a logging capability and with a process of identifying which events the log will record. Although our project employs auditing and recognizes its importance in a cybersecurity program, log aggregation and implementing a log review process, albeit vital activities, are beyond this project’s scope. DE.AE-1: A Baseline of Network Operations and Expected Data Flows for Users and Systems is Established and Managed

As we did with systems and medical devices, we took a least functionality approach when configuring the network. We followed best practices for configuring firewalls based on a default deny, restricted SSID broadcast, and limiting the power of wireless signals.

This CSF subcategory is supported by the Symantec Intrusion Detection System (IDS) component of the reference design. This tool identifies, monitors, and reports anomalous network traffic that may indicate a potential intrusion. Endpoint protection implements policies for expected behavior and alerts when activities occur outside the usual patterns.

7.3. Security Analysis Summary

Our reference design’s implementation of security surrounding wireless infusion pumps helps reduce risk from a pump, even if a vulnerability is identified in a pump, by creating a more secure environment for medical devices. The key feature is network segmentation. Supporting this zone approach, our project build follows security best practices to harden devices, monitor traffic, and limit access via the wireless network to only authorized users. Any organization following this guide must conduct its own analysis of how to employ the elements we’ve discussed here in their environment. It is essential that organizations follow security best practices to address potential vulnerabilities and minimize any risk to the operational network.

8. Functional Evaluation

We conducted a functional evaluation of our example implementation to verify that several common provisioning functions used in our laboratory test worked as expected. We also needed to ensure that the example solution would not alter normal pump and pump server functions. The test plan in Section 8.1 outlines our test cases, the purposes, and desired outcomes.

The subsequent sections explain the functional tests in more details and list the procedures for each of the functional tests.

8.1. Functional Test Plan

Test Case Purpose Desired Outcomes
WIP-1: Network Segmentation Test the effectiveness of network segmentation All firewall rules for each segment are implemented correctly, as designed.
WIP-2: Data Center Security Test the effectiveness of Data Center Security (DCS:SA) to see that it follows defined policies The inbound and outbound network traffic to and from servers is controlled per host firewall rules.
WIP-3: Endpoint Protection Test the effectiveness of the Symantec (SEP) to ensure that it follows defined policies A bad file is detected and the planned installation action is blocked.
WIP-4: Advanced Threat Protection Test the effectiveness of Advanced Threat Protection: Network (ATP:N) to ensure it follows defined policies The URLs in the blacklist are blocked. Also, the URLs in the whitelist are allowed.
WIP-5: Protected Remote Access Test the effectiveness of the remote access controls The vendor can only access to what’s been granted for access with the correct privileges.
WIP-6: Pump and Pump server network connection Confirm the installation and configuration of pumps and pump server are fully completed Pumps and pump servers are connected to the network and pumps communicate to the corresponding pump servers.
WIP-7: Pump and Pump server basic functions Test a set of operational events between pumps and pump servers Pumps are connected to the corresponding pump server, able to perform a set of operational events.

8.1.1. Test Case: WIP-1

Test Case Name Network Segmentation
  • Show that the WIP solution allows the inbound and outbound traffic of a given zone as per design
  • Show the WIP solution blocks the inbound and outbound traffic of a given zone as per design
  • WIP network segmentation is implemented
  • Internal firewall rules of each zone are defined and implemented
  • The ASAs are configured to use stateful filtering, so return traffic is automatically allowed if the initial connection is allowed. Everything not explicitly allowed in a rule is denied
  1. Use Medical Device and Biomedical Segment zones as a test example.
  2. Review the port and communication protocol requirements from each tested pump vendor, for pump and corresponding pump server
  3. Configure the ASA firewall access list to open only the needed ports and allow access only to necessary protocols
  4. Everything not explicitly allowed in a rule is denied.
  1. Review the ASA configuration file to verify that the ASA firewall is configured to only allow communication with a specific protocol and port as specified by the pump vendors. All other communication between these two segments will be denied and blocked using a command such as:
  2. “show access-list | include eq” to see the opened ports
  3. Use network discovery scanning tools such as nmap to check the open, closed, or filtered ports

8.1.2. Test Case: WIP-2

Test Case Name Data Center Security
  • Show that the WIP solution detects files that are defined in policy and apply the file and system tampering prevention methods by locking down files
  • DCS:SA is installed and configured
  • File and System Tamper Prevention policy is set
  • Windows_Baseline_detect_TEST is used as the baseline for server hardening

There are two admin applications for the DCS, the console admin and the portal admin. The console admin is the thick client and the portal is the thin client. The console is used to create and modify the policy, and the portal is used to publish the policy. Portal URL is

  • Log in to the DCS Console
  • Select the Policy->Work Space->Pump Server folder
  • Select Detection tab to show the detection polices
  • You should see a preinstalled policy-Windows_Baseline_detect_Test, double click it to open a detailed policy editing window for configuration
  • Create a policy for hardening the server, such as “do not allow any file to be installed on the server”
  • Enable the policy
  • Publish the policy
Result Test to verify that no file is allowed to be installed on the protected server

8.1.3. Test Case: WIP-3

Test Case Name Endpoint Protection/Advance Threat Protection
  • Show that the WIP solution has the capability to detect a bad file and act (i.e., stop installing that bad file)
  • Symantec Endpoint Protection (SEP) is installed and configured
  • Define the antivirus signature rule
  • Create a ‘bad’ file that is part of the antivirus signature rule
  1. Make sure the test server has a Symantec End Protection agent installed and enabled.
  2. From the server machine, open an IE browser and type: This is a test site provided by Symantec containing some unharmful links for testing purposes
  3. Click some links such as ‘antivirus test’ from the list to install some suspicious software on the test server
  4. The installation should be blocked by the server’s SEP and the violation incident should be reported in the ATP
  5. To view the violation in ATP: login to the ATP Server from a browser in a server that can access the 192.168.120.x network, such as the Active Directory server (
  6. Type this URL in the browser:
  7. View any violation incidents from the ATP to verify that the bad link is blocked.
  • If wanted, one can dive into the details to see which bad sites it tried to connect.
  • Then for an open incident, need to close it.

To verify that the ATP:N and Symantec deployment and configuration offers needed security protection to prevent malware installed in a server.

To view the violation, in ATP: login to the ATP Server from a browser in a server that can access the network, where the tested server is located.

  1. View any violation incidents from the ATP to verify that the bad link is blocked.
  2. Check the details to see which bad sites it tried to connect.
  3. Close open incidents

8.1.4. Test Case: WIP-4

Test Case Name Advanced Threat Protection
  • Show that the WIP solution has effective network threat protection based on network intrusion prevention, URL, and firewall policies.
  • Advanced Threat Protection: Network (ATP:N) is installed and configured
  • Firewall and browser protection rules are defined
  1. Logon to a vm server with APT:N installed
  2. Access to a malicious website
  3. Check the results
Result See Test Case WIP-3

8.1.5. Test Case: WIP-5

Test Case Name Protected Remote Access
  • Show that the WIP solution has the protected remote access capability. The VendorNet concept was created out of a need to give vendors more restricted remote access to a lab than NIST/NCCoE/MITRE staff. VendorNet is an NCCoE network created for each lab that is tied to an active directory group. This group of people is then allowed to access the lab through VendorNet. VendorNet hosts controlled access mechanisms such as ConsoleWorks, file transfer servers, or other remote access proxy services.
  • VendorNet is created
  • TDi ConsoleWorks is installed and configured
  • ConsoleWorks profile and user are created
  1. Using public Internet, remotely logon to the NCCoE VPN
  2. Logon to ConsoleWorks using the IP address:
  3. From the graphical menu, select the View to view graphical connections
  4. Each external vendor can only view the resources assigned to them
  5. Access the granted hosts
  6. Perform the allowed operations as specified
  7. Check the results
  1. Verify that the vendor can access associated pump server using VendorNet and ConsoleWorks
  2. Verify that they can perform the preassigned operational activities
  3. Verify that they cannot perform unauthorized operations, such as some administration task, such as adding a new user account
  4. Verify that all activities performed by the external vendor are logged and can be audited as needed

8.1.6. Test Case: WIP-6

Test Case Name Pump and Pump Server Network Connection
  • Show that the WIP solution establish the wireless network connection between each vendor’s pumps and their corresponding pump server
  • Wireless router with pre-share password SSID has been set up
  • Infusion pump servers have been installed and configured
  • Infusion pumps have been installed and configured using WPA2-PSK or WPA2-ENT/EAP-TLS for secure wireless network connection
  • Cisco ISE is installed and configured with root CA installed
  1. Turn on the pump
  2. Check the wireless indicator
  3. Check the Access Point and ISE administration portals for device connection and authentication status
  4. Check the Infusion Pump server management tool for discovered pumps

Both the access point portal should indicate that the pumps are successfully connected to the network

The pump server admin portal should indicate the pump is online and in use. (Note: the way the pump server portal displays these messages is vendor dependent.)

In the case of WPA2-Ent/EAP TLS wireless access mode, the Cisco ISE should display that the pumps are successfully authenticated

8.1.7. Test Case: WIP-7

Test Case Name Pump and Pump Server Basic Functions
  • Show that the WIP solution supports the basic operational events for each vendor’s pumps and their corresponding pump server
  • Successful test results of WIP-6
  • The drug library for a specific pump has been created by a pharmacist and validation has been performed.
  • The drug library has been successfully published or loaded to the infusion pump server to be tested
  1. From the pump server, send the new version of drug library to its pumps. Following is an example procedure used by Hospira to send Drug Library to its pump using the MedNet Software Server:
  • Log in to a Metnet software server
  • Request the download of the drug library to one or more pump
  • MedNet displays the drug library download status as “Pending”
  • MedNet using MedNet Service forwards the drug library to infusion pump selected
  • Pump infuser downloads the drug library from the MedNet Server
  • Pump Infuser sends a download status update to Hospira MedNet server to indicate the drug library is successfully downloaded and wait for installation
  • The pump server displays a download status as “On Pump”
  • The operator of the pump powers down the pump and choose to install the new drug library when prompted by the infuser
  • The pump sends the update status to MedNet to indicate that the drug library was successfully installed and a “Completed” status is displayed.
  1. From the pump server, send the new version of software updates to its pumps (Using Smiths Medical pump as an example). Using the PharmGuard pump server, packages containing data such as device configuration data or firmware, specific to an installed Smiths Medical device model can be installed. The package tested is provided by Smiths Medical.
  • Log in to a PharmGuard server
  • Select Package Deployment from the Asset Management drop-down menu, all previously-deployed packages, if any, are listed
  • Click Add Package
  • Click Browse to navigate to and select the package file
  • Click Upload to upload the package. After package file is read, information about the package is displayed in the package table
  • Select the package you like to deploy and click View/Deploy, the package detailed information is displayed
  • Click Deploy to deploy the new package
  • Enter the name for the deployment and specify a start deploy
  • Enter the required password and click Continue
  • After you confirm the package deployment, the name of the newly-deployed package displays in the Deployment list with the Status of Active
  • To check if a package has been received by the individual pump associated with the package deployment, you need to check the device itself
Result Using the device or the corresponding pump server portal to verify that the intended package has been successfully deployed. How this information is displayed is device- and manufacturer-specific. Please consult documentation for specific devices for more information.

9. Future Build Considerations

During our development of this project and practice guide, we did not implement several components; however, they should be considered. We did not implement a commercially available electronic health record (EHR) system. EHRs are often regarded as central within a hospital.

Other solutions that were not implemented in the lab were a central asset inventory management tool, or mechanisms to perform malware detection or network monitoring in the Medical Device zone. An update to this practice guide could evaluate these components and other control mechanisms that may become available in the future.

Appendix A Threats

Below are some potential known threats in the healthcare environments that use network-connected medical devices, such as wireless infusion pumps.

  • Targeted attacks: threats involving actors that attempt to compromise the pump and system components directly affecting pump operations, including the pump, the pump server, drug library, or drug library management systems. Actors who perform such targeted attacks may be external, in other words those who attempt to access the pump system through the public Internet, or via vendor support networks or VPNs. There may also be internal actors, such as those on staff who may be involved in accidental misconfiguration or who possess provisioned access and abuse their granted privileges, or patients or other visitors who attempt to modify the behavior of a pump.
  • Advanced Persistent Threats: APTs occur when the threat actor attempts to place malicious software on the pump or pump system components, which may enable that threat actor to perform unauthorized actions, either on the pump system itself, or as a pivot point to cause adverse conditions for hospital internal systems that may have reachability from the pump network environment. Placement of malicious software may or may not cause adverse scenarios on the pump or its system components.
  • Disruption of Service – Denial of Service (DoS) and Distributed Denial of Service (DDoS) attacks: DoS or DDoS attacks may be components found in a broader APT scenario. Such attacks are intended to cause the unavailability of the pump or pump system components, thus rendering providers with degraded capability to fulfill patient care.
  • Malware infections: In this type of attack, a threat actor places malicious software on the pump, likely as part of an APT campaign, or to cause an adverse situation on the pump or pump systems. One example of a malware infection is that of ransomware, in which malicious software would cause a disruption of the availability of the pump for standard operations, and may affect patient safety by preventing providers from leveraging system functionality (e.g., the ability to associate the pump with a patient and deliver medications), or by preventing the pump from effectively using safety measures such as the drug library.
  • Theft or loss of assets: This threat type applies when the pump or pump system components are not accounted for in an inventory, thereby leading to degraded availability of equipment, and a possible breach of PHI.
  • Unintentional misuse: This threat considers the possibility that the pump or its components may be unintentionally misconfigured or used for unintended purposes, including errors introduced through the misapplication of updates to operating systems or firmware, misconfiguration of settings that allow the pump to achieve network connectivity or communication to the pump server, misapplication or errors found in the drug library, or errors associated with fluids applied to pumps.

Vulnerable systems or devices directly connected to the device (e.g., via USB, or other hardwired non-network connections): Extending from the unintentional misuse of the device, this threat considers scenarios in which individuals may expose devices or server components using external ports or interfaces for purposes outside the device’s intended use, for example, to extract data to portable storage media, or to connect a mobile device to recharge that device’s battery. In leveraging ports for unintended purposes, threat actors may enable malicious software to migrate to the pump or server components, or to create adverse conditions based on unexpected connections.

Appendix B Vulnerabilities

Here’s a list of typical vulnerabilities that may arise when using wireless infusion pumps:

  • Lack of asset inventory: Deficient or out-of-date inventories represent a cybersecurity control deficiency that may lead to the loss/theft of devices or equipment, with little chance for the hospital to recover or take recourse against losses. Deficient asset inventory controls, when paired with a credible threat, such as the loss or theft of a device or equipment, raises risks associated with a provider’s ability to render patient care, and may expose PHI to unauthorized individuals.

  • Long useful life: Infusion pumps are designed to perform clinical functions for several years, and they tend to have long-term refresh rates. One vulnerability associated with infrequent refresh is that each device’s technological attributes may become obsolete or insufficient to support patching, updating, or the support of cyber security controls that may become available in the future.

  • Information/Data Vulnerabilities

    • Lack of encryption on private/sensitive data at rest: Pump devices may have local persistent storage, but they may not have a means to encrypt data stored on the device. Locally stored data may include sensitive configuration information, or patient information, including possible PHI.
    • Lack of encryption on transmitted data: Sensitive data should be safeguarded in transit as well as at rest. Where capabilities exist, pumps and server components should employ encryption on the network or when transmitting sensitive information. An inability to safeguard data in transit using appropriate encryption capabilities may expose sensitive information or allow malicious actors to determine how to connect to a pump or server to perform unauthorized activities.
    • Unauthorized changes to device calibration or configuration data: Modifications made to pump or server components that are not accurately approved, deployed, or tracked may lead to adverse operation of the equipment. Hospitals should ensure that changes to device calibration, configuration, or modification of safeguard measures such as the drug library are performed and managed using appropriate measures.
    • Insufficient data backup: Providing backup and recovery capability is a common cybersecurity control to ensure HDOs can restore services in a timely fashion after an adverse event. Hospitals should perform appropriate pump system backup and restore functions.
    • Lack of capability to de-identify private/sensitive data: As a secondary cybersecurity control to data encryption, hospitals may wish to consider the ability to de-identify or obfuscate sensitive information or PHI.
    • Lack of data validation: Data used and captured by infusion pumps and associated server components may require data integrity assurance to support proper functioning and patient safety. Mechanisms should be used to provide assurance that data cannot be altered inappropriately.
  • Device/Endpoint (Infusion Pump) Vulnerabilities

    • Debug-enabled interfaces: Interfaces required to support or troubleshoot infusion pump functions should be identified, with procedures noted to indicate when interfaces are available, and how interfaces may be disabled when not required for troubleshooting or system updates/fixes.
    • Use of removable media: Infusion pumps that include external or removable storage should be identified. Cybersecurity precautions are necessary because the use of removable media may lead to inappropriate information disclosure, and may provide a viable avenue for malicious software to migrate to the pump or server components.
    • Lack of physical tamper detection and response: Infusion pumps may involve physical interaction, including access to interfaces used for debugging. HDOs should enable mechanisms to prevent physical tampering with infusion pump devices, including alerting appropriate personnel whenever a pump or its server components are manipulated or altered.
    • Misconfiguration: Mechanisms should be used to ensure that pump configurations are well managed and may not be configured to produce adverse conditions.
    • Poorly protected and patched devices: Like the misconfiguration vulnerability, HDOs should implement processes to protect/patch/update pumps and server components. This may involve including controls on the device, or provisions that allow for external controls that would prevent exposure to flaws or weaknesses.
  • User or Administrator Accounts Vulnerabilities

    • Hard-coded or factory default passcodes: Processes or mechanisms should be added to prevent the use of so-called hard coded or default passcodes. This would overcome a common IT systems deficiency in the use of authentication mechanisms for privileged access to devices in terms of using weak passwords or passcodes protection. Weak authentication mechanisms that are well known or published degrade the effectiveness of authentication control measures. HDOs should implement a means to update and manage passwords.
    • Lack of role-based access and/or use of principles of least privilege: When access management roles and principles of least privilege are poorly designed, they may allow the use of a generic identity (e.g., a so-called admin account) that enables greater access capability than necessary. Instead, HDOs should implement processes to limit access to privileged accounts, infusion pumps and server components, and use accounts or identities that tie to specific functions, rather than providing/enabling the use of super user, root, or admin privileges.
    • Dormant accounts: Accounts or identities that are not used may be described as dormant. Dormant account information should be disabled or removed from pumps and server components.
    • Weak remote access controls: When remote access to a pump and or server components is required, access controls should be appropriately enforced to safeguard each network session and ensure appropriate authentication and authorization.
  • IT Network Infrastructure Vulnerabilities

    • Lack of malware protection: Pumps and server components should be protected using processes or mechanisms to prevent malware distribution. When malware protection cannot be implemented on end-point devices, malware detection should be implemented to protect network traffic.
    • Lack of system hardening: Pumps and server components should incorporate protective measures that limit functionality only to the specific capabilities necessary for infusion pump operations.
    • Insecure network configuration: HDOs should employ a least privilege principle when configuring networks that include pumps and server components, limiting network traffic capabilities, and enforcing limited trust between zones identified in hospital environments.
    • System complexity: When implementing network infrastructure controls, hospitals should seek device models and communications paths/patterns that limit complexity where possible.

Appendix C Recommendations and Best Practices

Associated best practices for reducing the overall risk posture of infusion pumps are also included in the following list:

  • Consider forming a Medical Device Security Committee composed of staff members from biomedical services, IT, and InfoSec that would report to C-suite governance.

    • Enable this committee to manage the security of all network-connected medical devices. Too often, for example, the biomedical services team is solely responsible for cradle-to-grave maintenance of all aspects of medical devices, including cybersecurity, leaving IT and InfoSec staff out-of-the-loop.
    • Develop a committee charter with roles and responsibilities and reporting requirements to the C-suite and Board of Directors.
  • Consider the physical security of mobile medical devices including wireless infusion pumps.

    • Designate a secure and lockable space for storing these devices when they are not in use.
    • Ensure that only personnel with a valid need have access to these spaces. Ideally, a proximity system with logging should be used and audited frequently.
  • Create a comprehensive inventory of medical devices and actively manage it.

    • Consider the use of Radio-frequency identification (RFID) or Real-time locating systems (RTLS) technologies to assist with inventory processes and help staff locate devices that have been moved without documentation.
  • Ensure that any Cybersecurity Incident Response Plan includes medical devices.

    • Recently, the FDA and Industrial Control System – Computer Emergency Response Team(ICS-CERT) have both issued cybersecurity vulnerability advisories for medical devices. This was the first major warning to covered entities regarding medical device vulnerabilities. Most covered entities have not incorporated medical device response into their planning.
  • Ensure that pumps cannot step down to a Wireless Encryption Protocol (WEP) encrypted network.

    • WEP is a compromised encryption protocol and should NEVER be used in operational wireless networks.
    • Operating any form of IT equipment including medical devices over a WEP network will result in the potential for data compromise and a regulatory breach.
    • Any wireless network should be using, at a minimum, Wi-Fi Protected Access 2 (WPA2). This protocol implements NIST-recommended Advanced Encryption Standard (AES).
  • Put in place an Information Security department and functionally separate it from the IT department. This is necessary to ensure operational IT personnel are not responsible for any information security measures, which may otherwise lead to a fox-guarding-the-hen-house situation.

    • Enable a separate InfoSec department to report to the Chief Information Security Officer (CISO) rather than to the Chief Information Officer (CIO.)
    • Make this organization part of the Medical Device Security Committee.
  • Create an operational information security program. This can take the form of an in-house Security Operations Center (SOC) to monitor information systems and initiate cybersecurity incident response, to include monitoring of potential exploits of medical devices, as necessary. Alternatively, organizations may wish to consider a Managed Security Service Provider (MSSP) to perform these duties.

  • Ensure that vendor management includes the evaluation of information security during the due diligence phase of any related procurement processes. Too often, the Information Security team is not brought in until after contracts have been signed.

    • When purchasing medical devices, ensure that devices incorporate the latest cybersecurity controls and capabilities.
    • Understand roles and responsibilities related to upgrades, patching, password management, remote access, etc., to ensure the cybersecurity of products or services.
  • Consider media access control (MAC) address filtering to limit exposure of unauthorized devices attempting to access the network. This would identify a bad actor attempting access a medical device from within the network through an exposed wired Ethernet port.

  • Develop or update policies and procedures to ensure a holistic approach to deployment, sanitization, and reuse of medical devices; include the Medical Device Security Committee.

Appendix C References

[1](1, 2, 3) FDA, Infusion Pumps Total Product Life Cycle - Guidance for Industry and FDA Staff, Document issued on: December 2, 2014. Accessed 6 April 2017:
[2](1, 2, 3, 4) FDA, Content of Premarket Submissions for Management of Cybersecurity in Medical Devices - Guidance for Industry and Food and Drug Administration Staff, Document Issued on: October 2, 2014. Accessed 6 April 2017:
[3](1, 2, 3, 4, 5, 6, 7) FDA, Postmarket Management of Cybersecurity in Medical Devices - Guidance for Industry and Food and Drug Administration Staff, Document Issued on: December 28, 2016. Accessed 6 April 2017:
[4]Department of Homeland Security (DHS), Attack Surface: Healthcare and Public Health Sector. Accessed 6 April 2017:
[5]Integrating the Healthcare Enterprise (IHE) Patient Care Device (PCD), Technical Framework White Paper. Accessed 6 April 2017:
[6](1, 2, 3) IHE PCD, White Paper, Medical Equipment Management (MEM): Cyber Security. Accessed 6 April 2017:
[7](1, 2, 3, 4, 5, 6) FDA, Guidance for Industry - Cybersecurity for Networked Medical Devices Containing Off-the-Shelf (OTS) Software. Accessed 6 April 2017:
[8](1, 2, 3) IHE PCD, White Paper, MEM: Medical Device Cyber Security – Best Practice Guide. Accessed 6 April 2017:
[9](1, 2, 3, 4, 5, 6, 7, 8, 9, 10) AAMI TIR57, Principles for medical device security – risk management
[10](1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12) NIST Cybersecurity Framework - Standards, guidelines, and best practices to promote the protection of critical infrastructure. Accessed 6 April 2017:
[11](1, 2, 3, 4, 5, 6) NIST SP 800-30, Guide for Conducting Risk Assessments. Accessed 6 April 2017:
[12](1, 2, 3, 4, 5) NIST SP 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach. Accessed 6 April 2017:
[13](1, 2, 3, 4) NIST SP 800-39, Managing Information Security Risk Organization, Mission, and Information System View. Accessed 6 April 2017:
[14](1, 2, 3, 4) NIST SP 800-53 Rev 4, Security and Privacy Controls for Federal Information Systems and Organization. Accessed 10 April 2017:
[15](1, 2) IEC Technical Report (TR) 80001-2-1, Edition 1.0 2012-07, Technical Report, Application of risk management for IT-networks incorporating medical devices – Part 2-1: Step-by-step risk management of medical IT-networks – Practical applications and examples
[16](1, 2, 3, 4) IEC TR 80001-2-2, Edition 1.0 2012-07, Technical Report, Application of risk management for IT Networks incorporating medical devices – Part 2-2: Guidance for the disclosure and communication of medical device security needs, risks and controls
[17](1, 2, 3, 4, 5) IEC TR 80001-2-3, Edition 1.0 2012-07, Technical Report, Application of risk management for IT-networks incorporating medical devices – Part 2-3: Guidance for wireless networks
[18](1, 2, 3, 4) IEC TR 80001-2-4, Edition 1.0 2012-11, Technical Report, Application of risk management for IT-networks incorporating medical devices – Part 2-4: Application guidance – General implementation guidance for healthcare delivery organizations
[19](1, 2, 3) IEC TR 80001-2-5, Edition 1.0 2014-12, Technical Report, Application of risk management for IT-networks incorporating medical devices – Part 2-5: Application guidance – Guidance on distributed alarm systems
[20]National Institute of Standards and Technology (NIST) Special Publication (SP) 800-66, An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule. Accessed 6 April 2017:
[21]Health Insurance Portability and Accountability Act (HIPAA) Security Rule. Accessed 6 April 2017:
[22]Department of Health and Human Services (HHS) HIPAA Administrative Simplification Statute and Rules. Accessed 6 April 2017:
[23](1, 2) American National Standards Institute (ANSI)/Association for the Advancement of Medical Instrumentation (AAMI)/International Electrotechnical Commission (IEC) 80001-1:2010, Application of risk management for IT Networks incorporating medical devices – Part 1: Roles, responsibilities and activities
[24](1, 2) ISO 14971, 2007 Medical devices – Application of risk management to medical devices
[25](1, 2, 3, 4, 5) IHE PCD Medical Equipment Management: Medical Device Cybersecurity – Best Practice Guide
[26](1, 2, 3, 4, 5) NIST SP 800-53 Rev 4, Recommended Security and Privacy Controls for Federal Information Systems and Organizations. Accessed 6 April 2017:
[27](1, 2) NIST SP 800-88, Guidelines for Media Sanitization. Accessed 6 April 2017:
[28](1, 2, 3) NIST SP 800-111, Guide to Storage Encryption Technologies for End User Devices. Accessed 6 April 2017:
[29](1, 2, 3) NIST SP 800-32, Introduction to Public Key Technology and the Federal PKI Infrastructure. Accessed 6 April 2017:
[30](1, 2, 3) NIST SP 800-57 Part 1 – Rev 3, Recommendation for Key Management: Part 1: General (Revision 3). Accessed 6 April 2017:
[31](1, 2, 3) NIST SP 800-57 Part 2, Recommendation for Key Management: Part 2: Best Practices for Key Management Organization. Accessed 6 April 2017:
[32](1, 2, 3) NIST SP 800-57 Part 3 Rev 1, Recommendation for Key Management: Part 3: Application-Specific Key Management Guidance. Accessed 6 April 2017:
[33](1, 2, 3, 4) NIST SP 800-48 Rev 1, Guide to Securing Legacy IEEE 802.11 Wireless Networks. Accessed 6 April 2017:
[34](1, 2, 3, 4) NIST SP 800-97, Establishing Wireless Robust Security Networks: A Guide to IEEE 802.11i. Accessed 6 April 2017:
[35](1, 2, 3, 4) IEEE 802.1x, Port Based Network Access Control. Accessed 6 April 2017:
[36](1, 2, 3, 4) IEEE 802.11, Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. Accessed 6 April 2017:
[37](1, 2, 3) NIST Federal Information Processing Standards (FIPS) 140-2, Security Requirements for Cryptographic Modules. Accessed 6 April 2017:
[38](1, 2) NIST SP 800-52 Rev 1, Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations. Accessed 6 April 2017:
[39]DHHS Office for Civil Rights, HIPAA Security Rule Crosswalk to NIST Cybersecurity Framework. Accessed 6 April 2017:
[40]IHE PCD User Handbook – 2011 Edition – Published 2011-08-12. Accessed 6 April 2017:
[41](1, 2, 3) Cisco Medical-Grade Network (MGN) 2.0-Wireless Architectures :
[42](1, 2, 3) FDA, Radio Frequency Wireless Technology in Medical Devices – Guidance for Industry and Food and Drug Administration Staff, Document issued on August 12, 2013. Accessed 6 April 2017:
[43](1, 2, 3) NIST SP 800-114, User’s Guide to Securing External Devices for Telework and Remote Access. Accessed 6 April 2017:
[44](1, 2, 3, 4) NIST SP 800-77, Guide to IPsec VPNs. Accessed 6 April 2017:
[45](1, 2) NIST SP 800-41 Rev 1, Guidelines on Firewalls and Firewall Policy. Accessed 6 April 2017:
[46](1, 2, 3) IEEE 802.1x, Port Based Network Access Control. Accessed 6 April 2017:
[47](1, 2, 3) IEEE 802.3, IEEE Standard for Ethernet. Accessed 6 April 2017:
[48](1, 2) IEEE 802.1Q, Bridges and Bridged Networks. Accessed 6 April 2017:
[49](1, 2, 3) Internet Engineering Task Force (IETF) Request for Comments (RFC) 4301, Security Architecture for the Internet Protocol. Accessed 6 April 2017:
[50](1, 2) NIST FIPS 197, Advanced Encryption Standard (AES). Accessed 6 April 2017:
[51](1, 2) NIST SP 800-46 Rev 1, Guide to Enterprise Telework and Remote Access Security. Accessed 6 April 2017:
[52](1, 2) NIST SP 800-41 Rev 1, Guidelines on Firewalls and Firewall Policy. Accessed 6 April 2017:
[53]NIST SP 800-95, Guide to Secure Web Services. Accessed 6 April 2017:
[54]NIST SP 1800-5A, IT Asset Management. Accessed 10 April 2017:
[56]Manufacturer Disclosure Statement for Medical Device Security (MDS2)