<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: 11 Things the Health Care Sector Must Do to Improve Cybersecurity</title>
	<atom:link href="http://www.epanorama.net/blog/2017/06/04/11-things-the-health-care-sector-must-do-to-improve-cybersecurity/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2017/06/04/11-things-the-health-care-sector-must-do-to-improve-cybersecurity/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Sun, 12 Apr 2026 21:37:09 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2017/06/04/11-things-the-health-care-sector-must-do-to-improve-cybersecurity/comment-page-1/#comment-1568322</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Fri, 27 Oct 2017 13:44:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=56073#comment-1568322</guid>
		<description><![CDATA[UK Blames North Korea for Cyberattack That Crippled Hospitals
http://www.securityweek.com/uk-blames-north-korea-cyberattack-crippled-hospitals

Britain on Friday blamed North Korea for a ransomware attack this year that a new report revealed affected a third of English hospitals and could have been prevented with &quot;basic&quot; IT security.

&quot;This attack, we believe quite strongly that it came from a foreign state,&quot; Ben Wallace, a junior minister for security, told BBC Radio 4&#039;s Today programme.

&quot;North Korea was the state that we believe was involved in this worldwide attack,&quot; he said, adding that the government was &quot;as sure as possible&quot;.

The WannaCry attack in May infected some 300,000 computers in 150 countries, including in Britain&#039;s National Health Service (NHS), Spanish telecoms company Telefonica and US logistics company FedEx. 

 Britain&#039;s National Audit Office revealed the attack had hit NHS England particularly hard, forcing the cancellation of some 19,500 medical appointments.

Computers at 81 hospital groups across England were affected -- a third of the total number of 236.

Some 600 general practitioners were also affected.]]></description>
		<content:encoded><![CDATA[<p>UK Blames North Korea for Cyberattack That Crippled Hospitals<br />
<a href="http://www.securityweek.com/uk-blames-north-korea-cyberattack-crippled-hospitals" rel="nofollow">http://www.securityweek.com/uk-blames-north-korea-cyberattack-crippled-hospitals</a></p>
<p>Britain on Friday blamed North Korea for a ransomware attack this year that a new report revealed affected a third of English hospitals and could have been prevented with &#8220;basic&#8221; IT security.</p>
<p>&#8220;This attack, we believe quite strongly that it came from a foreign state,&#8221; Ben Wallace, a junior minister for security, told BBC Radio 4&#8242;s Today programme.</p>
<p>&#8220;North Korea was the state that we believe was involved in this worldwide attack,&#8221; he said, adding that the government was &#8220;as sure as possible&#8221;.</p>
<p>The WannaCry attack in May infected some 300,000 computers in 150 countries, including in Britain&#8217;s National Health Service (NHS), Spanish telecoms company Telefonica and US logistics company FedEx. </p>
<p> Britain&#8217;s National Audit Office revealed the attack had hit NHS England particularly hard, forcing the cancellation of some 19,500 medical appointments.</p>
<p>Computers at 81 hospital groups across England were affected &#8212; a third of the total number of 236.</p>
<p>Some 600 general practitioners were also affected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2017/06/04/11-things-the-health-care-sector-must-do-to-improve-cybersecurity/comment-page-1/#comment-1549683</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Mon, 05 Jun 2017 09:16:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=56073#comment-1549683</guid>
		<description><![CDATA[Several Hospira Drug Pumps Use Vulnerable Software: Researcher
http://www.securityweek.com/several-hospira-drug-pumps-use-vulnerable-software-researcher

A researcher who has analyzed the software installed on infusion pumps manufactured by Hospira says several models are plagued by the vulnerabilities disclosed earlier this year.]]></description>
		<content:encoded><![CDATA[<p>Several Hospira Drug Pumps Use Vulnerable Software: Researcher<br />
<a href="http://www.securityweek.com/several-hospira-drug-pumps-use-vulnerable-software-researcher" rel="nofollow">http://www.securityweek.com/several-hospira-drug-pumps-use-vulnerable-software-researcher</a></p>
<p>A researcher who has analyzed the software installed on infusion pumps manufactured by Hospira says several models are plagued by the vulnerabilities disclosed earlier this year.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2017/06/04/11-things-the-health-care-sector-must-do-to-improve-cybersecurity/comment-page-1/#comment-1549682</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Mon, 05 Jun 2017 09:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=56073#comment-1549682</guid>
		<description><![CDATA[Sobering Thoughts When a Connected Medical Device Is Connected to You
http://www.securityweek.com/sobering-thoughts-when-connected-medical-device-connected-you]]></description>
		<content:encoded><![CDATA[<p>Sobering Thoughts When a Connected Medical Device Is Connected to You<br />
<a href="http://www.securityweek.com/sobering-thoughts-when-connected-medical-device-connected-you" rel="nofollow">http://www.securityweek.com/sobering-thoughts-when-connected-medical-device-connected-you</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2017/06/04/11-things-the-health-care-sector-must-do-to-improve-cybersecurity/comment-page-1/#comment-1549681</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Mon, 05 Jun 2017 09:15:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=56073#comment-1549681</guid>
		<description><![CDATA[A Fact Check on Medical Device Security
http://www.securityweek.com/fact-check-medical-device-security

Worrisome Chicken Little or savvy observer of truth?

This may have been your question while reading my previous article about the security of connected medical devices, “Sobering Thoughts When a Connected Medical Device Is Connected to You.” Did laying in a hospital bed, connected to an infusion pump like the one used by security researchers to demonstrate how breaching such a device could be used to administer a fatal dose of medicine, create unnecessary angst? Or, did it draw the facts into clear focus?

Medical device network vulnerability

Now let’s consider the network vulnerability of hospitals and other medical providers using that favorably timed news I mentioned. On Friday, May 12th, the WannaCry ransomware attack infected more than 230,000 computers in over 150 countries. The attack used two components: a propagation routine and a module used to perform extortion activities. The worm leveraged a Windows Server Message Block (SMB) vulnerability. This is a well-known attack tradecraft.

An industry unprepared to defend

We now have proof of network vulnerability and an actual documented attack in hand. Two points for the savvy observer. Thus, leaving the actual vulnerability of the medical devices in question. In May 2017, the Ponemon Institute issued a report (PDF) titled “Medical Device Security: An Industry Under Attack and Unprepared to Defend,” addressing this very subject. In the interest of full disclosure, the report was sponsored by Synopsys, my employer. 

Some highlights include:

 •  67 percent of medical device manufacturers and 56 percent of HDOs believe an attack on a medical device built or in use by their organization is likely to occur over the next 12 months.

 • 80 percent of device makers and HDOs report that medical devices are very difficult to secure. The top reasons cited include lack of knowledge/training on secure coding practices and pressure on development teams to meet product deadlines.

 • Only 9 percent of manufacturers and 5 percent of HDOs say they test medical devices at least once a year. Meanwhile, 53 percent of HDOs and 43 percent of manufacturers do not test devices at all. 

The most compelling evidence for my case is that the report cites that “38 percent of respondents in HDOs say they are aware of inappropriate therapy/treatment delivered to the patient because of an insecure medical device and 39 percent of device makers confirm that attackers have taken control of medical devices.” 

https://www.synopsys.com/content/dam/synopsys/sig-assets/reports/medical-device-security-ponemon-synopsys.pdf]]></description>
		<content:encoded><![CDATA[<p>A Fact Check on Medical Device Security<br />
<a href="http://www.securityweek.com/fact-check-medical-device-security" rel="nofollow">http://www.securityweek.com/fact-check-medical-device-security</a></p>
<p>Worrisome Chicken Little or savvy observer of truth?</p>
<p>This may have been your question while reading my previous article about the security of connected medical devices, “Sobering Thoughts When a Connected Medical Device Is Connected to You.” Did laying in a hospital bed, connected to an infusion pump like the one used by security researchers to demonstrate how breaching such a device could be used to administer a fatal dose of medicine, create unnecessary angst? Or, did it draw the facts into clear focus?</p>
<p>Medical device network vulnerability</p>
<p>Now let’s consider the network vulnerability of hospitals and other medical providers using that favorably timed news I mentioned. On Friday, May 12th, the WannaCry ransomware attack infected more than 230,000 computers in over 150 countries. The attack used two components: a propagation routine and a module used to perform extortion activities. The worm leveraged a Windows Server Message Block (SMB) vulnerability. This is a well-known attack tradecraft.</p>
<p>An industry unprepared to defend</p>
<p>We now have proof of network vulnerability and an actual documented attack in hand. Two points for the savvy observer. Thus, leaving the actual vulnerability of the medical devices in question. In May 2017, the Ponemon Institute issued a report (PDF) titled “Medical Device Security: An Industry Under Attack and Unprepared to Defend,” addressing this very subject. In the interest of full disclosure, the report was sponsored by Synopsys, my employer. </p>
<p>Some highlights include:</p>
<p> •  67 percent of medical device manufacturers and 56 percent of HDOs believe an attack on a medical device built or in use by their organization is likely to occur over the next 12 months.</p>
<p> • 80 percent of device makers and HDOs report that medical devices are very difficult to secure. The top reasons cited include lack of knowledge/training on secure coding practices and pressure on development teams to meet product deadlines.</p>
<p> • Only 9 percent of manufacturers and 5 percent of HDOs say they test medical devices at least once a year. Meanwhile, 53 percent of HDOs and 43 percent of manufacturers do not test devices at all. </p>
<p>The most compelling evidence for my case is that the report cites that “38 percent of respondents in HDOs say they are aware of inappropriate therapy/treatment delivered to the patient because of an insecure medical device and 39 percent of device makers confirm that attackers have taken control of medical devices.” </p>
<p><a href="https://www.synopsys.com/content/dam/synopsys/sig-assets/reports/medical-device-security-ponemon-synopsys.pdf" rel="nofollow">https://www.synopsys.com/content/dam/synopsys/sig-assets/reports/medical-device-security-ponemon-synopsys.pdf</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
