<?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: Medical firms losing data &#8211; Dude, where&#8217;s my teeth?</title>
	<atom:link href="http://infosecplace.com/blog/2007/02/20/medical-firms-losing-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://infosecplace.com/blog/2007/02/20/medical-firms-losing-data/</link>
	<description>Commentary on the State of Information Security</description>
	<lastBuildDate>Sun, 10 Jan 2010 16:13:08 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob Lewis</title>
		<link>http://infosecplace.com/blog/2007/02/20/medical-firms-losing-data/comment-page-1/#comment-12462</link>
		<dc:creator>Rob Lewis</dc:creator>
		<pubDate>Fri, 23 Feb 2007 21:18:51 +0000</pubDate>
		<guid isPermaLink="false">http://infosecplace.com/blog/2007/02/20/medical-firms-losing-data/#comment-12462</guid>
		<description>Any security efforts will only remove low hanging fruit anyway.

Why should health enterprises spend money on partial solutions? When there are solutions that address data access and not network access, then they should invest. Until then, it is probably a waste of money, because they will solve today&#039;s problem, but not tomorrow&#039;s.</description>
		<content:encoded><![CDATA[<p>Any security efforts will only remove low hanging fruit anyway.</p>
<p>Why should health enterprises spend money on partial solutions? When there are solutions that address data access and not network access, then they should invest. Until then, it is probably a waste of money, because they will solve today&#8217;s problem, but not tomorrow&#8217;s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: If This Is Why We Fight, Then PCI is Our Vietnam &#124; RiskAnalys.is</title>
		<link>http://infosecplace.com/blog/2007/02/20/medical-firms-losing-data/comment-page-1/#comment-12294</link>
		<dc:creator>If This Is Why We Fight, Then PCI is Our Vietnam &#124; RiskAnalys.is</dc:creator>
		<pubDate>Thu, 22 Feb 2007 13:10:15 +0000</pubDate>
		<guid isPermaLink="false">http://infosecplace.com/blog/2007/02/20/medical-firms-losing-data/#comment-12294</guid>
		<description>[...] great post by Michael Farnum at his blog, An Information Security Place, called &quot;Dude, Where&#8217;s My Teeth&quot; that discusses the lack of fines and judgments in the HIPAA space though [...]</description>
		<content:encoded><![CDATA[<p>[...] great post by Michael Farnum at his blog, An Information Security Place, called &quot;Dude, Where&#8217;s My Teeth&quot; that discusses the lack of fines and judgments in the HIPAA space though [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Malta Info Security</title>
		<link>http://infosecplace.com/blog/2007/02/20/medical-firms-losing-data/comment-page-1/#comment-12187</link>
		<dc:creator>Malta Info Security</dc:creator>
		<pubDate>Wed, 21 Feb 2007 12:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://infosecplace.com/blog/2007/02/20/medical-firms-losing-data/#comment-12187</guid>
		<description>&lt;strong&gt;Security and Priorities...&lt;/strong&gt;



When it comes to priorities, a lot of companies and
organizations still place security towards the end of the list. Many times the
right people cannot take the right decisions, while the wrong people go ahead
with decisions which affect the secu...</description>
		<content:encoded><![CDATA[<p><strong>Security and Priorities&#8230;</strong></p>
<p>When it comes to priorities, a lot of companies and<br />
organizations still place security towards the end of the list. Many times the<br />
right people cannot take the right decisions, while the wrong people go ahead<br />
with decisions which affect the secu&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
