Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

6/20/2016
08:35 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Veterans Administration Adopts UL Security Certification Program For Medical Devices

Goal is to ensure network-connected medical devices purchased by the VA meet baseline security standards established by Underwriters Laboratories.

The US Department of Veterans Affairs will use a new program and a set of standards developed by Underwriters Laboratories (UL) to ensure that network-connectable medical devices and systems the VA procures meet baseline requirements for security.

The VA and UL this week entered into a Cooperative Research and Development Agreement Program (CRADA) to facilitate the process. Under the agreement, the VA’s office of information technology will use UL’s Cybersecurity Assurance Program (CAP) to establish testable cybersecurity requirements for network-enabled medical devices, data systems, and associated technologies.

The program is scheduled for completion in December and is designed to support improvements in patient safety and security at the VA.

UL CAP, which Underwriters Laboratories announced earlier this year, which uses a newly created set of standards for IoT and critical infrastructure vendors to use for assessing security vulnerably and weaknesses in their products. features a set of standards, collectively referred to as UL 2900, that lets organizations asses network connected products for software vulnerabilities, known malware, and other security issues. The program combines input from multiple stakeholders from the federal government, academia, and industry.

The White House Cybersecurity National Action Plan (CNAP) officially recognizes UL’s CAP as a way to test and certify the security readiness of Internet connected products used in critical infrastructure sectors such as energy, healthcare, critical manufacturing, and utilities.

The VA’s plans to use UL CAP to refine its pre-procurement product vetting process are significant. Security vulnerabilities in network-enabled medical devices pose a significant risk to patient safety and security. Researchers in the past have demonstrated how security flaws in wireless enabled insulin pumps, pacemakers and heart monitors, and other medical devices can be exploited to deadly effect. 

In one demonstration five years ago, a security researcher at Black Hat USA showed how an attacker could shut down an insulin pump remotely by taking advantage of a security flaw in the device. In another demonstration, a security researcher showed how a flaw in a wireless-enabled pacemaker could be exploited to deliver a lethal shock to the wearer of the device. Malware in medical devices can also cause issues with reliability and availability of medical devices.

Concerns over the issue prompted the US Food and Drug Administration to issue draft cybersecurity guidelines and best practices for medical device makers earlier this year.

“Medical devices are susceptible to cybersecurity attacks, creating both patient safety risks and disclosure risks for protected health information,” the UL and VA said in a joint statement this week. The agreement “will seek to address an existing gap in the marketplace for cybersecurity standards and practical certification approaches for connected medical devices.”

Anura Fernando, global principal engineer at UL, says the CRADA project will accelerate the sharing of medical device cybersecurity information.

“Disclosure of potential cybersecurity concerns can be a sensitive topic when dealing with relationships across the supply chain,” Fernando says. “The UL CAP certification process provides mechanisms for having a blend of both public disclosures that can help the problems be effectively managed with minimal risk of public exposure or exploitation.”

Related stories

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Florida Town Pays $600K to Ransomware Operators
Curtis Franklin Jr., Senior Editor at Dark Reading,  6/20/2019
Pledges to Not Pay Ransomware Hit Reality
Robert Lemos, Contributing Writer,  6/21/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12280
PUBLISHED: 2019-06-25
PC-Doctor Toolbox before 7.3 has an Uncontrolled Search Path Element.
CVE-2019-3961
PUBLISHED: 2019-06-25
Nessus versions 8.4.0 and earlier were found to contain a reflected XSS vulnerability due to improper validation of user-supplied input. An unauthenticated, remote attacker could potentially exploit this vulnerability via a specially crafted request to execute arbitrary script code in a users browse...
CVE-2019-9836
PUBLISHED: 2019-06-25
Secure Encrypted Virtualization (SEV) on Advanced Micro Devices (AMD) Platform Security Processor (PSP; aka AMD Secure Processor or AMD-SP) 0.17 build 11 and earlier has an insecure cryptographic implementation.
CVE-2019-6328
PUBLISHED: 2019-06-25
HP Support Assistant 8.7.50 and earlier allows a user to gain system privilege and allows unauthorized modification of directories or files. Note: A different vulnerability than CVE-2019-6329.
CVE-2019-6329
PUBLISHED: 2019-06-25
HP Support Assistant 8.7.50 and earlier allows a user to gain system privilege and allows unauthorized modification of directories or files. Note: A different vulnerability than CVE-2019-6328.