IoT
1/20/2016
04:30 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Medical Device Security Gets Intensive Care

FDA draft cybersecurity guidance for medical device-makers and a new 'Hippocratic Oath' for the industry debut amid growing concerns of patient safety.

The heat is officially on medical device manufacturers and healthcare organizations to better secure and protect patient care equipment and systems from cyber attacks with new proposed best practices from the Food & Drug Administration (FDA) and proposals from a grassroots security industry group.

The FDA, late last week, issued draft guidelines for medical device makers that call for cyber threat intelligence-sharing via Information Sharing Analysis Organizations and ISACs, vulnerability disclosure and remediation programs, as well as other security best practices. Meanwhile, the I Am The Cavalry group, yesterday, published the "Hippocratic Oath for Connected Medical Devices," which aims to make medical device makers secure their equipment and healthcare providers to ensure they purchase secure equipment and secure it accordingly.

"Better patient care is the goal for everyone" here, says Beau Woods of I Am The Cavalry, whose Hippocratic Oath riffs off the traditional physician's oath to put patient care and safety first. "There are cyber-safety side effects … The Hippocratic Oath for medical devices attempts to join the ethics of care providers to deliver care in the best interest of the patient with methods and practices of cybersecurity."

Both documents were among the hot topics at the FDA's public workshop today on collaborative approaches to cybersecurity in medical devices.

Michael Murray, director of product development security for GE Healthcare, says healthcare is part of critical infrastructure and therefore requires requisite security protections. "From the presidential Executive Order around critical infrastructure protection [and] all the way to grassroots efforts like I Am The Cavalry, industry has realized the importance of security protections for critical infrastructure," says Murray, who is attending the FDA workshop in Washington, DC.

"Healthcare is no different: in fact, Suzanne Schwartz [of the FDA] pointed out in her opening comments that healthcare is the 'largest attack surface for critical infrastructure,'" Murray says.

The FDA's new draft guidelines call for medical device manufacturers to monitor and fix vulnerabilities and security problems in their products, according to Schwartz. "All medical devices that use software and are connected to hospital and health care organizations’ networks have vulnerabilities—some we can proactively protect against, while others require vigilant monitoring and timely remediation," Suzanne Schwartz, associate director for science and strategic partnerships and acting director of emergency preparedness/operations and medical countermeasures in the FDA’s Center for Devices and Radiological Health, said in a statement.

Security researchers for years now have been uncovering security flaws in medical devices such as insulin pumps, raising concerns of tampering and potential physical threats to patients. The latest draft recommendations for medical device-makers isn't the FDA's first foray into this space: in the fall of 2104, the agency issued recommendations to manufacturers about considering cybersecurity in the design of their products and submitting plans for patching and updating those systems. The agency in 2013 warned of the dangers of cyberattacks on medical equipment.

The FDA's draft guidance, which is open for public comment for the next 90 days, is all about proactive planning and assessment of vulnerabilities. Risk management is a key piece of the puzzle, and timely response to vulnerabilities that are reported in these products. The FDA cites the NIST Framework for Improving Critical Infrastructure Cybersecurity as a key component, as well as monitoring and testing for flaws and risk; setting up a vulnerability disclosure policy and program; and deploying mitigations, for example.

[How some white hat hackers are changing career paths to help fix security weaknesses in consumer devices and business systems. Read Hiring Hackers To Secure The Internet Of Things.]

"The guidance is aimed at how manufacturers are supposed to handle vulnerabilities in products that are already in the market," GE's Murray says. "The focus is on how manufacturers assess those vulnerabilities and respond to them, as well as their coordination along those lines with the FDA."

I Am The Cavalry's Woods applauds the FDA's guidelines, which he says encompasses the lifecycle of the products, starting with the design phase. "The first thing that stood out for me are the incentive structures" for building security into medical device manufacturers' processes and products, he says.

For instance, the FDA doesn't require manufacturers to report in advance to the agency each and every bug that's discovered in their products; "routine updates or patches" are exempt from that. "For a small subset of cybersecurity vulnerabilities and exploits that may compromise the essential clinical performance of a device and present a reasonable probability of serious adverse health consequences or death, the FDA would require medical device manufacturers to notify the Agency," the recommendations say.

I Am The Cavalry's recommendations, meanwhile, are similar to the five-star cybersecurity safety recommendations that I Am The Cavalry devised for automakers to protect cars from hacking. They include cyber safety by design; third-party collaboration for vulnerability reporting; forensics and analysis from incidents; resilience and containment of devices; and efficient and timely security updates.

"I think that all of the efforts to get security people, medical device manufacturers and healthcare payers/providers in the same room talking about how to work together to improve the security of the healthcare ecosystem is a positive development," Murray says.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
SecurityFool
50%
50%
SecurityFool,
User Rank: Apprentice
8/8/2016 | 12:00:39 PM
Ransomware
And what of Ransomware?

 

Today ransomeware is one of the most profitable endeavors in the hacking arena. When hackers figure out that they can hack into a medical device and essentially hold someone hostage on their life, how quick do you think they will pay?

Or hacks into a system and causes medical practitioners to be unable to provide critical care? Who gets hit with the malpractice suit if the doctor cannot get accurate imaging results or cannot use a crash cart because it is compromised?

 

I see a lot of scary stuff if this industry doesn't take this serios. Banks didn't take protecting their devices serious enough for a while there, and they are paying ransoms repeatedly. When you have a small population of technically proficient hackers in countries where it isn't illegal to demand a ransome, how can we even go get the bad guys? It is a tough situation, and until governments declare hacking a form of terrorism or at minimum criminal activity, healthcare organizations need to be protecting themselves from the bad guys.

At a minimum, have a security plan in place so that the easily deterred hackers are motivated to turn their efforts to easier targets.

 
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
1/28/2016 | 12:32:46 PM
Re: Showtime, anyone?
@Christian: You can at least feel better about the fact that cars are far safer than they were decades ago.  There are some interesting (if, at times, hard to watch) videos out there of crash tests -- replete with crash-test dummies -- involving head-on collisions between a new car and a car from, say, the '60s.  The difference between the damage the cars (and car drivers/passengers) take is astounding.
Christian Bryant
50%
50%
Christian Bryant,
User Rank: Ninja
1/28/2016 | 11:26:25 AM
Re: Showtime, anyone?
You said it, Joe!  It's sad, of course.  Especially as a father, I have serious reservations about the automobile industry and how far each model is tested before making it to the car lot; add computers to the complexity of safety research and testing, and the sweat begins to pour...
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
1/26/2016 | 11:20:35 AM
Re: Showtime, anyone?
To be fair, the automobile has long been depicted as a "careening comet of death."  One need merely watch driving ed videos from the '50s and '60s to know that.  ;)
Christian Bryant
50%
50%
Christian Bryant,
User Rank: Ninja
1/26/2016 | 2:46:53 AM
Re: Showtime, anyone?
As we've seen with the auto industry, hack after hack has painted a new picture of the automobile, switching the view from vehicle of leisure and labor to a careening comet of death.  Being locked in a car hurtling across a highway invokes claustrophobic feelings; imagine those emotions felt when you are the vehicle and the hack is occurring inside you.  

Yes, it's time for sure to get the right white hats working on every known hackable medical device and for patches and new designs to emerge from the rubble.  Perhaps we'll also see some major revision ideas around ISO/IEEE 11073 - Health informatics - Medical / health device communication standards.    
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
1/25/2016 | 9:11:19 PM
Re: Showtime, anyone?
Well, it would likely be a very different type of attacker altogether that went after pacemakers. 

 
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
1/25/2016 | 6:57:41 PM
Re: Showtime, anyone?
> But the good news--as with much of the IoT and connected consumer device space--the good guys have been ahead of the bad guys so far.

Is this truly correct and apt, though?

It seems to me that the bad guys have determined that, from a long-term view, there simply isn't as much profit to be had in hacking pacemakers to kill people and whatnot as there is in simply hacking healthcare companies to steal PHI.
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
1/25/2016 | 8:08:45 AM
Re: Showtime, anyone?
It's definitely something that's been on the radar for some time, for sure. But the good news--as with much of the IoT and connected consumer device space--the good guys have been ahead of the bad guys so far. Even so, the good guys need to keep the momentum and take action.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
1/23/2016 | 12:45:07 PM
Showtime, anyone?
I think Homeland deserves a little credit for this -- highlighting how pacemakers can be hacked to kill patients!

(And, of course, years before, then-VP Dick Cheney's pacemaker was adjusted to take it offline and make it unhackable -- to prevent exactly that kind of situation.)
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Five Emerging Security Threats - And What You Can Learn From Them
At Black Hat USA, researchers unveiled some nasty vulnerabilities. Is your organization ready?
Flash Poll
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-7445
Published: 2015-10-15
The Direct Rendering Manager (DRM) subsystem in the Linux kernel through 4.x mishandles requests for Graphics Execution Manager (GEM) objects, which allows context-dependent attackers to cause a denial of service (memory consumption) via an application that processes graphics data, as demonstrated b...

CVE-2015-4948
Published: 2015-10-15
netstat in IBM AIX 5.3, 6.1, and 7.1 and VIOS 2.2.x, when a fibre channel adapter is used, allows local users to gain privileges via unspecified vectors.

CVE-2015-5660
Published: 2015-10-15
Cross-site request forgery (CSRF) vulnerability in eXtplorer before 2.1.8 allows remote attackers to hijack the authentication of arbitrary users for requests that execute PHP code.

CVE-2015-6003
Published: 2015-10-15
Directory traversal vulnerability in QNAP QTS before 4.1.4 build 0910 and 4.2.x before 4.2.0 RC2 build 0910, when AFP is enabled, allows remote attackers to read or write to arbitrary files by leveraging access to an OS X (1) user or (2) guest account.

CVE-2015-6333
Published: 2015-10-15
Cisco Application Policy Infrastructure Controller (APIC) 1.1j allows local users to gain privileges via vectors involving addition of an SSH key, aka Bug ID CSCuw46076.

Dark Reading Radio
Archived Dark Reading Radio
Join Dark Reading community editor Marilyn Cohodas and her guest, David Shearer, (ISC)2 Chief Executive Officer, as they discuss issues that keep IT security professionals up at night, including results from the recent 2016 Black Hat Attendee Survey.