<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
   <channel>
      <title>Security, Privacy and The Law</title>
      <link>http://www.securityprivacyandthelaw.com/</link>
      <description />
      <language>en</language>
      <copyright>Copyright 2012</copyright>
      <lastBuildDate>Fri, 25 May 2012 11:22:19 -0500</lastBuildDate>
      <pubDate>Fri, 25 May 2012 11:22:19 -0500</pubDate>
      <generator>http://www.sixapart.com/movabletype/?v=3.34</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <feedburner:info uri="securityprivacyandthelaw" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://www.securityprivacyandthelaw.com/index.xml" /><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare href="http://www.bloglines.com/sub/http://www.securityprivacyandthelaw.com/index.xml" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><feedburner:feedFlare href="http://www.plusmo.com/add?url=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://plusmo.com/res/graphics/fbplusmo.gif">Subscribe with Plusmo</feedburner:feedFlare><feedburner:feedFlare href="http://www.thefreedictionary.com/_/hp/AddRSS.aspx?http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://img.tfd.com/hp/addToTheFreeDictionary.gif">Subscribe with The Free Dictionary</feedburner:feedFlare><feedburner:feedFlare href="http://www.bitty.com/manual/?contenttype=rssfeed&amp;contentvalue=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.bitty.com/img/bittychicklet_91x17.gif">Subscribe with Bitty Browser</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsalloy.com/?rss=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.newsalloy.com/subrss3.gif">Subscribe with NewsAlloy</feedburner:feedFlare><feedburner:feedFlare href="http://www.live.com/?add=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://tkfiles.storage.msn.com/x1piYkpqHC_35nIp1gLE68-wvzLZO8iXl_JMledmJQXP-XTBOLfmQv4zhj4MhcWEJh_GtoBIiAl1Mjh-ndp9k47If7hTaFno0mxW9_i3p_5qQw">Subscribe with Live.com</feedburner:feedFlare><feedburner:feedFlare href="http://mix.excite.eu/add?feedurl=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://image.excite.co.uk/mix/addtomix.gif">Subscribe with Excite MIX</feedburner:feedFlare><feedburner:feedFlare href="http://www.yourminis.com/subscribe.aspx?u=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.yourminis.com/images/addtoyourminisbadge.gif">Subscribe with Yourminis.com</feedburner:feedFlare><feedburner:feedFlare href="http://download.attensa.com/app/get_attensa.html?feedurl=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.attensa.com/blogs/attensa/WindowsLiveWriter/BadgeredintoBadges_10C02/attensa_feed_button5.gif">Subscribe with Attensa for Outlook</feedburner:feedFlare><feedburner:feedFlare href="http://www.webwag.com/wwgthis.php?url=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.webwag.com/images/wwgthis.gif">Subscribe with Webwag</feedburner:feedFlare><feedburner:feedFlare href="http://hub.netomat.net/account/account.autoSubscribe.jspa?urls=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.netomat.net/blogger/images/icon_netomat_feedbutton.gif">Subscribe with netomat Hub</feedburner:feedFlare><feedburner:feedFlare href="http://www.podcastready.com/oneclick_bookmark.php?url=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.podcastready.com/images/podcastready_button.gif">Subscribe with Podcast Ready</feedburner:feedFlare><feedburner:feedFlare href="http://www.flurry.com/pushRssFeed.do?r=fb&amp;url=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.flurry.com/images/flurry_rss_logo2.gif">Subscribe with Flurry</feedburner:feedFlare><feedburner:feedFlare href="http://www.wikio.com/subscribe?url=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.wikio.com/shared/img/add2wikio.gif">Subscribe with Wikio</feedburner:feedFlare><feedburner:feedFlare href="http://www.dailyrotation.com/index.php?feed=http%3A%2F%2Fwww.securityprivacyandthelaw.com%2Findex.xml" src="http://www.dailyrotation.com/rss-dr2.gif">Subscribe with Daily Rotation</feedburner:feedFlare><item>
         <title>A Few Thoughts from Deputy Undersecretary for Cybersecurity, Mark Weatherford, Department of Homeland Security</title>
         <description>&lt;p&gt;&lt;span style="font-size: 10pt"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;On May 16, &lt;a href="http://blog.dhs.gov/search/label/Mark%20Weatherford"&gt;Deputy Undersecretary for Cybersecurity, Mark Weatherford&lt;/a&gt;, spoke to the &lt;a href="http://www.massinsight.com/initiatives/cyber_security_center/"&gt;Advanced Cyber Security Center&lt;/a&gt; about &lt;a href="http://www.dhs.gov/files/cybersecurity.shtm"&gt;DHS's &lt;/a&gt;cyber security priorities: Information Sharing, R&amp;amp;D, and the Advanced Persistent Threat.&lt;/p&gt;
&lt;p&gt;On Information Sharing:&amp;nbsp; This is a continuing challenge, in part because of the way the federal government shares information. &amp;nbsp;At present, the federal government provides cyber threat information to private sector organizations, but prohibits discussion between those very organizations. His Office at DHS is working to address this unintended siloing of information, so as to&amp;nbsp;allow for greater cooperation and collaboration.&lt;/p&gt;
&lt;p&gt;On Research and Development:&amp;nbsp; He views cyber security education and training as essential, particularly because there is a rapidly shrinking pipeline of qualified professionals. As the Baby Boomers retire, they need to be replaced.&amp;nbsp; Another speaker noted that hiring in cyber security is growing at 14% per year. While Undersecretary Weatherford did not propose any government solutions to increase degree programs and students in cyber security, you have to believe that they will be forthcoming.&lt;/p&gt;
&lt;p&gt;On the Advanced Persistent Threat: The Undersecretary encouraged executive leadership to make cyber security as a priority, to raise awareness and create appropriate incentives.&amp;nbsp; With regard to prevention, he did not offer any sweeping solutions, but instead suggested focusing on &amp;ldquo;basic hygiene&amp;rdquo; steps that all&amp;nbsp;businesses can undertake, to eliminate the low-hanging fruit and get the greatest return on their data security investment.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;*&amp;nbsp; *&amp;nbsp;&amp;nbsp;*&lt;/p&gt;
&lt;p&gt;If you want to sign up for DHS cyber security updates, just click &lt;a href="https://public.govdelivery.com/accounts/USDHS/subscriber/new?"&gt;here&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/IGDD7tVEurE" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/IGDD7tVEurE/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/05/articles/cybersecurity-cybercrime/a-few-thoughts-from-deputy-undersecretary-for-cybersecurity-mark-weatherford-department-of-homeland-security/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">APT</category><category domain="http://www.securityprivacyandthelaw.com/tags">Advanced Persistent Threat</category><category domain="http://www.securityprivacyandthelaw.com/articles">Cybersecurity &amp; Cybercrime</category><category domain="http://www.securityprivacyandthelaw.com/tags">DHS</category><category domain="http://www.securityprivacyandthelaw.com/articles">Data Breach</category><category domain="http://www.securityprivacyandthelaw.com/tags">Department of Homeland Security</category><category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category><category domain="http://www.securityprivacyandthelaw.com/articles">Legislation &amp; Regulation</category><category domain="http://www.securityprivacyandthelaw.com/tags">Mark Weatherford</category><category domain="http://www.securityprivacyandthelaw.com/articles">Security Programs &amp; Policies</category><category domain="http://www.securityprivacyandthelaw.com/tags">cyber</category><category domain="http://www.securityprivacyandthelaw.com/tags">security</category>
         <pubDate>Fri, 25 May 2012 15:55:06 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/05/articles/cybersecurity-cybercrime/a-few-thoughts-from-deputy-undersecretary-for-cybersecurity-mark-weatherford-department-of-homeland-security/</feedburner:origLink></item>
            <item>
         <title>Data Breaches Keep Privacy and Security Lawyers Increasingly Busy and Looking for Recruits, But Recruits Are Hard to Find</title>
         <description>&lt;p&gt;Interesting &lt;a href="http://www.securityprivacyandthelaw.com/uploads/file/Of Counsel article feb 2012 Colin Zick.pdf"&gt;article from &lt;u&gt;Of Counsel &lt;/u&gt;&lt;/a&gt;regarding both the substance and the business of data privacy and security law.&amp;nbsp; Lawyers from several firms (including me) talk about current and pending legislation, the mechanisms of compliance and breach response, and the pipeline for new lawyers in the field of data security and privacy.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;One of the other attorneys discussed the shortage of trained attorneys in this area as follows:&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;You&amp;rsquo;d think, &amp;quot;Well heck, privacy has been around forever.&amp;quot;&amp;nbsp; But this is different. At law schools they need to find someone to teach this, and that&amp;rsquo;s not easy.&amp;nbsp; So we don&amp;rsquo;t have enough generations yet.&amp;nbsp; Mostly you have practicing attorneys who learned the area on the job, so you try to lateral in somebody, but it&amp;rsquo;s hard to get somebody just out of law school.&amp;nbsp; We have to train young associates.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/hgzAc3xBHlQ" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/hgzAc3xBHlQ/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/05/articles/government-enforcement/data-breaches-keep-privacy-and-security-lawyers-increasingly-busy-and-looking-for-recruits-but-recruits-are-hard-to-find/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/articles">Data Breach</category><category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category><category domain="http://www.securityprivacyandthelaw.com/articles">Security Programs &amp; Policies</category><category domain="http://www.securityprivacyandthelaw.com/tags">attorney</category><category domain="http://www.securityprivacyandthelaw.com/tags">breach</category><category domain="http://www.securityprivacyandthelaw.com/tags">data</category><category domain="http://www.securityprivacyandthelaw.com/tags">law school</category><category domain="http://www.securityprivacyandthelaw.com/tags">law student</category><category domain="http://www.securityprivacyandthelaw.com/tags">legislation</category><category domain="http://www.securityprivacyandthelaw.com/tags">privacy</category><category domain="http://www.securityprivacyandthelaw.com/tags">security</category><category domain="http://www.securityprivacyandthelaw.com/tags">training</category>
         <pubDate>Fri, 25 May 2012 10:23:28 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/05/articles/government-enforcement/data-breaches-keep-privacy-and-security-lawyers-increasingly-busy-and-looking-for-recruits-but-recruits-are-hard-to-find/</feedburner:origLink></item>
            <item>
         <title>Data Breaches Continue To Be A Problem For Health Care Providers:  South Shore Hospital (Massachusetts) Pays $750,000 To Settle Data Breach Charges</title>
         <description>&lt;p&gt;An aptly-timed article from Mass High Tech Business News noted earlier today that:&amp;nbsp;&lt;a href="http://www.masshightech.com/stories/2012/05/21/daily39-Data-breaches-a-growing-problem-in-healthcare.html"&gt;&amp;quot;Data Breaches [Are] a Growing Problem in Health Care.&amp;quot;&lt;/a&gt;&amp;nbsp;&amp;nbsp; This article focused on a recent breach at &lt;a href="http://www.childrenshospital.org/"&gt;Boston Children&amp;rsquo;s Hospital &lt;/a&gt;involving the records of 2,000 patients.&lt;/p&gt;
&lt;p&gt;The article was prescient, as this afternoon, the Massachusetts Attorney General announced a $750,000 settlement with suburban Boston's South Shore Hospital, relating to a &lt;a href="http://www.securityprivacyandthelaw.com/2010/09/articles/data-breach-1/gone-baby-gone-more-massachusetts-medical-records-go-missing/"&gt;2010 data breach&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;According to &lt;a href="http://www.mass.gov/ago/news-and-updates/press-releases/2012/2012-05-24-south-shore-hospital-data-breach-settlement.html"&gt;the Attorney General's press release&lt;/a&gt;:&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;South Shore Hospital has agreed to pay $750,000 to resolve allegations that it failed to protect the personal and confidential health information of more than 800,000 consumers, Attorney General Martha Coakley announced today. The investigation and settlement resulted from a data breach reported to the AG&amp;rsquo;s Office in July 2010 that included individual&amp;rsquo;s names, Social Security numbers, financial account numbers, and medical diagnoses....&lt;br /&gt;
&lt;br /&gt;
The consent judgment approved today in Suffolk Superior Court includes a $250,000 civil penalty and a payment of $225,000 for an education fund to be used by the Attorney General&amp;rsquo;s Office to promote education concerning the protection of personal information and protected health information. In addition to these payments, the consent judgment credits South Shore Hospital for $275,000 to reflect security measures it has taken subsequent to the breach.&lt;/p&gt;
&lt;p&gt;The suit and settlement also reflect one of the first uses of the delegated HIPAA&amp;nbsp;enforcement powers of state attorneys general under the Affordable Care Act.&lt;/p&gt;&lt;p&gt;The details are fairly typical of a hospital breach:&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;In February 2010, South Shore Hospital shipped three boxes containing 473 unencrypted back-up computer tapes with 800,000 individuals&amp;rsquo; personal information and protected health information off-site to be erased. The hospital contracted with Archive Data Solutions to erase the back-up tapes and resell them.&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;The hospital did not inform Archive Data, however, that personal information and protected health information was on the back-up computer tapes nor did South Shore Hospital determine whether Archive Data had sufficient safeguards in place to protect this sensitive information. Multiple companies handled the shipping of the boxes containing the tapes.&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;In June 2010 South Shore Hospital learned that only one of the boxes arrived at its destination in Texas. The missing boxes have not been recovered although there have been no reports of unauthorized use of the personal information or protected health information of affected individuals to date.&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;The allegations against South Shore Hospital in the lawsuit are based on both federal and state law violations, including failing to implement appropriate safeguards, policies, and procedures to protect consumers&amp;rsquo; information, failing to have a Business Associate Agreement in place with Archive Data, and failing to properly train its workforce with respect to health data privacy.&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;According to the consent judgment, South Shore Hospital has also agreed to take a variety of steps in order to ensure compliance with state and federal data security laws and regulations, including requirements regarding its contracts with business associates and third-party service providers engaged for data destruction purposes. The hospital also agreed to undergo a review and audit of certain security measures and to report the results and any corrective actions to the Attorney General.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/8B16IvYAVl4" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/8B16IvYAVl4/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/05/articles/government-enforcement/data-breaches-continue-to-be-a-problem-for-health-care-providers-south-shore-hospital-massachusetts-pays-750000-to-settle-data-breach-charges/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">Affordable Care Act</category><category domain="http://www.securityprivacyandthelaw.com/tags">Attorney General</category><category domain="http://www.securityprivacyandthelaw.com/articles">Data Breach</category><category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category><category domain="http://www.securityprivacyandthelaw.com/tags">HIPAA</category><category domain="http://www.securityprivacyandthelaw.com/articles">Healthcare Industry Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/tags">South Shore Hospital</category><category domain="http://www.securityprivacyandthelaw.com/tags">breach</category>
         <pubDate>Thu, 24 May 2012 15:12:21 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/05/articles/government-enforcement/data-breaches-continue-to-be-a-problem-for-health-care-providers-south-shore-hospital-massachusetts-pays-750000-to-settle-data-breach-charges/</feedburner:origLink></item>
            <item>
         <title>FTC Counters Constitutional Challenge to Fair Credit Reporting Act</title>
         <description>&lt;p&gt;The &lt;a href="http://www.ftc.gov"&gt;Federal Trade Commission &lt;/a&gt;has joined the &lt;a href="http://www.doj.gov"&gt;Department of Justice &lt;/a&gt;and the &lt;a href="http://www.consumerfinance.gov/"&gt;Consumer Financial Protection Bureau &lt;/a&gt;in filing a &lt;a href="http://www.ftc.gov/os/2012/05/120508fcraking-gis.pdf"&gt;memorandum&lt;/a&gt;&amp;nbsp;in support of the constitutionality of the &lt;a href="http://www.ftc.gov/os/statutes/fcrajump.shtm"&gt;Fair Credit Reporting Act&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This issue arose in &lt;u&gt;Shamara King v. General Information Services, Inc., &lt;/u&gt;a &amp;quot;consumer class action based upon Defendant&amp;rsquo;s willful violation of the Fair Credit Reporting Act, 15 U.S.C. &amp;sect;&amp;sect; 1681-1681x. (&amp;ldquo;FCRA&amp;rdquo;).&amp;quot; &amp;nbsp;In her &lt;a href="http://www.securityprivacyandthelaw.com/uploads/file/king complaint.pdf"&gt;complaint&lt;/a&gt;, Ms. King&amp;nbsp;brought suit &amp;quot;on behalf of thousands of employment applicants throughout the country who have been the subject of prejudicial, misleading and illegal background reports performed by the Defendant and sold to employers. Defendant has adopted and maintained a policy and practice of knowingly, intentionally, recklessly and willfully reporting outdated adverse information that is required to be excluded from the consumer reports that it sells.&amp;quot;&lt;/p&gt;
&lt;p&gt;The defendant GIS&amp;nbsp;then moved to dismiss the case, claiming that FCRA&amp;nbsp;was unconstitutional:&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;In sum, [the Supreme Court's decision in] &lt;a href="http://www.securityprivacyandthelaw.com/uploads/file/motion on pleadings.pdf"&gt;Sorrell [v. IMS&amp;nbsp;Health] &lt;/a&gt;marks a dramatic shift in the protection afforded to content- and speaker-based restrictions on truthful commercial information. As the dissent in Sorrell noted, its holding has sweeping effects on many other laws restricting disclosure of commercial information, including FCRA. Because a prohibition on disclosure of truthful information regarding an individual&amp;rsquo;s criminal record falls squarely within Sorrell&amp;rsquo;s holding,&amp;nbsp;[the FCRA]&amp;nbsp;is unconstitutional. Accordingly, the Court should enter judgment on the pleadings in favor of GIS on Plaintiff&amp;rsquo;s [FCRA] claim.&lt;/p&gt;
&lt;p&gt;This is certainly a creative defense, although it may be asking more than a federal district court is willing to do. It could be very interesting to see this argument get to an appellate court.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/7HBHsmz3hfg" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/7HBHsmz3hfg/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/05/articles/financial-information/ftc-counters-constitutional-challenge-to-fair-credit-reporting-act/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">Challenge</category><category domain="http://www.securityprivacyandthelaw.com/tags">Constitutional</category><category domain="http://www.securityprivacyandthelaw.com/tags">FCRA</category><category domain="http://www.securityprivacyandthelaw.com/tags">FTC</category><category domain="http://www.securityprivacyandthelaw.com/tags">Fair Credit Reporting Act</category><category domain="http://www.securityprivacyandthelaw.com/articles">Financial Industry Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category><category domain="http://www.securityprivacyandthelaw.com/articles">Legislation &amp; Regulation</category><category domain="http://www.securityprivacyandthelaw.com/articles">Retail Industry &amp; Customer Information Spotlight</category>
         <pubDate>Fri, 11 May 2012 10:17:25 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/05/articles/financial-information/ftc-counters-constitutional-challenge-to-fair-credit-reporting-act/</feedburner:origLink></item>
            <item>
         <title>ONC ("Office of the National Coordinator for Health Information Technology") Issues Guide to Privacy and Security of Health Information</title>
         <description>&lt;p&gt;&lt;span style="font-size: xx-small"&gt;The Office of the National Coordinator for Health Information Technology (&amp;quot;ONC&amp;quot;) has issued a &lt;/span&gt;&lt;a href="http://www.healthit.gov/sites/default/files/pdf/privacy/privacy-and-security-guide.pdf"&gt;&lt;span style="font-size: xx-small"&gt;Guide to Privacy and Security of Health Information Guide to Privacy and Security of Health Information&lt;/span&gt;&lt;/a&gt;&lt;span style="font-size: xx-small"&gt;.&amp;nbsp; The guide is targeted at smaller health care providers and their administrative staff members.&amp;nbsp; The 47 pages contain&amp;nbsp;five chapters:&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Chapter 1: What Is Privacy &amp;amp; Security and Why Does It Matter? &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Chapter 2: Privacy &amp;amp; Security and Meaningful Use &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Chapter 3: Privacy &amp;amp; Security 10-Step Plan for Meaningful Use &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Chapter 4: Integrating Privacy and Security into Your Practice &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Chapter 5: Privacy and Security Resources &lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;span style="font-size: xx-small"&gt;At first glance, there's nothing earth-shattering, but it could prove to be a useful&amp;nbsp;introduction for those moving toward meaningful use in the coming months.&lt;/span&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/KLmgKFqUwQ8" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/KLmgKFqUwQ8/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/05/articles/government-enforcement/onc-office-of-the-national-coordinator-for-health-information-technology-issues-guide-to-privacy-and-security-of-health-information/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category><category domain="http://www.securityprivacyandthelaw.com/tags">Guide</category><category domain="http://www.securityprivacyandthelaw.com/tags">Health Information</category><category domain="http://www.securityprivacyandthelaw.com/articles">Healthcare Industry Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/tags">ONC</category><category domain="http://www.securityprivacyandthelaw.com/tags">Office of the National Coordinator for Health Information Technology</category><category domain="http://www.securityprivacyandthelaw.com/tags">privacy</category><category domain="http://www.securityprivacyandthelaw.com/tags">security</category>
         <pubDate>Thu, 10 May 2012 11:24:40 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/05/articles/government-enforcement/onc-office-of-the-national-coordinator-for-health-information-technology-issues-guide-to-privacy-and-security-of-health-information/</feedburner:origLink></item>
            <item>
         <title>Governments Hire Hackers to Work for Them</title>
         <description>&lt;p&gt;Interesting article in Forbes, &amp;quot;&lt;a href="http://www.forbes.com/forbes/2012/0409/technology-hackers-government-security-zero-day-salesmen.html"&gt;The Zero-Day Salesmen&lt;/a&gt;,&amp;quot; about &amp;quot;government agencies who purchase such &amp;ldquo;zero-day&amp;rdquo; exploits, or hacking techniques that use undisclosed flaws in software, with the &amp;shy;explicit &amp;shy;intention of invading or disrupting the computers and phones of crime suspects and intelligence targets.&amp;quot;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/jqfoLBK0dpY" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/jqfoLBK0dpY/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/05/articles/identity-theft-1/governments-hire-hackers-to-work-for-them/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/articles">Cybersecurity &amp; Cybercrime</category><category domain="http://www.securityprivacyandthelaw.com/articles">Identity Theft</category><category domain="http://www.securityprivacyandthelaw.com/articles">Retail Industry &amp; Customer Information Spotlight</category>
         <pubDate>Mon, 07 May 2012 17:52:54 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/05/articles/identity-theft-1/governments-hire-hackers-to-work-for-them/</feedburner:origLink></item>
            <item>
         <title>Ninth Circuit En Banc Decision Creates Circuit Split with First Circuit that Affects Employer Claims Against Employees under the Computer Fraud and Abuse Act</title>
         <description>&lt;div class="entryinfo"&gt;&lt;span class="author"&gt;Posted on April 27, 2012 by &lt;a href="http://www.foleyhoag.com/People/Attorneys/Bialas-Brian.aspx"&gt;Brian P. Bialas&lt;/a&gt;&amp;nbsp;(This post also appears in &lt;a href="http://www.massachusettsnoncompetelaw.com/"&gt;www.massachusettsnoncompetelaw.com&lt;/a&gt;)&lt;/span&gt;&lt;/div&gt;
&lt;div class="entryinfo"&gt;&amp;nbsp;&lt;/div&gt;
&lt;div class="entryinfo"&gt;&lt;span class="author"&gt;Below is an article that I wrote for the June edition of Massachusetts Lawyers Journal, the monthly publication of the &lt;a href="http://www.massbar.org"&gt;Massachusetts Bar Association&lt;/a&gt;. It discusses an important case that interprets the &lt;a href="http://www.law.cornell.edu/uscode/text/18/1030"&gt;Computer Fraud and Abuse Act&lt;/a&gt; and the split in the law that case has created with the First Circuit, which includes Massachusetts.
&lt;p&gt;The U.S. District Court for the District of Massachusetts has noted that employers are increasingly using the federal Computer Fraud and Abuse Act (CFAA) &amp;ldquo;to sue former employees and their new companies who seek a competitive edge through wrongful use of information from the former employer&amp;rsquo;s computer system.&amp;rdquo; But in April, the U.S. Court of Appeals for the Ninth Circuit made such employer lawsuits more difficult in that circuit by issuing its en banc decision in &lt;u&gt;&lt;a href="http://www.ca9.uscourts.gov/datastore/opinions/2012/04/10/10-10038.pdf"&gt;United States v. Nosal&lt;/a&gt;&lt;/u&gt;. In &lt;u&gt;Nosal&lt;/u&gt;, the Ninth Circuit determined that an employee does not &amp;ldquo;exceed[] authorized access&amp;rdquo; to information in a computer under the CFAA when he or she violates an employer&amp;rsquo;s computer use restrictions. In contrast, the First Circuit concluded more than a decade ago in&amp;nbsp;&lt;u&gt;&lt;a href="http://scholar.google.com/scholar_case?case=2683575157740054983&amp;amp;hl=en&amp;amp;as_sdt=2&amp;amp;as_vis=1&amp;amp;oi=scholarr"&gt;EF Cultural Travel BV v. Explorica, Inc.&lt;/a&gt; &lt;/u&gt;that contractual restrictions can serve as the basis for a CFAA violation. This circuit split affects the ability of employers to maintain lawsuits under the CFAA against former employees who were authorized to access their employer&amp;rsquo;s confidential information but took that information to competitors. It also tees up the CFAA for review by the Supreme Court.&lt;/p&gt;
&lt;p&gt;I. The CFAA&lt;/p&gt;
&lt;p&gt;The CFAA provides for both criminal and civil liability (if certain conditions are met) when a person commits various acts involving a computer and &amp;ldquo;exceeds authorized access&amp;rdquo; or acts &amp;ldquo;without authorization&amp;rdquo; in the process. The provision under review in both &lt;u&gt;Nosal &lt;/u&gt;and &lt;u&gt;Explorica &lt;/u&gt;was 18 U.S.C. &amp;sect; 1030(a)(4), which imposes liability on someone who &amp;ldquo;knowingly and with the intent to defraud, accesses a protected computer without authorization, or exceeds authorized access, and by means of such conduct furthers the intended fraud and obtains anything of value.&amp;rdquo; The CFAA defines &amp;ldquo;exceeds authorized access&amp;rdquo; as &amp;ldquo;to access a computer with authorization and to use such access to obtain or alter information in the computer that the accesser is not entitled so to obtain or alter.&amp;rdquo; &amp;ldquo;Without authorization&amp;rdquo; is not defined. Both the Ninth Circuit and the First Circuit focused their respective analyses on whether employees &amp;ldquo;exceed[ed] authorized access&amp;rdquo; when they were permitted by their employers to access certain information on a computer, but then used that information for the benefit of competitors. But because &amp;ldquo;without authorization&amp;rdquo; is not defined, judicial interpretations of &amp;ldquo;exceeds authorized access&amp;rdquo; necessarily affect the meaning of &amp;ldquo;without authorization&amp;rdquo; as well.&lt;/p&gt;
&lt;p&gt;II. The Ninth Circuit: Limiting the CFAA to &amp;ldquo;Hacking&amp;rdquo;&lt;/p&gt;
&lt;p&gt;In &lt;u&gt;Nosal&lt;/u&gt;, the defendant Nosal worked for an executive search firm and convinced several employees shortly before he left to start a competing business with him. He asked the employees to use their log-in credentials to download confidential information from the firm&amp;rsquo;s computers and to send the information to him. The employees were permitted to access the information by their employer, but were forbidden from disclosing it. Nosal was indicted for aiding and abetting the employees in &amp;ldquo;exceed[ing] their authorized access&amp;rdquo; in violation of 18 U.S.C. &amp;sect; 1030(a)(4). The charge was dismissed by the district court, and the government appealed.&lt;/p&gt;
&lt;p&gt;The &lt;u&gt;Nosal&lt;/u&gt; court, sitting en banc, affirmed, reasoning that &amp;ldquo;exceeds authorized access&amp;rdquo; should only be applied to a person &amp;ldquo;who&amp;rsquo;s authorized to access only certain data or files but accesses unauthorized data or files&amp;mdash;what is colloquially known as &amp;lsquo;hacking.&amp;rsquo;&amp;rdquo; The statutory definition of the phrase supported this interpretation because &amp;ldquo;entitled&amp;rdquo; should be read as a synonym for &amp;ldquo;authorized&amp;rdquo; in the text and a broader interpretation &amp;ldquo;would transform the CFAA from an anti-hacking statute into an expansive misappropriation statute,&amp;rdquo; which the court would not presume Congress intended absent clearer language. A broader construction &amp;ldquo;would expand its scope far beyond computer hacking to criminalize any unauthorized use of information obtained from a computer.&amp;rdquo; What is more, because &amp;sect; 1030(a)(2)(C) punishes a person who merely &amp;ldquo;exceeds authorized access&amp;rdquo; and &amp;ldquo;obtains information from any protected computer&amp;rdquo; without intent to defraud, a broader interpretation &amp;ldquo;makes every violation of a private computer use policy a federal crime.&amp;rdquo; The court construed the statute narrowly &amp;ldquo;so that Congress will not unintentionally turn ordinary citizens into criminals&amp;rdquo; and concluded that &amp;ldquo;&amp;lsquo;exceeds authorized access&amp;rsquo; in the CFAA is limited to violations of restrictions on access to information, and not restrictions on its use.&amp;rdquo; Because Nosal&amp;rsquo;s coworkers had permission to access the information, Nosal was off the hook.&lt;/p&gt;
&lt;p&gt;The dissent, citing the &lt;u&gt;Explorica &lt;/u&gt;decision among others, noted that none of the other circuits to consider the meaning of &amp;ldquo;exceeds authorized access&amp;rdquo; read the statute the same way.&lt;/p&gt;
&lt;p&gt;III. The First Circuit: Breach of Confidentiality Agreement Proves Excessive Access&lt;/p&gt;
&lt;p&gt;The First Circuit in &lt;u&gt;Explorica &lt;/u&gt;reviewed the district court&amp;rsquo;s issuance of a preliminary injunction against defendant Explorica and several of its employees pursuant to &amp;sect; 1030(a)(4) of the CFAA. In &lt;u&gt;Explorica&lt;/u&gt;, an employee of Explorica and a former employee of the plaintiff, EF Cultural Travel BV (EF), revealed EF proprietary information to Zefer, a company employed by defendant Explorica, an EF competitor, in violation of his confidentiality agreement with EF. Zefer then used that information to create a computer program that &amp;ldquo;scraped&amp;rdquo; EF&amp;rsquo;s public website of pricing information, thus allowing Explorica to undercut EF&amp;rsquo;s prices.&lt;/p&gt;
&lt;p&gt;The court ruled that the district court&amp;rsquo;s decision was not clearly erroneous because &amp;ldquo;whatever authorization Explorica had to navigate around EF&amp;rsquo;s site (even in a competitive vein),&amp;rdquo; if EF&amp;rsquo;s allegations were proven, EF likely would prove that Explorica &amp;ldquo;exceeded that authorization by providing proprietary information and know-how to Zefer to create the scraper.&amp;rdquo; In fact, &amp;ldquo;[p]ractically speaking, . . . if proven, Explorica&amp;rsquo;s wholesale use of EF&amp;rsquo;s travel codes to facilitate gathering EF&amp;rsquo;s prices from its website reeks of use&amp;mdash;and, indeed, abuse&amp;mdash;of proprietary information that goes beyond any authorized use of EF&amp;rsquo;s website.&amp;rdquo; Although decided in a different factual and procedural context than &lt;u&gt;Nosal&lt;/u&gt;, as one judge in the District of Massachusetts noted, the First Circuit in &lt;u&gt;Explorica &lt;/u&gt;&amp;ldquo;advocated a broader reading&amp;rdquo; of the CFAA than the Ninth Circuit.&lt;/p&gt;
&lt;p&gt;IV. Conclusion: On to the Supreme Court?&lt;/p&gt;
&lt;p&gt;The &lt;u&gt;Nosal &lt;/u&gt;decision&amp;rsquo;s statement that a CFAA violation is limited to violations of restrictions on access to information, not use, when read with Explorica&amp;rsquo;s competing conclusion that a CFAA violation may be based on the abuse of proprietary information, crystallizes the CFAA circuit split for Supreme Court review. Violations of an employer&amp;rsquo;s contractual and computer use policies cannot be used to show a CFAA violation in the Ninth Circuit, but they can in the First Circuit. Assuming the government seeks certiorari, a decision by the Supreme Court not to review the &lt;u&gt;Nosal &lt;/u&gt;case will have an immediate impact on employer decisions on where to file CFAA claims against former employees who may have taken confidential information. In fact, the &lt;u&gt;Nosal &lt;/u&gt;decision adds yet another hurdle for employers filing lawsuits in California (part of the Ninth Circuit) in addition to the unenforceability of non-competition agreements as a matter of policy in that state. The circuit split is even more important because of the location of important industries: Silicon Valley and Massachusetts (part of the First Circuit) are high-tech hubs where many companies rely on highly sensitive information to stay ahead of the competition. If the Supreme Court chooses not to review &lt;u&gt;Nosal&lt;/u&gt;, more employers will file CFAA cases outside of the Ninth Circuit.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/g884JY9EkHQ" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/g884JY9EkHQ/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/05/articles/government-enforcement/ninth-circuit-en-banc-decision-creates-circuit-split-with-first-circuit-that-affects-employer-claims-against-employees-under-the-computer-fraud-and-abuse-act/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">Computer Fraud and Abuse Act</category><category domain="http://www.securityprivacyandthelaw.com/tags">Explorica</category><category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category><category domain="http://www.securityprivacyandthelaw.com/tags">Nosal</category>
         <pubDate>Wed, 02 May 2012 12:57:55 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/05/articles/government-enforcement/ninth-circuit-en-banc-decision-creates-circuit-split-with-first-circuit-that-affects-employer-claims-against-employees-under-the-computer-fraud-and-abuse-act/</feedburner:origLink></item>
            <item>
         <title>Random Cyberattackers Versus the Advanced Persistent Threat</title>
         <description>&lt;p&gt;What do cyberattackers want?&amp;nbsp; According to &lt;a href="http://online.wsj.com/article/SB10001424052970204603004577269544215115670.html"&gt;a recent article in the Wall Street Journal&lt;/a&gt;, it depends.&amp;nbsp; And the most dangerous ones are the ones that really know what they want:&amp;nbsp; the Advanced Persistent Threat (APT).&amp;nbsp; They APT&amp;nbsp;isn't easily defined, but think of APTs as professional thieves, going after high-value targets and using sophisticated techniques.&amp;nbsp; They are &lt;a href="http://en.wikipedia.org/wiki/The_Thomas_Crown_Affair_(1968_film)"&gt;Thomas Crown &lt;/a&gt;to the every &lt;a href="http://en.wikipedia.org/wiki/The_Friends_of_Eddie_Coyle_(novel)"&gt;Eddie Coynes &lt;/a&gt;of the world.&amp;nbsp; There's &lt;a href="http://www.massinsight.com/cms_page_media/184/ACSC%20Launch%20Conference%20Slides.pdf"&gt;more discussion of APTs&lt;/a&gt; on the Advanced Cyber Security Center's website.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/znwhPvG9eXQ" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/znwhPvG9eXQ/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/05/articles/cybersecurity-cybercrime/random-cyberattackers-versus-the-advanced-persistent-threat/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">APT</category><category domain="http://www.securityprivacyandthelaw.com/tags">Advanced Persistent Threat</category><category domain="http://www.securityprivacyandthelaw.com/tags">Cyberattackers</category><category domain="http://www.securityprivacyandthelaw.com/articles">Cybersecurity &amp; Cybercrime</category>
         <pubDate>Tue, 01 May 2012 21:46:54 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/05/articles/cybersecurity-cybercrime/random-cyberattackers-versus-the-advanced-persistent-threat/</feedburner:origLink></item>
            <item>
         <title>Massachusetts Reports on Data Breaches for 2007-2011</title>
         <description>&lt;p&gt;&lt;span style="font-size: xx-small"&gt;The &lt;/span&gt;&lt;a href="http://www.mass.gov/ocabr/"&gt;&lt;span style="font-size: xx-small"&gt;Massachusetts Office of Consumer Affairs and Business Regulation&amp;nbsp;&lt;/span&gt;&lt;/a&gt;&lt;span style="font-size: xx-small"&gt;has issued its first&amp;nbsp;&lt;/span&gt;&lt;a href="http://www.mass.gov/ocabr/docs/2011-data-breach-report.pdf"&gt;&lt;span style="font-size: xx-small"&gt;annual report on data breaches&lt;/span&gt;&lt;/a&gt;&lt;span style="font-size: xx-small"&gt;.&amp;nbsp; Since&amp;nbsp;Massachusetts has one of the more strict state laws on data security and breach reporting, this report bears close attention for trends across the nation.&amp;nbsp; Some of the highlights in this summary, which covers 2007-2011:&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Through September 30, 2011, the largest share of breaches was not in the financial sector, but in the retail and healthcare industries, along with government. &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Since the Data Security law, c. 93H, went into effect, the Office of Consumer Affairs and Business Regulation has tracked the data breach notifications it has received. As of Sept. 30, 2011, there had been 1,833 notifications of security breaches. The number of Massachusetts residents affected by the reported incidents since November 1, 2007 now totals 3,166,031. &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;As of September 30, 2011, criminal or malicious breaches totaled 241 of 454 notifications received, 52.5 percent of total breaches reported. &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Encryption is lagging:&amp;nbsp; If all portable devices were encrypted from 2007 to 2011, the number of residents whose personal information was compromised would be remarkably lower by 47 percent or 1,490,308 people. If all portable devices were encrypted from March 1, 2010 the number of compromised residents would have decreased by 29 percent or 909,992 people. &lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;span style="font-size: xx-small"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/QoyRNqdazQ0" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/QoyRNqdazQ0/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/04/articles/government-enforcement/massachusetts-reports-on-data-breaches-for-20072011/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">2011</category><category domain="http://www.securityprivacyandthelaw.com/articles">Data Breach</category><category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category><category domain="http://www.securityprivacyandthelaw.com/articles">Identity Theft</category><category domain="http://www.securityprivacyandthelaw.com/articles">Legislation &amp; Regulation</category><category domain="http://www.securityprivacyandthelaw.com/tags">Massachusetts Office of Consumer Affairs and Business Regulation</category><category domain="http://www.securityprivacyandthelaw.com/articles">Retail Industry &amp; Customer Information Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/tags">encrpytion</category><category domain="http://www.securityprivacyandthelaw.com/tags">report</category>
         <pubDate>Tue, 24 Apr 2012 08:03:57 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/04/articles/government-enforcement/massachusetts-reports-on-data-breaches-for-20072011/</feedburner:origLink></item>
            <item>
         <title>Stanford Law Review's Privacy Symposium</title>
         <description>&lt;p&gt;&lt;span style="font-size: xx-small"&gt;The Stanford Law Review has an interesting series of articles on privacy in its &lt;/span&gt;&lt;a href="http://www.stanfordlawreview.org/online/privacy-paradox"&gt;&lt;span style="font-size: xx-small"&gt;most recent edition&lt;/span&gt;&lt;/a&gt;&lt;span style="font-size: xx-small"&gt;:&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;A Reasonableness Approach to Searches After the Jones GPS Tracking Case by Peter Swire&lt;br /&gt;
    In the oral argument this fall in United States v. Jones, several Supreme Court Justices struggled with the government&amp;rsquo;s view that it can place Global Positioning System (GPS) tracking devices on cars without a warrant or other Fourth Amendment limit.&lt;br /&gt;
    &amp;nbsp; &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Privacy in the Age of Big Data by Omer Tene &amp;amp; Jules Polonetsky&lt;br /&gt;
    We live in an age of &amp;ldquo;big data.&amp;rdquo; Data has become the raw material of production, a new source of immense economic and social value&lt;br /&gt;
    &amp;nbsp; &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Yes We Can (Profile You) by Daniel Kreiss&lt;br /&gt;
    Online advertising and field campaigning rely on voter modeling based on hundreds of data points culled from surveys, public records, and commercial information sources such as credit histories. This data details the location, demographics, political affiliations, social networks, behavior, and interests of citizens.&lt;br /&gt;
    &amp;nbsp; &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Paving the Regulatory Road to the &amp;quot;Learning Health Care System&amp;quot; by Deven McGraw&lt;br /&gt;
    The poor quality and high cost of health care in the U.S. is well documented. The widespread adoption of electronic medical records&amp;mdash;for purposes of improving quality and reducing costs&amp;mdash;is key to reversing these trends. But federal privacy regulations do not set clear and consistent rules for access to health information to improve health care quality. Consequently, the regulations serve as a disincentive to robust analysis of information in medical records and may interfere with efforts to accelerate quality improvements.&lt;br /&gt;
    &amp;nbsp; &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Famous for Fifteen People by Simon J. Frankel, Laura Brookover &amp;amp; Stephen Satterfield&lt;br /&gt;
    A recent case in the Northern District of California, Fraley v. Facebook, recalls singer-songwriter Momus&amp;rsquo;s prescient parody of Andy Warhol: &amp;ldquo;In the future, everyone will be famous for fifteen people.&amp;rdquo; Although Momus was discussing the revolution in the recording and distribution of music made possible by digital technologies that allowed performers outside the mainstream to become &amp;ldquo;stars&amp;rdquo; within certain listening circles, his statement applies at least as forcefully to the recent revolution in digital communications technologies, particularly the emergence of social media. The Fraley decision suggests that Momus&amp;rsquo;s prediction was dead on&amp;mdash;and that the future has arrived.&lt;br /&gt;
    &amp;nbsp; &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;The Right to Be Forgotten by Jeffrey Rosen&lt;br /&gt;
    At the end of January, the European Commissioner for Justice, Fundamental Rights, and Citizenship, Viviane Reding, announced the European Commission&amp;rsquo;s proposal to create a sweeping new privacy right&amp;mdash;the &amp;ldquo;right to be forgotten.&amp;rdquo; The right, which has been hotly debated in Europe for the past few years, has finally been codified as part of a broad new proposed data protection regulation.&lt;br /&gt;
    &amp;nbsp; &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;The Dead Past by Alex Kozinski&lt;br /&gt;
    I must start out with a confession: When it comes to technology, I&amp;rsquo;m what you might call a troglodyte. I don&amp;rsquo;t own a Kindle or an iPad or an iPhone or a Blackberry. I don&amp;rsquo;t have an avatar or even voicemail. I don&amp;rsquo;t text.&amp;nbsp; I don&amp;rsquo;t reject technology altogether: I do have a typewriter&amp;mdash;an electric one, with a ball. But I do think that technology can be a dangerous thing because it changes the way we do things and the way we think about things; and sometimes it changes our own perception of who we are and what we&amp;rsquo;re about. And by the time we realize it, we find we&amp;rsquo;re living in a different world with different assumptions about such fundamental things as property and privacy and dignity. And by then, it&amp;rsquo;s too late to turn back the clock. &lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/0adPXgLIbjc" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/0adPXgLIbjc/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/04/articles/recent-legislation-1/stanford-law-reviews-privacy-symposium/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/articles">Legislation &amp; Regulation</category><category domain="http://www.securityprivacyandthelaw.com/tags">Standford</category><category domain="http://www.securityprivacyandthelaw.com/tags">privacy</category><category domain="http://www.securityprivacyandthelaw.com/tags">symposium</category>
         <pubDate>Sun, 22 Apr 2012 06:12:08 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/04/articles/recent-legislation-1/stanford-law-reviews-privacy-symposium/</feedburner:origLink></item>
            <item>
         <title>Second Circuit Reverses Convictions in Data-Theft Prosecution and Narrowly Interprets Federal Criminal Statutes with Important Intellectual Property Implications</title>
         <description>&lt;p&gt;by &lt;a href="http://www.foleyhoag.com/people/attorneys/marx-daniel.aspx"&gt;Daniel Marx&lt;/a&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;In February 2012, following oral argument, the U.S. Court of Appeals for the Second Circuit issued a brief order reversing Sergey Aleynikov&amp;rsquo;s convictions for violating the National Stolen Property Act, 18 U.S.C. &amp;sect;&amp;nbsp;2314 (&amp;ldquo;NSPA&amp;rdquo;), and the Economic Espionage Act, 18 U.S.C. &amp;sect; 1832(b) (&amp;ldquo;EEA&amp;rdquo;), and stating a longer opinion would follow.&amp;nbsp;In that promised opinion, which was issued earlier this month, &lt;i&gt;see &lt;a href="http://caselaw.findlaw.com/us-2nd-circuit/1598446.html"&gt;United States v. Aleynikov&lt;/a&gt;&lt;/i&gt;&lt;a href="http://caselaw.findlaw.com/us-2nd-circuit/1598446.html"&gt;, No. 11-1126 (2d Cir. Apr. 11, 2012), &lt;/a&gt;the appeals court explained why Aleynikov did not commit the charged federal crimes, and more importantly, it established significant limits on future federal prosecutions concerning the theft of intangible intellectual property.&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;&lt;u&gt;Background&lt;/u&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;Before his troubles began, Aleynikov worked for two years as a computer programmer at Goldman Sachs &amp;amp; Co.&amp;nbsp;There, he helped to write the source code for Goldman&amp;rsquo;s proprietary high-frequency trading (&amp;ldquo;HFT&amp;rdquo;) system, which makes large volume trades based on algorithms that incorporate rapid market developments and past trading data.&amp;nbsp;&amp;nbsp; Kept highly confidential and never licensed to any other parties, the HFT system was akin to the Wall Street bank&amp;rsquo;s own secret formula for Coke.&amp;nbsp;&amp;nbsp;As an employee, Aleynikov was subject to strict confidentiality provisions that prohibited him from divulging this valuable trade secret.&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;Aleynikov had other plans, however.&amp;nbsp;He decided to leave Goldman and join Teza Technologies, LLC, a financial firm in Chicago with plans to develop its own HFT system.&amp;nbsp;(The government did not accuse Teza of any wrongdoing.)&amp;nbsp;On his last day at Goldman, Aleynikov encrypted and uploaded source code from the HFT system to a server in Germany.&amp;nbsp;After returning home that night, Aleynikov downloaded the data to his personal computer.&amp;nbsp;He later made additional copies of the computer program on other devices, including a thumb drive and laptop, and also took steps to cover his electronic tracks.&amp;nbsp;Aleynikov then traveled to Chicago to meet with representatives of Teza, and he brought the purloined source code with him.&amp;nbsp;When he returned to New Jersey, he was arrested by the FBI at Newark airport.&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;At trial, Aleynikov argued that he only copied open source materials and never intended to harm Goldman.&amp;nbsp;The jury was unconvinced and found him guilty.&amp;nbsp;The trial court sentenced him to 97 months in prison.&amp;nbsp;In its recent opinion reversing Aleynikov&amp;rsquo;s convictions, the Second Circuit certainly did not condone his behavior -- repeatedly calling him a corporate thief and noting that his dishonest conduct breached his confidentiality obligations to his employer.&amp;nbsp;&amp;nbsp; But the court concluded, after closely analyzing the text of the criminal statutes and the relevant case law, that Aleynikov had not violated the NSPA or EEA. &amp;nbsp;&amp;nbsp;(The appeal related only to the criminal prosecution, and it did not address whether or how Goldman might sue Aleynikov for money damages.)&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;&lt;u&gt;Computer Fraud and Abuse Act&lt;/u&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;Although not part of the appeal, Aleynikov was also charged with violating the Computer Fraud and Abuse Act (&amp;ldquo;CFAA&amp;rdquo;), 18 U.S.C. &amp;sect; 1030, which prohibits accessing computers without authorization in certain specified situations that the statute describes (for example, protected computers containing national security information).&amp;nbsp;Aleynikov moved to dismiss that charge, and the trial court granted his motion.&amp;nbsp;&amp;nbsp; As the Second Circuit recounted, the trial court concluded that, as an employee, Aleynikov was authorized to access Goldman&amp;rsquo;s network; that as a programmer who worked on the HFT system in particular, his access to that source code did not exceed his authorization; and perhaps most critically, that his &amp;ldquo;authorized use of a computer in a manner that misappropriates information is not an offense under the CFAA.&amp;rdquo;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;Because this count was dismissed, and the government did not appeal from that decision, the Second Circuit had no reason to address the issue.&amp;nbsp;As it stands, therefore, it may be a crime under the CFAA for an outsider &amp;ndash; say, an ill-intentioned hacker &amp;ndash; to access a computer network and misappropriate source code or other intellectual property, but it is not illegal for an insider &amp;ndash; such as an authorized employee &amp;ndash; to do the very same thing.&amp;nbsp;When considering the parameters of the CFAA, it is important to distinguish (a) whether a person is authorized to access a computer from (b) how the person uses information from the computer (e.g., in violation of application confidentiality or non-compete agreements).&amp;nbsp;The CFAA addresses unauthorized access to certain computers, not the improper use of information stored within.&amp;nbsp;&lt;/p&gt;&lt;p style="margin: 0in 0in 10pt"&gt;&lt;u&gt;National Stolen Property Act&lt;/u&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;Aleynikov was charged with, and convicted of, violating the NSPA which prohibits as a federal crime &amp;ldquo;transporting, transmitting or transferring in interstate or foreign commerce any goods, wares, merchandise, securities or money, of the value of $5,000 or more, knowing the same to have been stolen, converted or taken by fraud.&amp;rdquo;&amp;nbsp;&amp;nbsp; As the Second Circuit explained, the &amp;ldquo;decisive question&amp;rdquo; was whether the source code that Aleynikov stole from Goldman constituted &amp;ldquo;goods, wares [or] merchandise&amp;rdquo; within the meaning of the NPSA.&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;To answer that question, the appeals court looked back almost 50-years &amp;ndash; long before the computer, much less complex HFT systems &amp;ndash; to its decision in &lt;i&gt;United States v. Bottone&lt;/i&gt;, 365 F.2d 389 (2d Cir. 1966).&amp;nbsp;In that case, the Second Circuit affirmed the conviction of Caesar Bottone who had photocopied documents outlining proprietary manufacturing procedures for certain pharmaceuticals and transported those documents across state lines.&amp;nbsp;But the law would not have ensnared Bottone, the court explained, if he had memorized the same manufacturing information and taken it, in his mind, across the Hudson River.&amp;nbsp;Based on this prior precedent, the Second Circuit concluded, in &lt;i&gt;Aleynikov&lt;/i&gt;, that the NSPA is not &amp;ldquo;endlessly elastic,&amp;rdquo; rather &amp;ldquo;some tangible property must be taken from the owner for there to be deemed a &amp;lsquo;good&amp;rsquo; that is &amp;lsquo;stolen&amp;rsquo; for the purposes of the NSPA.&amp;rdquo;&amp;nbsp;&amp;nbsp; Stated another way, the Second Circuit joined other federal appeals courts including the First Circuit in holding that stealing &amp;ldquo;purely intangible properly&amp;rdquo; is not a crime under the NSPA.&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;Wary of declaring open season on intellectual property, federal courts have been careful to emphasize a critical qualification:&amp;nbsp;&amp;nbsp;although the NSPA does not apply to &amp;ldquo;purely intangible information,&amp;rdquo; &amp;ldquo;it does apply when there has been &amp;lsquo;some tangible item taken, however insignificant or valueless it may be, absent the intangible component.&amp;rsquo;&amp;rdquo;&amp;nbsp;&lt;i&gt;United States v. Martin&lt;/i&gt;, 228 F.2d 1, 14-15 (1st Cir. 2000) (quoting &lt;i&gt;United States v. Brown&lt;/i&gt;, 925 F.2d at 1037, 1308 n.14 (10th Cir. 1991)).&amp;nbsp;But what does that mean exactly?&amp;nbsp;The Second Circuit did not have to answer that question, because there was no allegation that Aleynikov took anything tangible from Goldman, such as a compact disc or thumb drive containing source code.&amp;nbsp;If Aleynikov had copied data onto a Goldman disc, he would have violated the NSPA, but instead he uploaded it to a server, so he did not.&amp;nbsp;That distinction makes the critical question of criminal liability turn on whether a defendant steals a five-cent CD, not a five-million-dollar computer program.&amp;nbsp;That seems somewhat silly, as the Second Circuit acknowledged, noting &amp;ldquo;there is no doubt that in virtually every case involving proprietary computer code worth stealing, the value of the intangible code will vastly exceed the value of any physical item on which it might be stored.&amp;rdquo;&amp;nbsp;Read this way, the NSPA does a better job protecting thumb drives than the trade secrets stored on them.&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;To its credit, the Second Circuit did not ignore these oddities.&amp;nbsp;Rather, following the well-settled principle that federal crimes are &amp;ldquo;solely creatures of statute,&amp;rdquo; &lt;i&gt;Dowling v. United States&lt;/i&gt;, 473 U.S. 207, 213 (1985), which must be narrowly construed to avoid due process concerns, the appeals court appropriately refused &amp;ldquo;to stretch or update statutory words of plain and ordinary meaning&amp;rdquo; &amp;ndash; such as &amp;ldquo;goods&amp;rdquo; &amp;ndash; &amp;ldquo;to better accommodate the digital age.&amp;rdquo;&amp;nbsp;&amp;nbsp; Amending and expanding federal criminal statutes is a job reserved for Congress.&amp;nbsp;And the legislature, like the courts, must keep up with rapid technological change.&amp;nbsp;Indeed, re-reading the First Circuit&amp;rsquo;s 2000 decision in &lt;i&gt;Martin&lt;/i&gt;, one gets the sense that it, too, may already be out of date.&amp;nbsp;The First Circuit appeared to equate stolen &amp;ldquo;software,&amp;rdquo; which the defendant had mailed to her co-conspirator, with other &amp;ldquo;physical goods,&amp;rdquo; such as &amp;ldquo;test kits&amp;rdquo; for animal vaccines.&amp;nbsp;Today, however, software is more often downloaded from the internet, or accessed in a cloud, than delivered on a disc or any other physical media.&amp;nbsp;That evolution may have significant consequences for how the NSPA applies to the misappropriation of software, like the source code at issue in &lt;i&gt;Aleynikov&lt;/i&gt;.&amp;nbsp;If the NSPA retains its focus on the theft of physical items, then at least with regard to purely intellectual property, it may fade into obscurity like the floppy disk.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;&lt;u&gt;Economic Espionage Act&lt;/u&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;Aleynikov was also charged with, and convicted of, violating the domestic provision of the EEA which exposes to a 10-year prison sentence any person who, &amp;ldquo;with the intent to convert a trade secret, that is related to or included in a product that is produced for or placed in interstate or foreign commerce, to the economic benefit of anyone other than the owner thereof, and intending or knowing that the offense will, injure any owner of that trade secret, knowingly . . . without authorization . . . downloads, uploads, . . . transmits, . . . or conveys such information.&amp;rdquo;&amp;nbsp;This federal criminal statute presented the Second Circuit with an entirely different problem, one that resonates more with the current debate over the Affordable Care Act and the Commerce Clause than the legal challenges of the digital age.&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;The domestic provision of the EEA applies, by its terms, only to those trade secrets that are &amp;ldquo;related to or included in a product that is produced for or placed in interstate or foreign commerce.&amp;rdquo;&amp;nbsp;To use an example mentioned earlier, the secret formula for Coca-Cola has qualified for almost 100 years (since 1920) as such a trade secret because it is used in manufacturing soda which is itself a product placed in interstate and foreign commerce.&amp;nbsp;But Goldman did not sell or license its HFT system like cans of Coke.&amp;nbsp;&amp;nbsp; Quite the opposite.&amp;nbsp;Goldman aggressively protected the confidentiality of its computer program, and in large part, the system&amp;rsquo;s substantial value flowed from the fact that others did not know how it worked and, thus, could not design a competing system to affect even more rapid trades.&amp;nbsp;&amp;nbsp; For that reason, the Second Circuit concluded:&amp;nbsp;&amp;ldquo;Because the HFT system was not designed to enter or pass into commerce, or to make something that does, Aleynikov&amp;rsquo;s theft of source code relating to that system was not an offense under the EEA.&amp;rdquo;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;Further, in reaching that conclusion, the Second Circuit rejected the broader reading that the trial court had endorsed &amp;ndash; a product is &amp;ldquo;produced for&amp;rdquo; interstate or foreign commerce if its purpose is to &amp;ldquo;facilitate or engage&amp;rdquo; in such commerce.&amp;nbsp;&amp;nbsp; That interpretation covered Goldman&amp;rsquo;s HFT system, which clearly existed to facilitate and engage in securities transactions on domestic and foreign exchanges.&amp;nbsp;But the Second Circuit ruled that understanding was too broad and inconsistent with the statutory text.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;Thus, as with the NSPA, the decision in &lt;i&gt;Aleynikov&lt;/i&gt; established an important, new limit for federal criminal liability under the EEA.&amp;nbsp;A person who steals proprietary intellectual property from an owner who uses that information solely for internal, commercial purposes does not violate the domestic provisions of the EEA.&amp;nbsp;(The foreign provisions of the EEA, which are more expansive, were not at issue in &lt;i&gt;Aleynikov&lt;/i&gt;.)&amp;nbsp;Yet if the same person takes intellectual property that the owner uses in a product that it produces for or makes available on domestic or foreign markets, then the thief runs afoul of the federal criminal law.&amp;nbsp;While logical, this internal/external or private/public distinction would seem to leave unprotected, at least under the domestic provisions of the EEA, some extremely valuable intellectual property that is critical to how owners operate their businesses and obtain competitive advantages.&amp;nbsp;&amp;nbsp; Stealing the source code for Goldman&amp;rsquo;s HFT system to aid a competitor company seems like a quintessential act of economic espionage, but according to the Second Circuit, it did not violate the EEA.&amp;nbsp;Ironically, it was precisely because Goldman closely guarded its computer program that the source code fell beyond the EEA&amp;rsquo;s scope.&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;&lt;u&gt;Wire and mail fraud&lt;/u&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;Finally, it merits mention that Aleynikov was not charged with wire or mail fraud in violation of 18 U.S.C. &amp;sect;&amp;sect; 1341 and 1343.&amp;nbsp;The mail and wire fraud statutes prohibit using the mail or &amp;ldquo;wires,&amp;rdquo; meaning telephones, e-mail, or other electronic communications, to conduct a &amp;ldquo;scheme to defraud&amp;rdquo; or &amp;ldquo;to obtain money or property by means of false or fraudulent pretenses.&amp;rdquo; &amp;nbsp;Both federal criminal statutes require the government to prove beyond a reasonable doubt that the defendant engaged in some intentional deception.&amp;nbsp;On its face, Aleynikov&amp;rsquo;s conduct did not necessarily involve any deceit or trickery.&amp;nbsp;He did not tell anyone at Goldman what he had done, but he also did not lie about it.&amp;nbsp;He did not masquerade as someone else to gain access to the HFT system, nor did he dupe Goldman into sharing its source code with him.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;That is not to say Aleynikov may not have been convicted of wire or mail fraud, if he had been charged with those offenses.&amp;nbsp;In contrast to the NSPA which limits &amp;ldquo;goods, wares [and] merchandise&amp;rdquo; to physical items, the mail and wire fraud statutes broadly define &amp;ldquo;property&amp;rdquo; to include purely intellectual property, such as computer programs or other confidential business information.&amp;nbsp;&lt;i&gt;See&lt;/i&gt; &lt;i&gt;Carpenter v. United States&lt;/i&gt;, 484 U.S. 19, 25-26 (1987); &lt;i&gt;United States v. Czubinski&lt;/i&gt;, 106 F.3d 1069, 1074 (1st Cir. 1997).&amp;nbsp;Thus, in &lt;i&gt;United States v. Martin&lt;/i&gt;, a somewhat similar case involving an employee who shared trade secrets with a competitor company, the First Circuit ruled that, by relaying confidential information in violation of her fiduciary duty to her employer and her signed non-disclosure and non-compete agreements, the defendant engaged in &amp;ldquo;false pretenses.&amp;rdquo;&amp;nbsp;On that basis, the appeals court affirmed the defendant&amp;rsquo;s convictions for mail and wire fraud.&amp;nbsp;&lt;i&gt;See also United States v. Wang&lt;/i&gt;, 898 F. Supp. 758 (D. Colo. 2005) (denying the defendant&amp;rsquo;s motion to dismiss the indictment in a wire fraud prosecution where the defendant had transmitted by wires, without proper authorization, confidential source code that belonged to his employer).&amp;nbsp;Now that the Second Circuit has closed certain doors to federal criminal prosecutions in intellectual property cases, the Justice Department may opt to proceed through a door that other courts have left open, charging defendants like Aleynikov with mail and wire fraud and arguing that, by violating agreements with their employers, they engaged in prohibited deceit.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;&lt;u&gt;Conclusion&lt;/u&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;If asked, most people would probably think that, if an employee brazenly steals valuable intellectual property from his or her employer to give to a competitor company (where the employee has accepted a new job), then that employee has committed a federal crime.&amp;nbsp;Not necessarily.&amp;nbsp;As the Second Circuit decision in &lt;i&gt;Aleynikov&lt;/i&gt; makes clear, federal criminal liability under the NSPA, EEA and CFAA will turn on specific, and somewhat surprising, factual questions.&amp;nbsp;For example, did the employee take the intangible intellectual property on a tangible device, like a disc, that belonged to his or her employer?&amp;nbsp;Was the intellectual property used internally or as part of a product that the company produced for sale?&amp;nbsp;Did the company authorize the employee to access the computer system in the first place?&amp;nbsp;Depending on the answers to these types of factual questions, conduct that is dishonest, unethical and inappropriate may, nevertheless, not be criminal.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 10pt"&gt;As much as things change, some things will remain the same:&amp;nbsp;the government will continue to prosecute the theft of intellectual property; defendants will continue to raise creative challenges to the criminal laws, and the courts will continue to wrestle with these issues, all as technology continues to evolve.&amp;nbsp;For Aleynikov, that legal process unfolded over the past three years since his arrest in July 2009, and it took a heavy personal toll.&amp;nbsp;Because he is a dual Russian and U.S. citizen, Aleynikov was deemed a &amp;ldquo;flight risk&amp;rdquo; and denied bail pending his appeal.&amp;nbsp;As a result, Aleynikov -- the father of three young children -- served more than two years in federal prison before the Second Circuit decided that he had not, in fact, broken the law.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/HNKxcF77ZW4" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/HNKxcF77ZW4/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/04/articles/government-enforcement/second-circuit-reverses-convictions-in-datatheft-prosecution-and-narrowly-interprets-federal-criminal-statutes-with-important-intellectual-property-implications/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">Computer Fraud and Abuse Act</category><category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category>
         <pubDate>Sat, 21 Apr 2012 14:42:06 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/04/articles/government-enforcement/second-circuit-reverses-convictions-in-datatheft-prosecution-and-narrowly-interprets-federal-criminal-statutes-with-important-intellectual-property-implications/</feedburner:origLink></item>
            <item>
         <title>Will Massachusetts Adopt the Uniform Trade Secrets Act?</title>
         <description>&lt;p&gt;by &lt;a href="http://www.foleyhoag.com/People/Attorneys/Bialas-Brian.aspx"&gt;Brian P. Bialas, Esq.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A &lt;a href="http://www.malegislature.gov/Bills/187/House/H00023"&gt;bill &lt;/a&gt;to adopt the Uniform Trade Secrets Act (&amp;ldquo;UTSA&amp;rdquo;) has been pending in the Massachusetts Legislature since late January. Forms of the UTSA have been adopted in 46 states, as well as the District of Columbia, Puerto Rico, and the U.S. Virgin Islands. Only New York, Texas, North Carolina, and Massachusetts have not adopted the UTSA.&lt;/p&gt;
&lt;p&gt;The bill would supersede the definitions, procedures, and remedies applied in Massachusetts chapter 93A actions (regulating unfair and deceptive trade practices) for trade secret misappropriation. The UTSA expands the definition of &amp;ldquo;trade secret&amp;rdquo; to include information that has not been &amp;ldquo;continuously used in one&amp;rsquo;s business.&amp;rdquo; It leaves in place contractual remedies (i.e., non-disclosure agreements) so long as, to the extent contracts rely on confidentiality of information, such confidentiality be determined according to the definition of &amp;ldquo;trade secret&amp;rdquo; in the UTSA. This addresses an anomaly in Massachusetts created by an overly restrictive definition of trade secrets which requires &amp;ldquo;continuous use&amp;rdquo; of the trade secret and employers&amp;rsquo; need to protect by contract &amp;ldquo;confidential information&amp;rdquo; that does not meet the restrictive definition.&lt;/p&gt;
&lt;p&gt;The last action on the bill was a hearing before the Massachusetts Joint Committee on the Judiciary on February 28, 2012. Testimony before the Committee and a copy of the bill with both official comments on the UTSA and comments specific to the version proposed in Massachusetts, which is slightly different, are available &lt;a href="http://www.securityprivacyandthelaw.com/uploads/file/UTSA Testimony.doc"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;A more detailed discussion of the USTA, and its impact on non-competes, is available on our &lt;a href="http://www.massachusettsnoncompetelaw.com/2012/04/articles/trade-secrets/will-massachusetts-adopt-the-uniform-trade-secrets-act/"&gt;Non-Compete blog&lt;/a&gt;.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/LYrLP9_tlyI" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/LYrLP9_tlyI/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/04/articles/recent-legislation-1/will-massachusetts-adopt-the-uniform-trade-secrets-act/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">Debate</category><category domain="http://www.securityprivacyandthelaw.com/articles">Legislation &amp; Regulation</category><category domain="http://www.securityprivacyandthelaw.com/tags">Noncompete</category><category domain="http://www.securityprivacyandthelaw.com/tags">Noncompetes</category><category domain="http://www.securityprivacyandthelaw.com/tags">Trade Secrets</category><category domain="http://www.securityprivacyandthelaw.com/tags">legislation</category>
         <pubDate>Fri, 06 Apr 2012 08:35:04 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/04/articles/recent-legislation-1/will-massachusetts-adopt-the-uniform-trade-secrets-act/</feedburner:origLink></item>
            <item>
         <title>Good Advice that Bears Repeating:  Toughen Up Your Passwords!</title>
         <description>&lt;p&gt;In an article that repeats a &lt;a href="http://www.securityprivacyandthelaw.com/2011/02/articles/medical-information/you-call-that-a-password-passwords-used-to-protect-personal-health-information-in-clinical-trials-are-cracked-more-than-90-of-the-time/"&gt;common theme in this space&lt;/a&gt;, &lt;a href="http://www.economist.com/node/21550763"&gt;this week's Economist &lt;/a&gt;talks about how researchers are trying to help ordinary people toughen up their passwords.&amp;nbsp; But despite the efforts of these researchers, the article's conclusion is a gloomy one:&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;The upshot is that there is probably no right answer. All security is irritating (ask anyone who flies regularly), and there is a constant tension between people&amp;rsquo;s desire to be safe and their desire for things to be simple. While that tension persists, the hacker will always get through.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/lK6kC2q3rgc" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/lK6kC2q3rgc/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/03/articles/cybersecurity-cybercrime/good-advice-that-bears-repeating-toughen-up-your-passwords/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/articles">Cybersecurity &amp; Cybercrime</category><category domain="http://www.securityprivacyandthelaw.com/articles">Data Breach</category><category domain="http://www.securityprivacyandthelaw.com/tags">Economist</category><category domain="http://www.securityprivacyandthelaw.com/articles">Financial Industry Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/articles">Healthcare Industry Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/articles">Identity Theft</category><category domain="http://www.securityprivacyandthelaw.com/articles">Retail Industry &amp; Customer Information Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/articles">Security Programs &amp; Policies</category><category domain="http://www.securityprivacyandthelaw.com/tags">computer</category><category domain="http://www.securityprivacyandthelaw.com/tags">password</category><category domain="http://www.securityprivacyandthelaw.com/tags">security</category>
         <pubDate>Mon, 26 Mar 2012 14:48:35 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/03/articles/cybersecurity-cybercrime/good-advice-that-bears-repeating-toughen-up-your-passwords/</feedburner:origLink></item>
            <item>
         <title>FTC Releases Final Report:  "Protecting Consumer Privacy in an Era of Rapid Change:  Recommendations for Businesses and Policymakers"</title>
         <description>&lt;p&gt;FTC has today, at last, released the final version of its &lt;a href="http://www.securityprivacyandthelaw.com/uploads/file/Protecting%20Consumer%20Privacy%20in%20an%20Era%20of%20Rapid%20Change_%20A%20Proposed%20Framework%20for%20Businesses%20and%20Policymakers.pdf"&gt;original 2010 Report &lt;/a&gt;&amp;mdash; &lt;a href="http://ftc.gov/os/2012/03/120326privacyreport.pdf"&gt;&amp;quot;Protecting Consumer Privacy in an Era of Rapid Change: Recommendations for Businesses and Policymakers.&amp;quot;&amp;nbsp; &lt;/a&gt;As we have &lt;a href="http://www.securityprivacyandthelaw.com/2010/12/articles/retail-customer-information-sp/ftc-proposes-privacy-framework-that-will-impact-the-business-model-of-all-online-and-mobile-advertising-companies/"&gt;discussed previously&lt;/a&gt;, comments on the draft report were taken through January 31, 2011 and the final report had been expected in 2011.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The &lt;a href="http://www.ftc.gov"&gt;FTC &lt;/a&gt;received over 450 comments from businesses, privacy advocates, and consumers and claims that the final Report retains the basic principles outlined previously, but claiming it makes several important refinements.&amp;nbsp; There's also a brief new &lt;a href="http://onguardonline.gov/blog/ftc-releases-final-privacy-report"&gt;video &lt;/a&gt;explaining the FTC's positions.&amp;nbsp; Here are the key take-aways from the final report:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Privacy by Design. Companies should build privacy protections into their everyday business practices. That includes limiting data collection and retention, securing the information they hold on to, safely disposing of what they no longer need, and implementing reasonable measures to ensure information is accurate.&lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;Simplified Choice. Companies should give consumers a choice at a time and in a context that matters to people. The preliminary report noted that choice shouldn&amp;rsquo;t be necessary for certain &amp;ldquo;commonly accepted practices.&amp;rdquo; The final Report concludes that choice needn&amp;rsquo;t be provided for data practices that people would expect, given the context of the transaction, the company&amp;rsquo;s relationship with the consumer, or as required or specifically authorized by law.&lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;Do Not Track:&amp;nbsp; The Report also reaffirms the Commission&amp;rsquo;s strong support for Do Not Track.&lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;Improved transparency. Companies should increase the transparency of their data practices by&amp;nbsp;developing clearer, more standardized privacy disclosures and could give people reasonable access to their information. &lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;Exemption of&amp;nbsp;small businesses: &amp;nbsp;To minimize the effect on smaller companies, the final framework doesn&amp;rsquo;t apply to them if they collect only non-sensitive data from fewer than 5,000 consumers a year, provided they don&amp;rsquo;t share the data with third parties.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Most interesting to me is the Dissenting Statement of &lt;a href="http://www.ftc.gov/commissioners/rosch/index.shtml"&gt;Commissioner J. Thomas Rosch&lt;/a&gt;, in which he makes several interesting points:&lt;/p&gt;
&lt;ol&gt;
    &lt;li&gt;&amp;quot;First, the Report is rooted in its insistence that the &amp;ldquo;unfair&amp;rdquo; prong, rather than the &amp;ldquo;deceptive&amp;rdquo; prong, of the Commission&amp;rsquo;s Section 5 consumer protection statute, should govern information gathering practices (including &amp;ldquo;tracking&amp;rdquo;). &amp;ldquo;Unfairness&amp;rdquo; is an elastic and elusive concept. What is &amp;ldquo;unfair&amp;rdquo; is in the eye of the beholder.&amp;quot;&lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;&amp;quot;Second, the current self-regulation and browser mechanisms for implementing Do Not Track solutions may have advanced since the issuance of the preliminary staff Report&amp;quot; and the Report does not adequately take account of this change.&lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;&amp;quot;I am concerned that &amp;quot;opt-in&amp;rdquo; will necessarily be selected as the de facto method of consumer choice for a wide swath of entities that have a first-party relationship with consumers but who can potentially track consumers&amp;rsquo; activities across unrelated websites, under circumstances where it is unlikely, because of the &amp;ldquo;context&amp;rdquo; (which is undefined) for such tracking to be &amp;ldquo;consistent&amp;rdquo; (which is undefined) with that first-party relationship: 1) companies with multiple lines of business that allow data collection in different contexts (such as Google); 2) &amp;ldquo;social networks,&amp;rdquo; (such as Facebook and Twitter), which could potentially use &amp;ldquo;cookies,&amp;rdquo; &amp;ldquo;plug-ins,&amp;rdquo; applications, or other mechanisms to track a consumer&amp;rsquo;s activities across the Internet; and 3) &amp;ldquo;retargeters,&amp;rdquo; (such as Amazon or Pacers), which include a retailer who delivers an ad on a third-party website based on the consumer&amp;rsquo;s previous activity on the retailer&amp;rsquo;s website.&lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;&amp;quot;I question the Report&amp;rsquo;s apparent mandate that ISPs, with respect to uses of deep packet inspection, be required to use opt-in choice.&amp;quot;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/Fnmv1Qlps50" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/Fnmv1Qlps50/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/03/articles/government-enforcement/ftc-releases-final-report-protecting-consumer-privacy-in-an-era-of-rapid-change-recommendations-for-businesses-and-policymakers/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">Do Not Track</category><category domain="http://www.securityprivacyandthelaw.com/tags">FTC</category><category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category><category domain="http://www.securityprivacyandthelaw.com/articles">Legislation &amp; Regulation</category><category domain="http://www.securityprivacyandthelaw.com/articles">Retail Industry &amp; Customer Information Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/tags">consumer</category><category domain="http://www.securityprivacyandthelaw.com/tags">privacy</category><category domain="http://www.securityprivacyandthelaw.com/tags">report</category>
         <pubDate>Mon, 26 Mar 2012 11:14:01 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/03/articles/government-enforcement/ftc-releases-final-report-protecting-consumer-privacy-in-an-era-of-rapid-change-recommendations-for-businesses-and-policymakers/</feedburner:origLink></item>
            <item>
         <title>Ponemon Institute's 2011 Cost of Data Breach Study Released</title>
         <description>&lt;p&gt;The annual &lt;a href="http://www.ponemon.org/index.php"&gt;Ponemon Institute report on data breaches &lt;/a&gt;has been released.&amp;nbsp; Among the notable conclusions are the following:&lt;/p&gt;
&lt;p&gt;&amp;bull; The average cost of data breach declined.&lt;/p&gt;
&lt;p&gt;&amp;bull;&amp;nbsp;Customers remained with companies&amp;nbsp;following the data breach.&lt;/p&gt;
&lt;p&gt;&amp;bull; Negligent insiders and malicious attacks were the main causes of data breach.&lt;/p&gt;
&lt;p&gt;&amp;bull; Lost business costs from breaches&amp;nbsp;declined.&lt;/p&gt;
&lt;p&gt;&amp;bull; Detection and escalation costs declined but notification costs increased.&lt;/p&gt;
&lt;p&gt;Taken together, these factors suggest that the process of dealing with data breach is maturing and becoming routinized.&amp;nbsp; Companies know better how to deal with breaches, hence the decreased costs, and improved customer retention.&amp;nbsp; This improved loyalty also is reflected in increased notification costs:&amp;nbsp; companies are spending more but have more to show&amp;nbsp;for&amp;nbsp;it.&amp;nbsp; It would appear we are heading to a state of affairs in which breaches are routine, expected and dealt with.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/eDGzqIYo-Dw" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/eDGzqIYo-Dw/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/03/articles/data-breach-1/ponemon-institutes-2011-cost-of-data-breach-study-released/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/articles">Data Breach</category><category domain="http://www.securityprivacyandthelaw.com/articles">Retail Industry &amp; Customer Information Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/articles">Security Programs &amp; Policies</category>
         <pubDate>Sun, 25 Mar 2012 11:52:06 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/03/articles/data-breach-1/ponemon-institutes-2011-cost-of-data-breach-study-released/</feedburner:origLink></item>
            <item>
         <title>New Case Highlights Split of Authority Interpreting the Computer Fraud and Abuse Act</title>
         <description>&lt;p&gt;&lt;span&gt;by &lt;a href="http://www.foleyhoag.com/People/Attorneys/Bialas-Brian.aspx"&gt;Brian P.&amp;nbsp;Bialas&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Employers increasingly are suing former employees who have left to join or form competing companies using the civil remedies available under the &lt;a href="http://www.law.cornell.edu/uscode/text/18/1030"&gt;Computer Fraud and Abuse Act (&amp;ldquo;CFAA&amp;rdquo;), 18 U.S.C. &amp;sect; 1030&lt;/a&gt;.&amp;nbsp;They use the CFAA to prevent their former employees from using sensitive information obtained from the former employer&amp;rsquo;s computer system.&amp;nbsp;The scope of the CFAA, however, is subject to hot debate among the federal courts, as highlighted by a recent case from the District of Minnesota.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; In &lt;a href="http://www.securityprivacyandthelaw.com/uploads/file/Walsh Bishop v_ O'Brien.pdf"&gt;&lt;u&gt;Walsh Bishop Associates, Inc. v. O&amp;rsquo;Brien&lt;/u&gt;, Civil Action No. 11-2673 (DSD/AJB), 2012 WL 669069 (D. Minn. Feb. 28, 2012), &lt;/a&gt;the court interpreted a provision of the CFAA, &lt;a href="http://www.law.cornell.edu/uscode/text/18/1030"&gt;18 U.S.C. &amp;sect; 1030&lt;/a&gt;(a)(2)(C), which subjects an individual who &amp;ldquo;intentionally accesses a computer without authorization or exceeds authorized access, and thereby obtains information from any protected computer&amp;rdquo; to civil liability should the plaintiff meet certain conditions.&amp;nbsp;In particular, the court had to determine the scope of the phrase &amp;ldquo;exceeds authorized access,&amp;rdquo; which the CFAA defines as &amp;ldquo;to access a computer with authorization and to use such access to obtain or alter information in the computer that the accesser is not entitled so to obtain or alter.&amp;rdquo;&amp;nbsp;18 U.S.C. &amp;sect; 1030(e)(6).&amp;nbsp;The plaintiff argued that a person exceeds authorized access by accessing information in order to use it in a manner contrary to an employer&amp;rsquo;s interests and use policies.&amp;nbsp;The &lt;u&gt;O&amp;rsquo;Brien&lt;/u&gt; court, however, concluded, among other things, that subsection (a)(2) is not based on use of information, but rather access to information.&amp;nbsp;Plaintiff&amp;rsquo;s interpretation therefore could not be correct and the court had to focus on whether the defendants accessed information that they were forbidden to access instead of how defendants intended to use the information they had obtained.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Other courts, including the District of Massachusetts, have come to a different conclusion regarding this language in the CFAA.&amp;nbsp;In &lt;a href="http://www.securityprivacyandthelaw.com/uploads/file/Guest-Tek v  Pullen.pdf"&gt;&lt;u&gt;Guest-Tek Interactive Entertainment Inc. v. Pullen&lt;/u&gt;, 665 F. Supp. 2d 42 (D. Mass. 2009&lt;/a&gt;), Judge Gorton analyzed a different provision of the CFAA that also included both the &amp;ldquo;without authorization&amp;rdquo; and &amp;ldquo;exceeds authorized access&amp;rdquo; language.&amp;nbsp;&lt;u&gt;See&lt;/u&gt; 18 U.S.C. &amp;sect; 1030(a)(4).&amp;nbsp;The defendants argued that the CFAA applies only to those lacking initial authorization and not those who subsequently misuse or misappropriate information.&amp;nbsp;The plaintiff in response argued that the employee defendant&amp;rsquo;s alleged breach of his fiduciary duty of loyalty to the plaintiff (by copying files and secretly planning a competitive venture while still employed) effectively extinguished his authorization to access plaintiff&amp;rsquo;s computers.&amp;nbsp;The employee defendant&amp;rsquo;s initial authorization to access the plaintiff&amp;rsquo;s confidential information was premised on the agency relationship between the parties, the plaintiff argued, and therefore when the employee breached his duty of loyalty he ended that relationship and constructively terminated his authorization to access the plaintiff&amp;rsquo;s files.&amp;nbsp;Judge Gorton agreed with the plaintiff.&amp;nbsp;He determined that the First Circuit advocated a broader reading of the CFAA in &lt;a href="http://www.ca1.uscourts.gov/cgi-bin/getopn.pl?OPINION=01-2001.01A"&gt;&lt;u&gt;EF Cultural Travel BV v. Explorica, Inc.&lt;/u&gt;, 274 F.3d 577 (1st Cir. 2001&lt;/a&gt;).&amp;nbsp;In that case, the court &amp;ldquo;upheld a CFAA claim against employees who had collected pricing information from their former employer&amp;rsquo;s website in order to develop a competing entity with lower prices.&amp;rdquo;&amp;nbsp;&lt;u&gt;Guest-Tek&lt;/u&gt;, 665 F. Supp. 2d at 45. &amp;nbsp;The First Circuit found &amp;ldquo;that the former employees&amp;rsquo; reliance on [plaintiff]&amp;rsquo;s pricing information reeked of use&amp;mdash;and indeed, abuse&amp;mdash;of proprietary information that goes beyond any authorized use of [plaintiff]&amp;rsquo;s website.&amp;rdquo;&amp;nbsp;&lt;u&gt;Id.&lt;/u&gt; (quotation and brackets omitted).&amp;nbsp;The First Circuit&amp;rsquo;s analysis of the employees&amp;rsquo; &amp;ldquo;authorized use&amp;rdquo; and &amp;ldquo;abuse&amp;rdquo; of the plaintiff&amp;rsquo;s proprietary information in &lt;u&gt;Explorica&lt;/u&gt;, Judge Gorton ruled, undercut the &lt;u&gt;Guest-Tek&lt;/u&gt; defendants&amp;rsquo; plain language argument&amp;mdash;the type of argument the court accepted in &lt;u&gt;O&amp;rsquo;Brien&lt;/u&gt;. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; These two cases show that employers can use the CFAA when employees depart to join or form competing companies, but the CFAA&amp;rsquo;s usefulness may be limited by the case law in the jurisdiction in which the employer sues.&amp;nbsp;Employers therefore should consider where they can sue and the state of the law in those jurisdictions before filing suit.&amp;nbsp;These cases also call attention to a split in case law that eventually may require resolution by the Supreme Court. &lt;/span&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/gHl9VKPWYXg" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/gHl9VKPWYXg/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/03/articles/government-enforcement/new-case-highlights-split-of-authority-interpreting-the-computer-fraud-and-abuse-act/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">CFAA</category><category domain="http://www.securityprivacyandthelaw.com/tags">Computer Fraud and Abuse Act</category><category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category><category domain="http://www.securityprivacyandthelaw.com/tags">Guest-Tek Interactive Entertainment Inc. v. Pullen</category><category domain="http://www.securityprivacyandthelaw.com/articles">Legislation &amp; Regulation</category><category domain="http://www.securityprivacyandthelaw.com/articles">Retail Industry &amp; Customer Information Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/tags">Walsh Bishop Associates, Inc. v. O'Brien</category>
         <pubDate>Sun, 18 Mar 2012 18:43:18 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/03/articles/government-enforcement/new-case-highlights-split-of-authority-interpreting-the-computer-fraud-and-abuse-act/</feedburner:origLink></item>
            <item>
         <title>Phyisican Medical Identify Theft -- A Growing Problem?</title>
         <description>&lt;p&gt;A &lt;a href="http://jama.ama-assn.org/content/307/5/459/suppl/DC1"&gt;recent issue of the Journal of the American Medical Association &lt;/a&gt;takes on the issue of physician medical identify theft; here's the abstract:&amp;nbsp;&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;It took several months for one physician to learn that she was a victim of medical identity theft. This realization occurred after patients reported that her name was on their Medicare Summary Notices although they had never seen her. A fraudulent clinical practice had enrolled in Medicare using her name without her knowledge. Another physician had retired from clinical practice but decided to work part-time. Nearly 2 years after sending out job applications, he was asked by Medicare to return more than $350 000 in overpayments made to a practice he had interviewed with but never joined. The Department of Treasury began to garnish his Social Security payments for unpaid debts.&lt;/p&gt;
&lt;p&gt;There's also an interesting interview with one of the authors, who holds an M.D. and J.D., discussing the consequences for physicians and their patients.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/rnA1Iwl-eNg" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/rnA1Iwl-eNg/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/03/articles/identity-theft-1/phyisican-medical-identify-theft-a-growing-problem/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/articles">Healthcare Industry Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/articles">Identity Theft</category><category domain="http://www.securityprivacyandthelaw.com/tags">JAMA</category><category domain="http://www.securityprivacyandthelaw.com/tags">identity</category><category domain="http://www.securityprivacyandthelaw.com/tags">medical</category><category domain="http://www.securityprivacyandthelaw.com/tags">theft</category>
         <pubDate>Sun, 18 Mar 2012 18:35:29 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/03/articles/identity-theft-1/phyisican-medical-identify-theft-a-growing-problem/</feedburner:origLink></item>
            <item>
         <title>$1.5 Million Settlement of First HIPAA Enforcement Action Resulting from HITECH Breach Notification Rule</title>
         <description>&lt;p&gt;The trend toward increasingly large health information breach settlements has continued with &lt;a href="http://www.hhs.gov/news/press/2012pres/03/20120313a.html"&gt;yesterday's announcement &lt;/a&gt;that&lt;a href="http://www.bcbst.com"&gt;Blue Cross Blue Shield of Tennessee &lt;/a&gt;(BCBST) has agreed to pay the U.S. Department of Health and Human Services (&lt;a href="http://www.hhs.gov"&gt;HHS&lt;/a&gt;) $1,500,000 to settle potential violations of&amp;nbsp;HIPAA's Privacy and Security Rules, HHS's Office of Civil Rights. BCBST also agreed to a &lt;a href="http://www.hhs.gov/ocr/privacy/hipaa/enforcement/examples/"&gt;corrective action plan&lt;/a&gt; to address gaps in its HIPAA compliance program. The enforcement action is the first resulting from a breach report required by the HITECH Act's Breach Notification Rule.&lt;/p&gt;
&lt;p&gt;The investigation started with a notice submitted by BCBST to HHS reporting that 57 unencrypted computer hard drives were stolen from a leased facility in Tennessee. The drives contained the PHI of over 1 million individuals, including member names, Social Security numbers, diagnosis codes, dates of birth, and health plan identification numbers. OCR&amp;rsquo;s investigation indicated BCBST failed to implement appropriate administrative safeguards to adequately protect information remaining at the leased facility by not performing the required security evaluation in response to operational changes. In addition, OCR&amp;nbsp;found&amp;nbsp;a failure to implement appropriate physical safeguards by not having adequate facility access controls; both of these safeguards are required by the HIPAA Security Rule.&lt;/p&gt;
&lt;p&gt;In addition to the $1,500,000 settlement, the agreement requires BCBST to review, revise, and maintain its privacy and security policies and procedures, to conduct regular and robust trainings for all BCBST employees covering employee responsibilities under HIPAA, and to perform monitor reviews to ensure BCBST compliance with the &lt;a href="http://www.hhs.gov/ocr/privacy/hipaa/enforcement/examples/"&gt;corrective action plan&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/6OrBEUdvLdM" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/6OrBEUdvLdM/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/03/articles/data-breach-1/15-million-settlement-of-first-hipaa-enforcement-action-resulting-from-hitech-breach-notification-rule/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">$1.5 million</category><category domain="http://www.securityprivacyandthelaw.com/tags">Blue Cross Blue Shield of Tennessee</category><category domain="http://www.securityprivacyandthelaw.com/tags">Corrective Action Plan</category><category domain="http://www.securityprivacyandthelaw.com/articles">Data Breach</category><category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category><category domain="http://www.securityprivacyandthelaw.com/tags">HHS</category><category domain="http://www.securityprivacyandthelaw.com/tags">HIPAA</category><category domain="http://www.securityprivacyandthelaw.com/tags">HITECH</category><category domain="http://www.securityprivacyandthelaw.com/articles">Healthcare Industry Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/tags">OCR</category><category domain="http://www.securityprivacyandthelaw.com/tags">PHI</category><category domain="http://www.securityprivacyandthelaw.com/tags">Social Security Numbers</category><category domain="http://www.securityprivacyandthelaw.com/tags">breach</category>
         <pubDate>Wed, 14 Mar 2012 07:50:00 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/03/articles/data-breach-1/15-million-settlement-of-first-hipaa-enforcement-action-resulting-from-hitech-breach-notification-rule/</feedburner:origLink></item>
            <item>
         <title>Join Us on April 4 for a Discussion on FATCA Compliance, and the Latest SEC and Massachusetts Guidance on Social Media Use by Investment Advisers</title>
         <description>&lt;p&gt;On April 4, &lt;a href="http://www.foleyhoag.com"&gt;Foley Hoag &lt;/a&gt;will be hosting&amp;nbsp;a discussion on &lt;a href="http://www.irs.gov/businesses/corporations/article/0,,id=236667,00.html"&gt;FATCA &lt;/a&gt;compliance, and the &lt;a href="http://www.securityprivacyandthelaw.com/2012/01/articles/cybersecurity-cybercrime/inside-counsel-magazine-revisits-secs-cybersecurity-guidance/"&gt;latest SEC and Massachusetts guidance on social media use by investment advisers&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;
&lt;table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="799" style="width: 399.5pt; mso-cellspacing: 0in; mso-yfti-tbllook: 1184; mso-padding-alt: 0in 0in 0in 0in"&gt;
    &lt;tbody&gt;
        &lt;tr style="height: 63pt; mso-yfti-irow: 0; mso-yfti-firstrow: yes"&gt;
            &lt;td valign="top" colspan="4" style="border-bottom: #f0f0f0; border-left: #f0f0f0; padding-bottom: 0in; background-color: transparent; padding-left: 0in; padding-right: 0in; height: 63pt; border-top: #f0f0f0; border-right: #f0f0f0; padding-top: 6pt"&gt;
            &lt;p class="date" style="margin: auto 0in"&gt;&lt;font size="3"&gt;&lt;strong&gt;&lt;span class="placeheader1"&gt;&lt;font color="#990066"&gt;FOLEY HOAG LLP&lt;/font&gt;&lt;/span&gt; |&amp;nbsp;APRIL 4, 2012&lt;o:p&gt;&lt;/o:p&gt;&lt;/strong&gt;&lt;/font&gt;&lt;/p&gt;
            &lt;p class="titles" style="margin: auto 0in"&gt;&lt;strong&gt;&lt;font size="5"&gt;Part of the Operational Risk Breakfast Club's Quarterly Series&lt;o:p&gt;&lt;/o:p&gt;&lt;/font&gt;&lt;/strong&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr style="height: 357pt; mso-yfti-irow: 1; mso-yfti-lastrow: yes"&gt;
            &lt;td valign="top" width="789" style="border-bottom: #f0f0f0; border-left: #f0f0f0; padding-bottom: 0in; background-color: transparent; padding-left: 0in; width: 394.5pt; padding-right: 0in; height: 357pt; border-top: #f0f0f0; border-right: #f0f0f0; padding-top: 0in"&gt;
            &lt;p style="line-height: 16.5pt"&gt;&lt;span class="maincontent"&gt;&lt;span style="font-family: &amp;quot;Georgia&amp;quot;,&amp;quot;serif&amp;quot;; color: black; font-size: 10pt"&gt;The Operational Risk Breakfast Club provides the opportunity for senior investment management professionals to mix informally and gain advantages by gathering insights and information regarding key developments in the industry. The meetings are sponsored by Kinetic Partners and Foley Hoag on a quarterly basis. &lt;/span&gt;&lt;/span&gt;&lt;span style="font-family: &amp;quot;Georgia&amp;quot;,&amp;quot;serif&amp;quot;; color: black; font-size: 10pt"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;p style="line-height: 16.5pt"&gt;&lt;strong&gt;&lt;span style="font-family: &amp;quot;Georgia&amp;quot;,&amp;quot;serif&amp;quot;; color: black; font-size: 10pt"&gt;Speakers:&lt;/span&gt;&lt;/strong&gt;&lt;b&gt;&lt;span style="font-family: &amp;quot;Georgia&amp;quot;,&amp;quot;serif&amp;quot;; color: black; font-size: 10pt"&gt;&lt;br /&gt;
            &lt;/span&gt;&lt;/b&gt;&lt;span class="maincontent"&gt;&lt;span style="font-family: &amp;quot;Georgia&amp;quot;,&amp;quot;serif&amp;quot;; color: black; font-size: 10pt"&gt;Donald Babbitt, Kinetic Partners &lt;/span&gt;&lt;/span&gt;&lt;span style="font-family: &amp;quot;Georgia&amp;quot;,&amp;quot;serif&amp;quot;; color: black; font-size: 10pt"&gt;&lt;br /&gt;
            &lt;span class="maincontent"&gt;&lt;a href="http://response.foleyhoag.com/rs/ct.aspx?ct=24F76814DFAE4EE0CCD189AFD62B911A91BE4194F8A167B734C5554410DCE620FF44178FDECD5A863F43771AB95B44FB99A4B2555C160F0FEA854F11A4A13D83CC4FDEE7181BD9A70B5222693DDD69F659B43159A62FDC30610CB305B55A32BA28AB8F8C9EDF3"&gt;&lt;span style="color: #0073cf"&gt;Kip Cawley&lt;/span&gt;&lt;/a&gt;, Foley Hoag LLP &lt;/span&gt;&lt;br /&gt;
            &lt;span class="maincontent"&gt;Terence Coppinger, Deloitte Tax LLP &lt;/span&gt;&lt;/span&gt;&lt;span class="maincontent"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;p style="line-height: 16.5pt"&gt;&lt;span style="font-family: &amp;quot;Georgia&amp;quot;,&amp;quot;serif&amp;quot;; color: black; font-size: 10pt"&gt;&amp;nbsp;&lt;/span&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;
            &lt;p style="line-height: 16.5pt"&gt;&lt;span style="font-family: &amp;quot;Georgia&amp;quot;,&amp;quot;serif&amp;quot;; color: black; font-size: 10pt"&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;p style="line-height: 16.5pt"&gt;&lt;span style="font-family: &amp;quot;Georgia&amp;quot;,&amp;quot;serif&amp;quot;; color: black; font-size: 10pt"&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;p style="line-height: 16.5pt"&gt;&lt;span style="font-family: &amp;quot;Georgia&amp;quot;,&amp;quot;serif&amp;quot;; color: black; font-size: 10pt"&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;p style="line-height: 16.5pt"&gt;&lt;span style="font-family: &amp;quot;Georgia&amp;quot;,&amp;quot;serif&amp;quot;; color: black; font-size: 10pt"&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td valign="top" width="23" style="border-bottom: #f0f0f0; border-left: #f0f0f0; padding-bottom: 0in; background-color: transparent; padding-left: 0in; width: 11.25pt; padding-right: 0in; height: 357pt; border-top: #f0f0f0; border-right: #b4b5b8 1pt solid; padding-top: 0in; mso-border-right-alt: solid #B4B5B8 .75pt"&gt;
            &lt;p class="MsoNormal" style="margin: 0in 0in 0pt"&gt;&lt;span style="mso-fareast-font-family: 'Times New Roman'"&gt;&lt;font size="3"&gt;&lt;font face="Times New Roman"&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/font&gt;&lt;/font&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td valign="top" width="23" style="border-bottom: #f0f0f0; border-left: #f0f0f0; padding-bottom: 0in; background-color: transparent; padding-left: 0in; width: 11.25pt; padding-right: 0in; height: 357pt; border-top: #f0f0f0; border-right: #f0f0f0; padding-top: 0in"&gt;
            &lt;p class="MsoNormal" style="margin: 0in 0in 0pt"&gt;&lt;span style="mso-fareast-font-family: 'Times New Roman'"&gt;&lt;font size="3"&gt;&lt;font face="Times New Roman"&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/font&gt;&lt;/font&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td valign="top" width="309" style="border-bottom: #f0f0f0; border-left: #f0f0f0; padding-bottom: 0in; background-color: transparent; padding-left: 0in; width: 154.5pt; padding-right: 0in; height: 357pt; border-top: #f0f0f0; border-right: #f0f0f0; padding-top: 9pt"&gt;
            &lt;div align="center"&gt;
            &lt;table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="350" height="453" style="width: 174.75pt; mso-cellspacing: 0in; mso-yfti-tbllook: 1184; mso-padding-alt: 6.0pt 6.0pt 6.0pt 6.0pt"&gt;
                &lt;tbody&gt;
                    &lt;tr style="height: 52.5pt; mso-yfti-irow: 0; mso-yfti-firstrow: yes; mso-yfti-lastrow: yes"&gt;
                        &lt;td style="border-bottom: #f0f0f0; border-left: #f0f0f0; padding-bottom: 6pt; background-color: transparent; padding-left: 6pt; padding-right: 7.5pt; height: 52.5pt; border-top: #f0f0f0; border-right: #f0f0f0; padding-top: 6pt"&gt;
                        &lt;p style="line-height: 13.5pt"&gt;&lt;b&gt;&lt;span style="font-family: &amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: #999999; font-size: 8pt"&gt;Wednesday, April 4, 2012&lt;br /&gt;
                        &lt;span class="datetimeinfo1"&gt;Registration: 8:30 a.m.&lt;/span&gt;&lt;br /&gt;
                        &lt;span class="datetimeinfo1"&gt;Program: 9:00 a.m. - 10:00 a.m.&lt;/span&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
                        &lt;p class="location" style="margin: auto 0in"&gt;&lt;font size="2"&gt;&lt;font color="#999999"&gt;&lt;font face="Verdana"&gt;&lt;strong&gt;LOCATION&lt;br /&gt;
                        &lt;/strong&gt;&lt;span class="locationsubtext1"&gt;Foley Hoag LLP&lt;/span&gt;&lt;/font&gt;&lt;/font&gt;&lt;/font&gt;&lt;span style="font-weight: normal"&gt;&lt;br /&gt;
                        &lt;font size="2"&gt;&lt;font color="#999999"&gt;&lt;font face="Verdana"&gt;&lt;span class="locationsubtext1"&gt;Seaport West&lt;/span&gt;&lt;br /&gt;
                        &lt;span class="locationsubtext1"&gt;155 Seaport Boulevard&lt;/span&gt;&lt;br /&gt;
                        &lt;span class="locationsubtext1"&gt;16th Floor&lt;/span&gt;&lt;br /&gt;
                        &lt;span class="locationsubtext1"&gt;boston, MA 02210&lt;/span&gt;&lt;/font&gt;&lt;/font&gt;&lt;/font&gt;&lt;/span&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;
                        &lt;p class="MsoNormal" style="line-height: 13.5pt; margin: 0in 0in 0pt; vertical-align: middle"&gt;&lt;span style="font-family: &amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: #999999; font-size: 8pt; mso-fareast-font-family: 'Times New Roman'"&gt;&lt;a href="http://response.foleyhoag.com/rs/ct.aspx?ct=24F76814DFAE4EE0CCD189AFD62B911A91BE4194F8A167B734C5554410DCE620FF44178FDECD5A863F43771EB45172FE8EE6DC6E4E1F1402EA8F125F94B0324"&gt;&lt;font color="#999999" size="2"&gt;&lt;img id="_x0000_i1025" border="0" alt="Map It" style="border-bottom: 0px solid; border-left: 0px solid; border-top: 0px solid; border-right: 0px solid" src="http://response.foleyhoag.com/reaction/images/map_it_icon.gif" /&gt;&lt;/font&gt;&lt;/a&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;
                        &lt;p style="line-height: 13.5pt"&gt;&lt;b&gt;&lt;span style="font-family: &amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: #999999; font-size: 8pt"&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
                        &lt;p style="line-height: 13.5pt"&gt;&lt;b&gt;&lt;span style="font-family: &amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: #999999; font-size: 8pt"&gt;&lt;img id="_x0000_i1026" border="0" alt="Foley Hoag logo" style="width: 169px; height: 62px" src="http://response.foleyhoag.com/rs/emsimages/FH_logo.gif" /&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
                        &lt;p style="line-height: 13.5pt"&gt;&lt;b&gt;&lt;span style="font-family: &amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: #999999; font-size: 8pt"&gt;&lt;img id="_x0000_i1027" border="0" alt="Kinetic Partners logo" style="width: 209px; height: 42px" src="http://response.foleyhoag.com/rs/emsimages/KInetic_Partners_logo.gif" /&gt;&lt;br /&gt;
                        &lt;br /&gt;
                        &lt;/span&gt;&lt;/b&gt;&lt;b&gt;&lt;span style="font-family: &amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: #6699cc; font-size: 8pt"&gt;&lt;a target="_blank" href="http://response.foleyhoag.com/rs/ct.aspx?ct=24F76814DFAE4EE0CCD189AFD62B911A91BE4194F8A167B734C047404ED5E73FFF13198FD3CF0D8D3F4F3F64BF5B59B88EEE92425C10120FA0AE6F7982AE1A8ECE53DDC503198FB109583C7511CB718B39B4016B833ADA301E54F16E8C0F23A764E4938"&gt;&lt;img id="_x0000_i1028" border="0" alt="" src="http://response.foleyhoag.com/reaction/images/RSVP_button.gif" /&gt;&lt;/a&gt;&lt;/span&gt;&lt;/b&gt;&lt;b&gt;&lt;span style="font-family: &amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;; color: #999999; font-size: 8pt"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
                        &lt;/td&gt;
                    &lt;/tr&gt;
                &lt;/tbody&gt;
            &lt;/table&gt;
            &lt;/div&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
    &lt;/tbody&gt;
&lt;/table&gt;
&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/YTKkNC6cawM" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/YTKkNC6cawM/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/03/articles/recent-legislation-1/join-us-on-april-4-for-a-discussion-on-fatca-compliance-and-the-latest-sec-and-massachusetts-guidance-on-social-media-use-by-investment-advisers/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">FACTA</category><category domain="http://www.securityprivacyandthelaw.com/articles">Financial Industry Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category><category domain="http://www.securityprivacyandthelaw.com/articles">Legislation &amp; Regulation</category><category domain="http://www.securityprivacyandthelaw.com/tags">SEC</category><category domain="http://www.securityprivacyandthelaw.com/tags">investment advisors</category><category domain="http://www.securityprivacyandthelaw.com/tags">social media</category>
         <pubDate>Mon, 12 Mar 2012 07:28:33 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/03/articles/recent-legislation-1/join-us-on-april-4-for-a-discussion-on-fatca-compliance-and-the-latest-sec-and-massachusetts-guidance-on-social-media-use-by-investment-advisers/</feedburner:origLink></item>
            <item>
         <title>Breaking Down the White House Privacy Framework--a Video Blog</title>
         <description>&lt;p&gt;&lt;span style="font-size: xx-small"&gt;Here is a &lt;/span&gt;&lt;a href="http://lxbn.lexblog.com/2012/02/27/lxbn-tv-breaking-down-the-white-house-privacy-framework-with-foley-hoags-colin-zick/"&gt;&lt;span style="font-size: xx-small"&gt;video discussion &lt;/span&gt;&lt;/a&gt;&lt;span style="font-size: xx-small"&gt;I had with LexBlog on the new &lt;/span&gt;&lt;a href="http://www.securityprivacyandthelaw.com/uploads/file/White%20House%20privacy_white_paper.pdf"&gt;&lt;span style="font-size: xx-small"&gt;White House Data Privacy report&lt;/span&gt;&lt;/a&gt;&lt;span style="font-size: xx-small"&gt;, &lt;font color="#0073cf"&gt;&amp;ldquo;Consumer Data Privacy in a Networked World: A Framework for Protecting Privacy and Promoting Innovation in the Global Digital Economy.&lt;/font&gt;&amp;rdquo;&amp;nbsp; In this&amp;nbsp;conversation, we&amp;nbsp;discussed&amp;nbsp;the report's&amp;nbsp;four primary&amp;nbsp;elements:&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;a Consumer Privacy Bill of Rights, &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;a multistakeholder process to specify how the principles in the Consumer Privacy Bill of Rights apply in particular business contexts, &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;effective enforcement, and &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;a commitment to increase interoperability with the privacy frameworks of our international partners. &lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;span style="font-size: xx-small"&gt;Specifically, in&amp;nbsp;the&amp;nbsp;Consumer Privacy Bill of Rights,&amp;nbsp;it provides for:&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Individual Control: Consumers have a right to exercise control over what personal data companies collect from them and how they use it. &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Transparency: Consumers have a right to easily understandable and accessible information about privacy and security practices. &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Respect for Context: Consumers have a right to expect that companies will collect, use, and disclose personal data in ways that are consistent with the context in which consumers provide the data. &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Security: Consumers have a right to secure and responsible handling of personal data. &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Access and Accuracy: Consumers have a right to access and correct personal data in usable formats, in a manner that is appropriate to the sensitivity of the data and the risk of adverse consequences to consumers if the data is inaccurate. &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Focused Collection: Consumers have a right to reasonable limits on the personal data that companies collect and retain. &lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: xx-small"&gt;Accountability: Consumers have a right to have personal data handled by companies with appropriate measures in place to assure they adhere to the Consumer Privacy Bill of Rights. &lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/SecurityPrivacyAndTheLaw/~4/guA7BWnOsC0" height="1" width="1"/&gt;</description>
         <link>http://feedproxy.google.com/~r/SecurityPrivacyAndTheLaw/~3/guA7BWnOsC0/</link>
         <guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2012/03/articles/government-enforcement/breaking-down-the-white-house-privacy-frameworka-video-blog/</guid>
         <category domain="http://www.securityprivacyandthelaw.com/tags">Commerce</category><category domain="http://www.securityprivacyandthelaw.com/tags">Congress</category><category domain="http://www.securityprivacyandthelaw.com/tags">Customer</category><category domain="http://www.securityprivacyandthelaw.com/tags">Department</category><category domain="http://www.securityprivacyandthelaw.com/tags">FTC</category><category domain="http://www.securityprivacyandthelaw.com/articles">Government Enforcement</category><category domain="http://www.securityprivacyandthelaw.com/tags">House</category><category domain="http://www.securityprivacyandthelaw.com/tags">Industry</category><category domain="http://www.securityprivacyandthelaw.com/tags">Information</category><category domain="http://www.securityprivacyandthelaw.com/articles">Legislation &amp; Regulation</category><category domain="http://www.securityprivacyandthelaw.com/articles">Retail Industry &amp; Customer Information Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/tags">Spotlight</category><category domain="http://www.securityprivacyandthelaw.com/tags">White</category><category domain="http://www.securityprivacyandthelaw.com/tags">enforcement</category><category domain="http://www.securityprivacyandthelaw.com/tags">government</category><category domain="http://www.securityprivacyandthelaw.com/tags">legislation</category><category domain="http://www.securityprivacyandthelaw.com/tags">of</category><category domain="http://www.securityprivacyandthelaw.com/tags">privacy</category><category domain="http://www.securityprivacyandthelaw.com/tags">regulation</category><category domain="http://www.securityprivacyandthelaw.com/tags">report</category><category domain="http://www.securityprivacyandthelaw.com/tags">retail</category>
         <pubDate>Mon, 05 Mar 2012 05:31:38 -0500</pubDate>
         <author>blogs@foleyhoag.com (Colin J. Zick)</author>
      
      <feedburner:origLink>http://www.securityprivacyandthelaw.com/2012/03/articles/government-enforcement/breaking-down-the-white-house-privacy-frameworka-video-blog/</feedburner:origLink></item>
      
   </channel>
</rss>

