<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Foley Hoag LLP - Security, Privacy and The Law</title>
<link>http://www.securityprivacyandthelaw.com/olubin.html</link>
<description></description>
<language>en-us</language>
<copyright>Copyright 2010</copyright>
<lastBuildDate>Sat, 28 Feb 2009 17:28:29 -0500</lastBuildDate>
<pubDate>Thu, 02 Sep 2010 12:06:50 -0500</pubDate>
<generator>http://www.movabletype.org/</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 

<item>
<title>Lessons Learned from Facebook&apos;s Terms of Service</title>
<description><![CDATA[<p>* By&nbsp;<a href="http://www.securityprivacyandthelaw.com/ghelmer.html">Gabriel M. Helmer</a>&nbsp;and <a href="http://www.securityprivacyandthelaw.com/aaron-wright.html">Aaron Wright</a></p>
<p>When&nbsp;<a href="http://www.facebook.com/">Facebook</a>&nbsp;changed its official terms of service earlier this month, what ensued&nbsp;was an explosive public outcry over who owns what users post to social networking sites. Tens of thousands&nbsp;of Facebook's 175+ million users&nbsp;suddenly clicked that often-overlooked link at the bottom of the webpage and poured over&nbsp;the arcane and legalistic language comprising Facebook's terms of service.&nbsp;For many, this was no doubt the first time they had ever&nbsp;read the policy. Below, we recap the recent controversy and discuss the three lessons Facebook and the rest of us should have learned from this series of events.&nbsp;</p>
<p><strong>Recap: Facebook&nbsp;Revises Terms of Service, Ignites Massive Public Firestorm</strong></p>
<p>On February 4, 2009 Facebook announced on its&nbsp;<a href="http://blog.facebook.com/blog.php?post=50531412130">official blog</a>&nbsp;that it had updated its terms of service and provided its customers with a link to those new terms of service.&nbsp;The&nbsp;revisions went little remarked upon until February 15th when&nbsp;<a href="http://consumerist.com/">The Consumerist</a>,&nbsp;<a href="http://www.consumerreports.org/cro/index.htm">Consumer Reports</a>' official blog, posted a story entitled &ldquo;<a href="http://consumerist.com/5150175/facebooks-new-terms-of-service-we-can-do-anything-we-want-with-your-content-forever">Facebook's New Terms Of Service: &lsquo;We Can Do Anything We Want With Your Content. Forever.</a>&rsquo;&rdquo;&nbsp;The post focused on a revised clause that provided Facebook with irrevocable rights to use its users&rsquo; likenesses and content:</p>
<blockquote>
<p>You hereby grant Facebook an irrevocable, perpetual, non-exclusive, transferable, fully paid, worldwide license (with the right to sublicense) to (a) use, copy, publish, stream, store, retain, publicly perform or display, transmit, scan, reformat, modify, edit, frame, translate, excerpt, adapt, create derivative works and distribute (through multiple tiers), any User Content you (i) Post on or in connection with the Facebook Service or the promotion thereof subject only to your privacy settings or (ii) enable a user to Post, including by offering a Share Link on your website and (b) to use your name, likeness and image for any purpose, including commercial or advertising, each of (a) and (b) on or in connection with the Facebook Service or the promotion thereof.</p>
</blockquote>
<p>This most severe change from the original terms was that the revised clause excised&nbsp;a&nbsp;sentence&nbsp;that terminated Facebook's license to user content:</p>
<blockquote>
<p>You may remove your User Content from the Site at any time. If you choose to remove your User Content, the license granted above will automatically expire, however you acknowledge that the Company may retain archived copies of your User Content.</p>
</blockquote>
<p>After the Consumerist broke the news, the post received over 300,000&nbsp;hits in a single day (according to the&nbsp;<a href="http://www.nytimes.com/2009/02/17/technology/internet/17facebook.html">New York Times</a>) and after the post ignited a firestorm of criticism, blog posts and articles, one Facebook user created&nbsp;the&nbsp;user group &ldquo;<a href="http://www.facebook.com/group.php?gid=77069107432"><span>People Against the New Terms of Service (TOS)&rdquo;</span></a>.&nbsp; Two days later, the Consumerist&nbsp;<a href="http://consumerist.com/5155538/facebook-privacy-fallout-goes-nuclear">reported</a>&nbsp;that more than 750 articles had been written on the subject and&nbsp;the People Against the New Terms of&nbsp;Service&nbsp;group had 64,000 members.&nbsp; As of this posting, the group is over 141,000 members and growing.&nbsp; This may make Facebook's recent revision the most controversial&nbsp;event that has ever occurred&nbsp;in the history of website usage policies.&nbsp;</p>
<p>Facebook responded to the criticism within days.&nbsp; First, on February 16, 2009, Facebook attempted to&nbsp;<a href="http://blog.facebook.com/blog.php?post=54434097130"><span>explain</span></a>&nbsp;that they did not believe the new terms of service did what critics said they did.&nbsp; Then, Facebook&nbsp;<a href="http://blog.facebook.com/blog.php?post=54746167130">withdrew</a>&nbsp;the revised terms of service two days later, on February 18, 2009, and created a user group to open up discussion on a&nbsp;<a href="http://www.facebook.com/group.php?gid=69048030774">Facebook Bill of Rights and Responsibilities</a>. Facebook appears to be attempting to harness this controversy to power continued user debate and involvement in the site.&nbsp;</p>
<p>Below we discuss three key lessons to learn from the controversy over Facebook&rsquo;s terms of service.</p>]]><![CDATA[<p><strong>Lesson 1: My Information Is Mine, No Matter What I Do With It.</strong></p>
<p><span>What will make millions of Facebook users suddenly stop ignoring&nbsp;the link that has always been at the bottom of their Facebook profile and actually read the terms of service?&nbsp;The answer is: a rumor that their vacation photos, wall-to-wall conversations with friends and movie compatibility test results are no longer theirs to control.&nbsp; Much of the criticism comes from a simple objection to Facebook asserting ownership of its users&rsquo;&nbsp;<a href="http://www.filmmakermagazine.com/blog/2009/02/facebook-terms-of-service-change-causes.php"><span>creative works</span></a>&nbsp;and&nbsp;<a href="http://blog.facebook.com/blog.php?post=54434097130">personal photographs</a>, no matter how widely they are distributed.&nbsp;Like&nbsp;it or not,&nbsp;the clear concern&nbsp;voiced&nbsp;by tens, if not hundreds of thousands of Facebook users is&nbsp;that&nbsp;their photos and content belongs to them, not Facebook.&nbsp; Anyone that permits users to create or post their own on-line content should&nbsp;be paying careful attention here.&nbsp;Social networking permits users to generate public content, but there is an emerging view, if not a consensus, that a user is entitled to a certain degree of control over the content that she or he generates.&nbsp;</span></p>
<p><strong>Lesson 2: &nbsp;No One Likes Legal Terminology, Especially the Terms Apply To Me</strong></p>
<p>Perhaps the greatest irony of the Facebook controversy is that it demonstrates that few users have ever read the terms of service before.&nbsp;There has been loud criticism of Facebook for asserting an &quot;irrevocable, perpetual . . . worldwide license&quot; of user content (see user comments&nbsp;<a href="http://consumerist.com/5154745/facebook-clarifies-terms-of-service-we-do-not-own-your-stuff-forever">here</a>),&nbsp;even though this language was taken word for word from&nbsp;<a href="http://www.facebook.com/home.php#/terms.php?ref=pf">the original terms of service</a>.&nbsp;As lawyers, some of us have become used to this kind of legal boilerplate, but when the news of Facebook's revision hit, users turned in record numbers to the terms of service and discovered, for the first time, an uncomfortable&nbsp;twinge at the thought that anyone, let alone Facebook, had something &quot;perpetual&quot; or &quot;irrevocable&quot; to do with the pictures from their last family reunion or Friday night's cocktail party. Even lawyers have become concerned, judging from the number of lawyers from a wide variety of practices that we recognize among&nbsp;the&nbsp;members of the People Against the New Terms of Service user group.&nbsp;</p>
<p>It may be necessary for Facebook to obtain certain legal rights to user content because it has to store, manage and archive this information.&nbsp; But, the Facebook firestorm teaches us that policymakers and lawyers may sometimes need to spare the overbroad legal boilerplate and reassess what rights are really necessary to operate.</p>
<p><strong>Lesson 3: &nbsp;Let&rsquo;s Discuss, Not Dictate</strong></p>
<p>Finally, the introduction of the new terms of service was seen by some as having been done in an inappropriate manner.&nbsp;Some claimed that Facebook did not inform users of the change to the terms (see&nbsp;<a href="http://www.edrants.com/im-done-with-facebook/"><span>here</span></a>), while others argued that the notification provided to users of the new terms of service was too&nbsp;<a href="http://www.foxnews.com/story/0,2933,494804,00.html">subtle</a>.&nbsp;In response to this criticism, Facebook has been quick to open lines of communication.&nbsp;It created a user group to&nbsp;<a href="http://blog.facebook.com/blog.php?post=54746167130">discuss</a>&nbsp;changes they believe they must make to the terms of service and allowing users to&nbsp;<a href="http://blog.facebook.com/blog.php?post=56566967130">comment on proposed policy</a>&nbsp;before it is implemented.&nbsp;While there has been&nbsp;<a href="http://www.allfacebook.com/2009/02/live-facebook-terms-of-service-announcement/">talk</a>&nbsp;that the solution is greater transparency so that users know what policies you are considering, it seems the greater lesson to be learned here is to know your users.&nbsp;</p>
<p><u>Links</u>:</p>
<ul type="disc">
    <li>Amanda L. French, Ph.D. blog &ldquo;Facebook terms of service compared with MySpace, Flickr, Picasa, YouTube, LinkedIn, and Twitter&rdquo;:&nbsp;<a href="http://amandafrench.net/2009/02/16/facebook-terms-of-service-compared/"><span>http://amandafrench.net/2009/02/16/facebook-terms-of-service-compared/</span></a></li>
    <li>Consumer Reports:&nbsp;<a href="http://www.consumerreports.org/cro/index.htm"><span>http://www.consumerreports.org/cro/index.htm</span></a></li>
    <li>The Consumerist:&nbsp;<a href="http://consumerist.com/"><span>http://consumerist.com/</span></a></li>
    <li>Consumerist article&nbsp;&quot;&nbsp;<a href="http://consumerist.com/5150175/facebooks-new-terms-of-service-we-can-do-anything-we-want-with-your-content-forever"><span>http://consumerist.com/5150175/facebooks-new-terms-of-service-we-can-do-anything-we-want-with-your-content-forever</span></a></li>
    <li>Consumerist &ldquo;Facebook Clarifies Terms of Service: &lsquo;We Do Not Own Your Stuff Forever&rsquo;&rdquo;:<a href="http://consumerist.com/5154745/facebook-clarifies-terms-of-service-we-do-not-own-your-stuff-forever"><span>http://consumerist.com/5154745/facebook-clarifies-terms-of-service-we-do-not-own-your-stuff-forever</span></a></li>
    <li>Edward Champion, &ldquo;I&rsquo;m Done With Facebook&rdquo;:&nbsp;<a href="http://www.edrants.com/im-done-with-facebook/"><span>http://www.edrants.com/im-done-with-facebook/</span></a></li>
    <li>Facebook:&nbsp;<a href="http://www.facebook.com/"><span>http://www.facebook.com/</span></a></li>
    <li>Facebook announces new terms of service:&nbsp;<a href="http://blog.facebook.com/blog.php?post=50531412130"><span>http://blog.facebook.com/blog.php?post=50531412130</span></a></li>
    <li>Facebook explains new terms of service:&nbsp;<a href="http://blog.facebook.com/blog.php?post=54434097130"><span>http://blog.facebook.com/blog.php?post=54434097130</span></a></li>
    <li>Facebook to allow comments on new policy:&nbsp;<a href="http://blog.facebook.com/blog.php?post=56566967130"><span>http://blog.facebook.com/blog.php?post=56566967130</span></a></li>
    <li>Facebook withdraws new terms of service and announces group to discuss changes in policy:&nbsp;<a href="http://blog.facebook.com/blog.php?post=54746167130"><span>http://blog.facebook.com/blog.php?post=54746167130</span></a></li>
    <li>Filmmaker blog &ldquo;Facebook Terms of Service Change Causes Uproar&rdquo;:<a href="http://www.filmmakermagazine.com/blog/2009/02/facebook-terms-of-service-change-causes.php"><span>http://www.filmmakermagazine.com/blog/2009/02/facebook-terms-of-service-change-causes.php</span></a></li>
    <li>Fox New, &ldquo;Facebook CEO to Scared Users: Trust Us&rdquo;:<a href="http://www.foxnews.com/story/0,2933,494804,00.html"><span>http://www.foxnews.com/story/0,2933,494804,00.html</span></a></li>
    <li>Jim. M. Goldstein, &ldquo;Facebook Terms of Use: From Bad to Worse&rdquo;:&nbsp;<a href="http://www.jmg-galleries.com/blog/2009/02/17/facebooks-terms-of-use-from-bad-to-beyond-worse/"><span>http://www.jmg-galleries.com/blog/2009/02/17/facebooks-terms-of-use-from-bad-to-beyond-worse/</span></a></li>
    <li>New York&nbsp;Times &ldquo;Facebook&rsquo;s Users Ask Who Owns Information&rdquo; (registration required):<a href="http://www.nytimes.com/2009/02/17/technology/internet/17facebook.html">http://www.nytimes.com/2009/02/17/technology/internet/17facebook.html</a></li>
    <li>People Against the New Terms of Service (TOS):&nbsp;<a href="http://www.facebook.com/group.php?gid=77069107432"><span>http://www.facebook.com/group.php?gid=77069107432</span></a></li>
</ul>]]></description>
<link>http://www.securityprivacyandthelaw.com/2009/02/articles/security-programs-policies/lessons-learned-from-facebooks-terms-of-service/</link>
<guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2009/02/articles/security-programs-policies/lessons-learned-from-facebooks-terms-of-service/</guid>
<category>Facebook</category><category>People Against the New Terms of Service</category><category>Security Programs &amp; Policies</category><category>Terms of Service</category><category>policy</category>
<pubDate>Sat, 28 Feb 2009 17:28:29 -0500</pubDate>
<dc:creator>Foley Hoag LLP</dc:creator>

</item>
<item>
<title>FTC Says &quot;Dumpster Wrong Place for Consumers&apos; Personal Information&quot;</title>
<description><![CDATA[<p><span>*&nbsp;By Stacy Anderson and <a href="http://www.securityprivacyandthelaw.com/ghelmer.html">Gabriel M. Helmer</a>.</span></p>
<p>Anyone required to comply with the FTC&rsquo;s Disposal Rule [the text of the rule can be found <a href="http://www.securityprivacyandthelaw.com/uploads/file/FTC%20Disposal%20Rule.pdf">here</a>], which requires companies to take reasonable steps to dispose of information contained in consumer credit reports, should take note of a recent FTC enforcement action in federal court from the District of Nevada.&nbsp;On December 30, 2008, the FTC filed a <a href="http://www.securityprivacyandthelaw.com/uploads/file/FTC%20v_%20Navone%20-%20Complaint.pdf">complaint</a> against Las Vegas businessman Gregory Navone alleging that he violated the Disposal Rule and the Fair Credit Reporting Act (FCRA) when he discarded forty boxes of documents into a public dumpster behind an office building in Las Vegas.&nbsp;The boxes contained tax returns, mortgage applications, bank statements, photocopies of credit cards and drivers&rsquo; licenses, and other sensitive customer information collected by Navone&rsquo;s businesses. The FTC seeks monetary damages and an injunction against further violations under the Disposal Rule and the FRCA for Navone&rsquo;s alleged failure to take reasonable measures to protect customer information. &nbsp;Interestingly, the complaint also asserts claims under the FTC Act on the basis that Navone failed to abide by his own customer privacy policy, which stated:</p>
<blockquote>
<p>We take our responsibility to protect the privacy and confidentiality of customer information very seriously. We maintain physical, electronic, and procedural safeguards that comply with federal standards to store and secure information about you from unauthorized access, alteration and destruction. . . . From time to time, we enter into agreements with other companies to provide services to us or make products and services available to you. Under these agreements, the company may receive information about you but they must safeguard this information and they may not use it for any other purposes</p>
</blockquote>
<p>While the case remains pending, it serves as a reminder from the FTC&nbsp;on the importance of not only taking reasonable steps to protect sensitive customer information, but also living up to customer assurances regarding information security.</p>
<p><u>Links</u>:</p>
<ul>
    <li>The text of the FTC's Disposal Rule, 16 C.F.R. Part 682 can be found <a href="http://www.securityprivacyandthelaw.com/uploads/file/FTC%20Disposal%20Rule.pdf">here</a> (.pdf) or from the FTC's website <a href="http://www.ftc.gov/os/2004/11/041118disposalfrn.pdf">here</a> (.pdf)</li>
    <li>The complaint filed in FTC v. Navone is available <a href="http://www.securityprivacyandthelaw.com/uploads/file/FTC%20v_%20Navone%20-%20Complaint.pdf">here</a> (.pdf) or from the FTC's website&nbsp;<a href="http://www.ftc.gov/os/caselist/0723067/090121navonecmpt.pdf">here</a> (.pdf)</li>
</ul>]]></description>
<link>http://www.securityprivacyandthelaw.com/2009/01/articles/identity-theft-1/ftc-says-dumpster-wrong-place-for-consumers-personal-information/</link>
<guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2009/01/articles/identity-theft-1/ftc-says-dumpster-wrong-place-for-consumers-personal-information/</guid>
<category>16 C.F.R. Part 682</category><category>Disposal Rule</category><category>FCRA</category><category>FTC</category><category>Fair Credit Reporting Act</category><category>Gregory Navone</category><category>Identity Theft</category>
<pubDate>Thu, 29 Jan 2009 13:15:40 -0500</pubDate>
<dc:creator>Foley Hoag LLP</dc:creator>

</item>
<item>
<title>Isn&apos;t There Already A Federal Standard Governing Information Security? -- Re-Examining the Gramm-Leach Bliley Act</title>
<description><![CDATA[<p>*&nbsp;By Stacy Anderson and <a href="http://www.securityprivacyandthelaw.com/ghelmer.html">Gabriel M. Helmer</a>.</p>
<p>As an ever-increasing number of states enact legislation governing identity theft, customer data and personal information, pressure for clear federal legislation governing information security has mounted.&nbsp;For example, in December 2008, the FTC joined the growing number of voices calling on Congress to enact a legislation to create a single federal standard for the handling of personal information.&nbsp;(See our report <a href="../fckeditor.html?InstanceName=text&amp;Toolbar=alogblog#glbahere">here</a>.)&nbsp;As we see movement towards a unifying federal standard, we are also observing a growing&nbsp;insistence that such legislation be consistent with the customer data security requirements of the Gramm-Leach Bliley Financial Modernization Act of 1999 (GLBA) and its implementing regulations.&nbsp;As a result, even industries that are not required to comply with GLBA may wish to become familiar with its requirements.</p>
<p>Section 501(b) of GLBA requires agencies with oversight over financial institutions to establish standards relating to administrative, technical and physical safeguards for three purposes: 1) to insure the security and confidentiality of customer information, (2) to protect against any anticipated threats to the security of customer information, and (3) to protect against unauthorized access or use of customer information.&nbsp;</p>
<p>In 2001, the Department of Treasury, the Board of Governors of the Federal Reserve System, and the Federal Deposit Insurance Corporation (FDIC) issued Interagency Guidelines Establishing Standards for Safeguarding Customer Information. These guidelines require that financial institutions adopt an information security plan, which must be approved by the institution&rsquo;s Board.&nbsp;The plan must assess, manage and control threats that could result in unauthorized disclosure of information.&nbsp;The risk guidelines are flexible &ndash; they do not require that institutions implement specific risk control or assessment systems, but rather encourage them to adopt measures appropriate to their circumstances.&nbsp;Institutions are then required to monitor the plan and report to the Board annually.&nbsp;In addition, they must also ensure that their service providers implement appropriate measures to secure customer information.&nbsp;In 2005, the Department of the Treasury, the Board of Governors of the Federal Reserve System, and the FDIC issued the &ldquo;Interagency Guidance on Response Programs for Unauthorized Access to Customer Information and Customer Notice.&rdquo;&nbsp;This guidance requires that institutions develop a response plan to address unauthorized access to customer information.&nbsp;As part of this process, institutions must notify customers if sensitive customer information has been improperly accessed and misuse of that information has occurred or is likely to occur.</p>
<p>In 2002, the Federal Trade Commission (FTC) issued its &ldquo;Standards for Safeguarding Customer Information,&rdquo; commonly referred to as the Safeguards Rule.&nbsp;The rule apples to financial institutions over whom the FTC has oversight and resembles the interagency guidelines for safeguarding customer information.&nbsp;Like those guidelines, the Safeguards Rule affords institutions considerable flexibility in implementing safeguards.&nbsp;Unlike the guidelines, the Safeguards Rule does not require that the information security plan be approved by the institution&rsquo;s board, and does not contain customer notification requirements such as those set out in the Guidance on Response Programs, although the FTC does encourage entities to consider notifying customers in the event of a breach.&nbsp;In considering these federal regulations, it is worth noting that the FTC&rsquo;s recently issued Red Flag Rule implements the Fair and Accurate Credit Transactions Act of 2003 (&quot;FACT Act&quot;), and not GLBA<span>, although the FTC does anticipate that many institutions may have implemented some of the practices required under the Red Flag Rule as part of their efforts to conform with GLBA.</span></p>
<p>Of course, it remains to be seen whether broad federal legislation governing customer data security will be enacted and if so, whether GLBA requirements will be used as a blueprint for such legislation.&nbsp;Regardless, an understanding of GLBA requirements and their effectiveness can help inform the debate around such legislation.</p>
<p><u>Links</u>:</p>
<ul>
    <li>The FTC's webpage <a href="http://www.ftc.gov/bcp/edu/pubs/business/idtheft/bus53.shtm">In Brief: The Financial Privacy Requirements of the Gramm-Leach-Bliley Act</a></li>
    <li>The FTC&nbsp;publication <a href="http://www.ftc.gov/bcp/edu/pubs/business/idtheft/bus67.pdf">How To Comply with the Privacy of Consumer Financial Information Rule of the Gramm-Leach-Bliley Act</a> (.pdf)</li>
</ul>]]></description>
<link>http://www.securityprivacyandthelaw.com/2009/01/articles/recent-legislation-1/isnt-there-already-a-federal-standard-governing-information-security-reexamining-the-grammleach-bliley-act/</link>
<guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2009/01/articles/recent-legislation-1/isnt-there-already-a-federal-standard-governing-information-security-reexamining-the-grammleach-bliley-act/</guid>
<category>Articles</category><category>FTC</category><category>Financial Industry Spotlight</category><category>Financial Modernization Act</category><category>GLBA</category><category>Gramm Leach Bliley Act</category><category>Identity Theft</category><category>Legislation &amp; Regulation</category>
<pubDate>Wed, 21 Jan 2009 08:58:12 -0500</pubDate>
<dc:creator>Foley Hoag LLP</dc:creator>

</item>
<item>
<title>Document Library</title>
<description><![CDATA[<p>Here you will find a selection of the articles, documents and other resources highlighted in our various posts. In most cases links are either to another site or a PDF. &nbsp;</p>
<table cellspacing="5" cellpadding="5" border="0" style="border: 1px solid rgb(153, 153, 153); width: 149px; height: 37px;">
    <tbody>
        <tr>
            <td><a href="#ebooks">eBooks</a></td>
            <td>|</td>
            <td><a href="#briefs">Legal&nbsp;Briefs</a></td>
            <td>|</td>
            <td><a href="#policies">Federal&nbsp;Policies&nbsp;&amp;&nbsp;Guidelines</a></td>
            <td>|</td>
            <td><a href="#general">General&nbsp;Articles&nbsp;&amp;&nbsp;Publications</a></td>
        </tr>
    </tbody>
</table>
<p>&nbsp;&nbsp;</p>
<h2><a name="ebooks"></a>Security &amp; Privacy Guides <span style="font-size: 11px; color: rgb(153, 153, 153);">[ <a href="#">top</a> ]</span></h2>
<p>Foley Hoag publishes eBooks from time to time. This material is written by lawyers from the Firm's Security &amp; Privacy practice for the purpose of providing general guidance on security, privacy and the law. </p>
<ul>
    <li><a href="http://www.foleyhoag.com/~/media/Files/Publications/eBooks/5steps_infosecurity_ebook.ashx"><strong><img align="left" alt="" style="width: 65px; height: 88px;" src="http://www.securityprivacyandthelaw.com/uploads/image/5-steps-thumbnail_ashx.jpeg" />Five Key Steps to Developing an Information Security Program</strong></a> (.pdf) in this eBook, Gabriel Helmer introduces you to the key first steps in developing a written information security program to comply with federal and state regulations.&nbsp; The eBook also includes our guides to the Federal Trade Commission's Red Flags Rule, 16 CFR 681, and Massachusetts' identity theft regulations, 201 CMR&nbsp;17.00.<br />
    <br />
    &nbsp;</li>
    <li><strong>[IMAGE] Security &amp; Privacy Guide: FTC Red Flags Rule</strong> (.pdf) provides a condensed outline of what you need to know about the FTC's Red Flags Rule, 16 CFR&nbsp;681.&nbsp; If you are looking to answer questions about whether the Rule applies to you and what a business needs to do to comply, this is a good place to start.<br />
    &nbsp;</li>
    <li><strong>[IMAGE] </strong><strong>Security &amp; Privacy Guide: Massachusetts Identity Theft Regulations</strong> (.pdf) is a brief introduction to the Massachusetts identity theft regulations that will walk you through the requirements of these regulations and discusses what needs to be included in a &quot;comprehensive, written information security program.&quot;<br />
    &nbsp;</li>
    <li><strong>[IMAGE] </strong><strong>Security &amp; Privacy Guide: August 2009 Revisions to the Massachusetts Identity Theft Regulations</strong><strong> </strong>(.pdf) is a redline comparison of the most recent amendments to the Massachusetts identity theft regulations.</li>
</ul>
<h2><a name="briefs"></a>Noteworthy Court Filings &amp; Documents <span style="font-size: 11px; color: rgb(153, 153, 153);">[ <a href="#">top</a> ]</span></h2>
<p>Intro...</p>
<ul>
    <li>Criminal Complaint: USA v. Alberto Gonzales, Civ. A. No. (D.Mass.) contains the criminal charges against the individual alleged to be behind the massive consumer data breach at Heartland Payment Systems as well as the previous breach at TJX, Inc.<br />
    &nbsp;</li>
    <li>Civil Complaint: American Bar Association v. Federal Trade Commission, Civ. A. No. (D.D.C.) in this case, the ABA&nbsp;seeks a ruling that lawyers are not required to comply with the FTC's Red Flags Rule.<br />
    &nbsp;</li>
    <li>&nbsp;</li>
</ul>
<p>&nbsp;</p>
<h2><a name="policies"></a>Laws, Regulations &amp; Rules <span style="font-size: 11px; color: rgb(153, 153, 153);">[ <a href="#">top</a> ]</span></h2>
<p>Intro.</p>
<ul>
    <li>Document Listing</li>
</ul>
<p>&nbsp;</p>
<h2><a name="general"></a>Key Publications &amp; Reports <span style="font-size: 11px; color: rgb(153, 153, 153);">[ <a href="#">top</a> ]</span></h2>
<p>Intro.</p>
<ul>
    <li>Document Listing</li>
</ul>
<p>&nbsp;</p>]]></description>
<link>http://www.securityprivacyandthelaw.com/2008/11/articles/document-library/</link>
<guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2008/11/articles/document-library/</guid>
<category>Articles</category>
<pubDate>Sat, 01 Nov 2008 13:10:49 -0500</pubDate>
<dc:creator>Foley Hoag LLP</dc:creator>

</item>

</channel>
</rss>
