Risk
9/30/2013
01:01 PM
50%
50%

Medical Device Security: A Work In Progress

Healthcare organizations vary widely in how prepared they are to handle breaches of medical devices, says Deloitte report.

Healthcare Robotics: Patently Incredible Inventions
Healthcare Robotics: Patently Incredible Inventions
(click image for larger view)
Healthcare organizations are in various stages of mitigating the cybersecurity risks of medical devices such as patient monitors, infusion pumps, ventilators, pacemakers and imaging devices, a new Deloitte report says. Overall, however, Deloitte's interviews with medical device security leaders at nine large hospital systems indicate that their organizations have a long way to go and that they'll need more cooperation from device manufacturers.

Last June, the Food and Drug Administration (FDA) released a guidance on the "content of premarket submissions for management of cybersecurity in medical devices." This guidance suggested that device makers incorporate security features into their products to limit access to only trusted users, determine trusted content, and use fail-safe and recovery devices. FDA called on the manufacturers to consider threats such as hacking, malware and other vulnerabilities of device software and to work with providers on use cases.

"The cybersecurity guidance has definitely gotten the attention of some of the manufacturers," said Russell Jones, a report author and a partner in Deloitte's life sciences and healthcare division, in an interview. "The FDA has made it clear, with the guidance and the additional communications they've published, that this is an area of importance."

However, he told InformationWeek Healthcare, many device makers are still not ready to include these security features in their purchasing agreements with healthcare providers. Although providers and manufacturers have begun collaborating on this issue, he said, they have a long way to go.

[ Are apps the answer to doctors' hectic schedules? Read Healthcare Apps Could Be Doctor's Best Friend. ]

Also, the Deloitte report noted, healthcare organizations have had difficulty in developing risk-mitigation strategies for devices that are more than five years old and run on proprietary operating systems. "These legacy devices are difficult to test for vulnerabilities because off-the-shelf security scanning tools do not exist," the paper said. In cases where hospitals lack spare devices of the same kind, these products can't even be taken offline for testing, Jones added.

Other devices that run on "well known commercial operating systems" have the same vulnerabilities as other types of systems connected to a network, the report said.

For both these and the legacy devices, the most extreme risk mitigation method is to quarantine the medical devices from the rest of the hospital IT system. But, partly because of the complexity of running multiple systems that aren't networked, Deloitte suggested that organizations do this only where it's appropriate.

"We recommend that organizations consider quarantining, and if it doesn't make sense, fall back to other types of controls, such as detection controls and sim systems," Jone said. "That may be the best you can do to see whether there has been activity that suggests hacking or unauthorized access to medical devices."

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
anon2450048136
50%
50%
anon2450048136,
User Rank: Apprentice
1/12/2015 | 5:13:45 AM
re: medical device security
go and read here on schneier.com
MarciaNWC
100%
0%
MarciaNWC,
User Rank: Apprentice
11/17/2013 | 7:06:57 PM
re: medical device security
Even though the threat level is low right now, it's incumbent on medical device makers to step up on security, and for health care providers to require security in their purchasing agreements. It doesn't take long for attackers to exploit vulnerabilities.
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6501
Published: 2015-03-30
The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_s...

CVE-2014-9652
Published: 2015-03-30
The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote atta...

CVE-2014-9653
Published: 2015-03-30
readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available data, which allows remote attackers to cause a denial of service (uninitialized memory ...

CVE-2014-9705
Published: 2015-03-30
Heap-based buffer overflow in the enchant_broker_request_dict function in ext/enchant/enchant.c in PHP before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6 allows remote attackers to execute arbitrary code via vectors that trigger creation of multiple dictionaries.

CVE-2014-9709
Published: 2015-03-30
The GetCode_ function in gd_gif_in.c in GD 2.1.1 and earlier, as used in PHP before 5.5.21 and 5.6.x before 5.6.5, allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted GIF image that is improperly handled by the gdImageCreateFromGif function.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.