<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Insider Fraud Spotlight &#187; Ponemon</title>
	<atom:link href="http://www.attachmate.com/blogs/insider-fraud-spotlight/index.php/tag/ponemon/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.attachmate.com/blogs/insider-fraud-spotlight</link>
	<description>Attachmate Luminet</description>
	<lastBuildDate>Mon, 05 Aug 2013 19:58:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Medical Identity Theft&#8211;The Next Big Thing?</title>
		<link>http://www.attachmate.com/blogs/insider-fraud-spotlight/index.php/healthcare/medical-identity-theft-the-next-big-thing/</link>
		<comments>http://www.attachmate.com/blogs/insider-fraud-spotlight/index.php/healthcare/medical-identity-theft-the-next-big-thing/#comments</comments>
		<pubDate>Tue, 08 Nov 2011 14:08:14 +0000</pubDate>
		<dc:creator>Christine Meyers</dc:creator>
				<category><![CDATA[Healthcare Fraud]]></category>
		<category><![CDATA[enterprise fraud]]></category>
		<category><![CDATA[ePHI]]></category>
		<category><![CDATA[healthcare]]></category>
		<category><![CDATA[HIPAA]]></category>
		<category><![CDATA[insider fraud]]></category>
		<category><![CDATA[medical identity theft]]></category>
		<category><![CDATA[patient privacy]]></category>
		<category><![CDATA[Ponemon]]></category>
		<category><![CDATA[privacy]]></category>

		<guid isPermaLink="false">http://www.attachmate.com/blogs/insider-fraud-spotlight/?p=78</guid>
		<description><![CDATA[&#160; I was speaking with a friend the other day about Medical Identity Theft, HIPAA compliance and enterprise fraud management. We were discussing a survey report published in March by the Ponemon Institute that found roughly 1.5 million Americans are victims of medical ID theft. In the survey, fourteen percent of respondents said the breach [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>&nbsp;</p>
<p>I was speaking with a friend the other day about Medical Identity Theft, <a title="HIPAA compliance and enterprise fraud management" href="http://www.attachmate.com/solutions/managing-enterprise-fraud/industry/healthcare.htm">HIPAA compliance and enterprise fraud management</a>. We were discussing a survey report published in March by the Ponemon Institute that found roughly 1.5 million Americans are victims of medical ID theft. In the survey, fourteen percent of respondents said the breach occurred at a health care office, and 10% said employees at a health care organization&#8217;s office had stolen the data.</p>
<p> It occurred to me that medical identity theft is one of those “wild west” opportunities for identity thieves at the moment. While everyone is pretty familiar with the concept of financial fraud and what happens when your credit card information is stolen, what happens when someone pretends to be you to access medical care can have far more devastating consequences.</p>
<p>According to the Federal Bureau of Consumer Protection, here are some indications that might indicate that someone has been a victim of medical identity theft. Victims may:</p>
<ul>
<li>get a bill for medical services they didn’t receive;</li>
<li>be contacted by a debt collector about medical debt they don’t owe;</li>
<li>see medical collection notices on their credit report that they don’t recognize;</li>
<li>be told by their health plan that they’ve reached their limit on benefits; or</li>
<li>be denied insurance because their medical records show a condition they don’t have.</li>
</ul>
<p>Source: <a href="http://business.ftc.gov/documents/bus75-medical-identity-theft-faq-health-care-health-plan">http://business.ftc.gov/documents/bus75-medical-identity-theft-faq-health-care-health-plan</a></p>
<p>Whoa—think about that for a moment. Those are significant impacts. Then, spin the scenario out a bit further. What happens if medical records become co-mingled at the provider level? Can you get to a point where the records of the thief are entered into the medical history of the victim? According to the experts, you can. Back in 2006, Pam Dixon, founder of the World Privacy Forum, referenced the challenges that medical identity theft can create and cited examples of misinformation appearing in patient files. She also stated that changes to patient records could remain in the files for many years.</p>
<p><strong>Providers Protecting Privacy as Part of Their Healthcare Brand</strong></p>
<p>Leading healthcare organizations are increasingly seeing ways to protect their brand while safeguarding patient privacy. Moving the privacy discussion beyond the HIPAA disclosure form that all of us sign when accessing care and making ePHI protection a differentiator demonstrates a commitment on the part of the provider. When given a choice, my healthcare dollars are spent with those institutions that care enough about me to protect my personal information. It just makes sense to require the same level of accountability from my doctor as I do from my bank—the risks are just as real and the opportunity for damage may even be greater.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.attachmate.com/blogs/insider-fraud-spotlight/index.php/healthcare/medical-identity-theft-the-next-big-thing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Ponemon: Real Risks of Insider Threats Often Stay Hidden</title>
		<link>http://www.attachmate.com/blogs/insider-fraud-spotlight/index.php/insider-threat/insider-risk-is-real-and-often-stays-hidden-in-organizations-finds-new-ponemon-research/</link>
		<comments>http://www.attachmate.com/blogs/insider-fraud-spotlight/index.php/insider-threat/insider-risk-is-real-and-often-stays-hidden-in-organizations-finds-new-ponemon-research/#comments</comments>
		<pubDate>Tue, 18 Oct 2011 08:44:31 +0000</pubDate>
		<dc:creator>Christine Meyers</dc:creator>
				<category><![CDATA[Insider Threat]]></category>
		<category><![CDATA[Analytics]]></category>
		<category><![CDATA[enterprise fraud]]></category>
		<category><![CDATA[Fraud]]></category>
		<category><![CDATA[Insider Risk]]></category>
		<category><![CDATA[Ponemon]]></category>

		<guid isPermaLink="false">http://www.attachmate.com/blogs/insider-fraud-spotlight/?p=49</guid>
		<description><![CDATA[It’s easy to point fingers when another organization has an insider fraud incident. But information from the new Survey on the Risk of Insider Fraud by Attachmate Corporation and Ponemon Instituteshows that more organizations need to turn a scrutinizing eye toward their own risk. The survey encompassed more than 700 organizations and revealed some alarming [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>It’s easy to point fingers when another organization has an insider fraud incident. But information from the new Survey on the Risk of Insider Fraud by <a title="Attachmate Corporation" href="http://www.attachmate.com/">Attachmate Corporation</a> and <a title="www.ponemon.org" href="http://www.ponemon.org/" target="_blank">Ponemon Institute</a>shows that more organizations need to turn a scrutinizing eye toward their own risk.</p>
<p>The survey encompassed more than 700 organizations and revealed some alarming data security trends:</p>
<ul>
<li>More than 75 percent of the respondents indicated that privileged users within their own institutions had or were likely to turn off or alter application controls to change sensitive information – and then reset the controls to cover their tracks.</li>
<li>Eighty-one percent replied that individuals at their institutions either had used or were likely to use someone else’s credentials to gain elevated rights or bypass separation of duty controls.</li>
<li>On average, respondents noted that their organizations experienced more than one incident of employee-related fraud per week – about <a title="53 in a year’s time" href="http://www.attachmate.com/images/info/employee-fraud.jpg" target="_blank">53 in a year’s time</a>(infographic available). Twenty-four percent of respondents indicated that their organizations experienced more than 100 incidents in the past 12 months.</li>
<li>Once an incident has occurred, it takes organizations an average of 89 days to discover it and an additional 96 days to uncover the root cause and determine the consequences to the organization.</li>
<li>A majority of respondents – or 62 percent – were unable or unsure of their ability to assess the financial impact and true costs of fraud.</li>
<li>Approximately two-thirds of internal fraud investigations do not result in actionable evidence against the perpetrators, meaning a majority of the incidents go unpunished and leave organizations vulnerable to additional incidents.</li>
</ul>
<p>“This data demonstrates that employee actions across an enterprise are not visible,” said Larry Ponemon, chairman and founder of the Ponemon Institute. “While organizations may have policies in place that are meant to curtail insider fraud, what’s on paper doesn’t necessarily lead to compliance.”</p>
<p>In fact, 52 percent of respondents noted that they do not believe they have the appropriate technologies to prevent or quickly detect insider fraud, including employees’ misuse of IT resources. Traditionally, IT departments review log files to analyze employee activity. However, 78 percent of respondents believe the manual review of log files is an inadequate method for observing questionable or suspicious employee access and computing activities.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.attachmate.com/blogs/insider-fraud-spotlight/index.php/insider-threat/insider-risk-is-real-and-often-stays-hidden-in-organizations-finds-new-ponemon-research/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>