<?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>Data Breach Resolution &#187; pluehr</title>
	<atom:link href="http://www.experian.com/blogs/data-breach/author/pluehr/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.experian.com/blogs/data-breach</link>
	<description>Tools to help you navigate privacy, compliance, and security issues that may result in a data breach.</description>
	<lastBuildDate>Thu, 03 Jan 2013 19:44:41 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
		<item>
		<title>Data breaches – to prepare or not to prepare? The answer is simple.</title>
		<link>http://www.experian.com/blogs/data-breach/2011/05/17/data-breaches-%e2%80%93-to-prepare-or-not-to-prepare-the-answer-is-simple/</link>
		<comments>http://www.experian.com/blogs/data-breach/2011/05/17/data-breaches-%e2%80%93-to-prepare-or-not-to-prepare-the-answer-is-simple/#comments</comments>
		<pubDate>Tue, 17 May 2011 16:00:22 +0000</pubDate>
		<dc:creator>pluehr</dc:creator>
				<category><![CDATA[Breach Notification]]></category>
		<category><![CDATA[Breach Prevention]]></category>
		<category><![CDATA[Fraud Resolution]]></category>
		<category><![CDATA[Healthcare Breach]]></category>
		<category><![CDATA[Data Breach Notification]]></category>
		<category><![CDATA[data breach response]]></category>
		<category><![CDATA[healthcare data breach]]></category>
		<category><![CDATA[HITECH Act]]></category>
		<category><![CDATA[PHI]]></category>
		<category><![CDATA[PII]]></category>
		<category><![CDATA[State Law]]></category>

		<guid isPermaLink="false">http://www.experian.com/blogs/data-breach/?p=566</guid>
		<description><![CDATA[All data breaches have two things in common: the need for prompt resolution and the need for a robust preparedness plan. ]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.experian.com%2Fblogs%2Fdata-breach%2F2011%2F05%2F17%2Fdata-breaches-%25e2%2580%2593-to-prepare-or-not-to-prepare-the-answer-is-simple%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif&amp;source=Experian_DBR&amp;style=normal&amp;hashtags=Data+Breach+Notification,data+breach+response,healthcare+data+breach,HITECH+Act,PHI,PII,State+Law&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><em>Our guest blogger this week is</em><em> Paul Luehr, Managing Director, General Counsel, <a href="http://www.strozfriedberg.com/professionals/xprProfessionalDetails1.aspx?xpST=ProfessionalDetail&amp;professional=11" rel="”nofollow” nofollow" target="_blank" class="broken_link">Stroz Friedberg, LLC</a> -</em> <em>a global digital risk management and investigations firm</em><em>.</em><em></em></p>
<p>All data breaches have two things in common: the need for prompt resolution and the need for a robust preparedness plan. Healthcare institutions especially should heed the call for an incident response plan because it provides the best preventive medicine to minimize financial and reputational risks.  So <strong>PLAN</strong>, keeping in mind:  <strong><span style="text-decoration: underline;">P</span></strong>eople, the <strong><span style="text-decoration: underline;">L</span></strong>aw, and <strong><span style="text-decoration: underline;">A</span></strong>ction, with <strong><span style="text-decoration: underline;">N</span></strong>o time to waste.</p>
<p><strong><span style="text-decoration: underline;">P</span></strong>eople – Define the responsibilities of a coordinated incident response team. Don’t act alone. A good response team should include key internal players (In-house Counsel, IT, Compliance/Security, HR and Public Relations), as well as outside experts who confront data breaches on a regular basis (trusted Attorneys, Forensic Analysts and Fraud Monitors). These external experts can help restore key business functions, preserve crucial forensic evidence, strengthen data security, address victims’ needs, and communicate effectively with regulators and the public.</p>
<p><strong><span style="text-decoration: underline;">L</span></strong>aw – Track fast-changing data breach laws, privacy regulations, and notification mandates <em>before</em> a breach should occur.  This can help your organization identify protected health or personally identifiable information (PHI/PII which may trigger liability), navigate the HITECH Act and state law, understand reporting timelines, and effectively reach select constituents (i.e. Health and Human Services, victims, law enforcement and/or the media).</p>
<p><strong><span style="text-decoration: underline;">A</span></strong>ction – Outline clear action items to accomplish within the first seventy-two hours. One early misstep can destroy crucial evidence, delay an effective response, and trigger government penalties or class-action lawsuits.</p>
<p><strong><span style="text-decoration: underline;">N</span></strong>o time to waste – Remember that time is of the essence. <a href="http://www.experian.com/data-breach/data-breach-resources.html" target="_blank">Once a breach is identified</a>, the clock starts ticking and may require immediate notice to regulators and/or notification to individual victims within 60 days.  </p>
<p>A comprehensive preparedness plan can promote extraordinary efficiencies when a breach threatens a healthcare entity. So, <strong>create your PLAN now.</strong></p>
<div class="dropshadowboxes-container " style="width:600px;"><div class="dropshadowboxes-drop-shadow dropshadowboxes-rounded-corners dropshadowboxes-inside-and-outside-shadow dropshadowboxes-lifted-both dropshadowboxes-effect-default" style="border:1px solid #dddddd; height:;background-color:#ffffff"><a title="Download the free Data Breach Response Guide by Experian!" href="http://www.experian.com/innovation/business-resources/data-breach-response-guide.jsp?WT.srch=ecd_dbres_blog_051711_article ">Download your free Data Breach Response Guide!</a> </div></div>
<div style="float: right; margin-left: 10px;"><a href="http://twitter.com/share?url=http://www.experian.com/blogs/data-breach/2011/05/17/data-breaches-%e2%80%93-to-prepare-or-not-to-prepare-the-answer-is-simple/&via=Experian_DBR&text=Data breaches – to prepare or not to prepare? The answer is simple.&related=:&lang=en&count=horizontal" class="twitter-share-button">Tweet</a><script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script></div>]]></content:encoded>
			<wfw:commentRss>http://www.experian.com/blogs/data-breach/2011/05/17/data-breaches-%e2%80%93-to-prepare-or-not-to-prepare-the-answer-is-simple/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>