Healthcare CERTs highlight the need for security guidance for specific sectors

Posted by   Martijn Grooten on   Jan 24, 2018

In February 2016, a US hospital saw a heart operation interrupted by the rebooting of a monitoring PC, caused by anti-virus software running on the machine. The report filed makes it clear that this was a case of someone not following the product recommendations, but the incident does highlight an important point: what is a sensible policy for many, won't work for all.

There is ample advice available on what to do to make your devices and your networks more secure, and how to respond to new malware outbreaks or newly discovered vulnerabilities. However, such advice rarely takes into account either the unique threat models or the unique requirements of specific sectors.

Though certainly not the only sector with its own specific needs, healthcare is a good example of why generic advice often doesn't apply. Medical software and equipment is typically supposed to last well beyond standard replacement cycles. Even buying new desktop PCs with more modern operating systems is, in times of squeezed budgets, often not politically possible, no matter how necessary such upgrades may be. At the same time, a failing digital device could literally be fatal (even if the cited example didn't cause any physical harm to the patient).

This is why I was pleased to learn about the recent launch of Z-CERT, a computer emergency response team focused on the Dutch healthcare sector ('Z' comes from 'zorg', Dutch for care), following the example of similar organisations that exist in Norway and the UK. CERTs are common in other sectors, such as banking and industrial control systems, where they do a good job of giving specific advice. They are also in a position to help security researchers responsibly disclose vulnerabilities in software and hardware used in these sectors.

zcert-logo.png
Anyone who has listened to Jelena Milosevic's inside view of the state of digital security in the healthcare sector (which she presented at VB2017) will understand that there is a lot of room for improvement. Initiatives such as this give me confidence that we are at least on the right track.

jelenamilosevic_vb2017.png

Jelena Milosevic, a nurse with a passion for IT security, shared her experiences of security in the healthcare sector at VB2017.

twitter.png
fb.png
linkedin.png
hackernews.png
reddit.png

 

Latest posts:

VB2018 paper: From Hacking Team to hacked team to…?

Today we publish the VB2018 paper and video by ESET researcher Filip Kafka, who looked at the new malware by Hacking Team, after the company had recovered from the 2015 breach.

The spam that is hardest to block is often the most damaging

We see a lot of spam in the VBSpam test lab, and we also see how well such emails are being blocked by email security products. Worryingly, it is often the emails with a malicious attachment or a phishing link that are most likely to be missed.

Throwback Thursday: We're all doomed

Mydoom turns 15 this month, and is still being seen in email attachments. This Throwback Thursday we look back to March 2004, when Gabor Szappanos tracked the rise of W32/Mydoom.

VB2019 call for papers - now open!

Have you analysed a new online threat? Do you know a new way to defend against such threats? Are you tasked with securing systems and fending off attacks? The call for papers for VB2019 is now open and we want to hear from you!

VB2018 paper: Unpacking the packed unpacker: reversing an Android anti-analysis library

Today, we publish a VB2018 paper by Google researcher Maddie Stone in which she looks at one of the most interesting anti-analysis native libraries in the Android ecosystem. We also release the recording of Maddie's presentation.

We have placed cookies on your device in order to improve the functionality of this site, as outlined in our cookies policy. However, you may delete and block all cookies from this site and your use of the site will be unaffected. By continuing to browse this site, you are agreeing to Virus Bulletin's use of data as outlined in our privacy policy.