[Part 3] Medical Device Security Program Development
Discover how healthcare organizations can build a robust medical device security program. Learn key recommendations from CynergisTek to identify risks, implement controls, and protect connected medical devices across your enterprise.
Listening to the third and final webinar of the Minnesota HIMSS webinar series, Medical Device Security Overview for Healthcare Delivery Organizations with speakers Matt Dimino and Carrie Whysall from CynergisTek, I found the following useful tips when developing a medical device security program.
Medical Device Security
Medical devices are difficult to secure on a technical level. They are expensive and their operating systems typically stay the same while in service. These devices are not easily remotely managed, may not be able to be encrypted, and have default user passwords.
IoMT Security Components
To develop a thorough security program you should plan it in three stages:
Assist with medical device procurement and decommissioning
Provide IoMT device training and awareness
Manage continuing vulnerability reporting and remediation programs
Device Risk
When trying to secure your medical devices you should be looking at all of the risk areas. Security vulnerabilities pose a threat (opens in a new tab) to patient safety, medical device availability, and could result in financial loss or unauthorized access to information.
How to Analyze Risk
Risk analysis should follow these steps:
System characterization: Gather data on hardware & software
Threat identification: Look at the full spectrum of possible threats
Vulnerability analysis: Ask how do vulnerabilities impact devices and protocols
Controls analysis: Look at controls already in place and what is needed
Likelihood determination: Ask what are the chances of a device being compromised
Impact analysis: Ask how a compromised asset would affect the organization
Risk determination: Ask what risk level a device should be placed in
Controls recommendation: Determine what controls assets need to mitigate vulnerabilities
Results documentation: Share information and communicate with stakeholders
Risk categorization aids in risk prioritization and remediation. You can categorize risks through device threat modeling: collecting device data, establishing a hypothesis, threat hunting, threat detection, and threat response.
Governance
It takes a team to create and manage a medical device security program. Setting a purpose and objective for this committee is key. The Responsible Accountable Consulted Informed (RACI) Matrix can help organize stakeholders and ensure everyone is aware of their role and responsibilities.
How ORDR Can Help
Developing a medical device security program can be a difficult and lengthy process. ORDR can help.
The ORDR System Control Engine (SCE) gives organizations the power to enable visibility and security of their network-connected devices, with a simple and powerful solution to identify, classify, profile the behavior and risk and automate action for every network-connected device in the enterprise.