<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>David Pardo - Security, Privacy and The Law</title>
<link>http://www.securityprivacyandthelaw.com/david-pardo.html</link>
<description><![CDATA[David Pardo is  an Associate in the firm’s Litigation Department. His practice includes  international disputes, securities investigations, and white collar criminal  defense. In addition, David maintains an active pro bono practice, representing  tenants in public housing matters. 
 During law  school, David served as Managing Editor of the American criminal Law Review’s  Annual Survey of White Collar Crime, served as a Global Teaching Fellow for Georgetown’s  “Law In A Global Context” seminars, and tutored first-year law students. David  also worked for the U.S. Department of Justice’s Aviation &amp; Admiralty  Litigation section and for an Administrative Law Judge in the U.S. Department  of Transportation’s Office of Hearings. 
 Before arriving  at Foley Hoag, David worked as a legal assistant at a New York law firm and  interned on a presidential campaign. 
Bars and Court  Admissions

  Massachusetts 
  U.S.       District Court for the District of Massachusetts 
  U.S.       Court of Appeals, First Circuit 

Professional /  Civic involvement

  Boston       Bar Association, Member  
  American       Constitution Society for Law and Public Policy, Boston Chapter, Member 

Practice Areas

  Litigation 
  Business Crimes &amp; Government       Investigations 
  Securities Litigation 
  International 

Education

  Georgetown University Law Center, J.D., 2008 
  Embry-Riddle Aeronautical University, B.S., summa cum laude,       2003 
]]></description>
<language>en-us</language>
<copyright>Copyright 2010</copyright>
<lastBuildDate>Wed, 15 Jul 2009 10:35:00 -0500</lastBuildDate>
<pubDate>Thu, 09 Sep 2010 07:41:03 -0500</pubDate>
<generator>http://www.movabletype.org/</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 

<item>
<title>Bozeman, Montana Suspends Controversial Requirement That Job Applicants Provide Usernames and Passwords to Facebook Accounts</title>
<description><![CDATA[<p>When, in June, the City of Bozeman, Montana sought to change its job application to require municipal job seekers to disclose usernames and passwords for popular social networking sites, it immediately drew <a href="http://www.montanasnewsstation.com/global/story.asp?S=10559290">widespread criticism</a>.&nbsp; Specifically, Bozeman asked applicants to &quot;Please list any and all, current personal or business websites, web pages or memberships on any Internet-based chat rooms, social clubs or forums, to include, but not limited to: Facebook, Google, Yahoo, YouTube.com, MySpace, etc.&quot;&nbsp; In the aftermath of media exposure, Bozeman has decided to &quot;suspend its practice of reviewing candidate&rsquo;s password protected internet information until the City conducts a more comprehensive evaluation of the practice.&quot;</p>
<p>On June 19, 2009, city manager Chris Kukulski <a href="http://www.securityprivacyandthelaw.com/uploads/file/Background%20Check%20Press%20Release%20June%2019%202009.pdf">officially apologized</a>&nbsp;(.pdf) for the intrusive application, stating &ldquo;[t]he extent of our request for a candidate&rsquo;s password, user name, or other internet information appears to have exceeded that which is acceptable to our community.&rdquo;</p>
<p>This controversy is another indication that social networking sites and other digital media are coming under greater scrutiny as employers conduct background checks. For example, the application for high-level political positions in the Obama transition phase <a href="http://www.nytimes.com/2008/11/13/us/politics/13apply.html?_r=1">required</a> applicants to include copies of e-mails that might embarrass the President, copies of all blog posts, a link to one&rsquo;s Facebook page, and a list of &ldquo;all aliases or &lsquo;handles&rsquo; . . . used to communicate on the Internet.&rdquo;</p>
<p>The Bozeman application would have required applicants to violate Facebook&rsquo;s <a href="http://www.facebook.com/terms.php">Terms of Use</a>, which state that &ldquo;You will not share your password, let anyone else access your account, or do anything else that might jeopardize the security of your account.&rdquo; In addition, Bozeman&rsquo;s request apparently was limited to obtaining usernames and passwords and did not seek authorization to access applicants&rsquo; sites. Consequently, any access by city officials might have run afoul of the <a href="http://frwebgate.access.gpo.gov/cgi-bin/usc.cgi?ACTION=RETRIEVE&amp;FILE=$$xa$$busc18.wais&amp;start=2083841&amp;SIZE=36266&amp;TYPE=TEXT">Computer Fraud and Abuse Act</a>, 18 U.S.C. &sect; 1030(a)(2)(C), which prohibits intentionally accessing a &ldquo;protected computer&rdquo; without authorization. <br />
<br />
<u>Links</u>:</p>
<ul>
    <li><a href="http://www.montanasnewsstation.com/global/story.asp?S=10559290">Local news article</a></li>
    <li><a href="http://www.bozeman.net/bozeman/upcoming%20events/hire/06-18-09/Background%20Check%20Press%20Release%20June%2019%202009.pdf">City of Bozeman press release</a>&nbsp;(.pdf)</li>
    <li><a href="http://www.nytimes.com/2008/11/13/us/politics/13apply.htm">New York Times article</a></li>
    <li><a href="http://www.facebook.com/terms.php">Facebook Terms of Use</a></li>
    <li><a href="http://frwebgate.access.gpo.gov/cgi-bin/usc.cgi?ACTION=RETRIEVE&amp;FILE=$$xa$$busc18.wais&amp;start=2083841&amp;SIZE=36266&amp;TYPE=TEXT">Computer Fraud and Abuse Act, 18 U.S.C. &sect; 1030</a></li>
</ul>
<p>&nbsp;</p>]]></description>
<link>http://www.securityprivacyandthelaw.com/2009/07/articles/security-programs-policies/bozeman-montana-suspends-controversial-requirement-that-job-applicants-provide-usernames-and-passwords-to-facebook-accounts/</link>
<guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2009/07/articles/security-programs-policies/bozeman-montana-suspends-controversial-requirement-that-job-applicants-provide-usernames-and-passwords-to-facebook-accounts/</guid>
<category>Bozeman</category><category>Chris Kukulski</category><category>Computer Fraud and Abuse Act</category><category>Facebook</category><category>Montana</category><category>Security Programs &amp; Policies</category><category>background check</category><category>social networking</category>
<pubDate>Wed, 15 Jul 2009 10:35:00 -0500</pubDate>
<dc:creator>David Pardo</dc:creator>

</item>
<item>
<title>Privacy Panel Recommends Updates to Privacy Act, Privacy Officers for Federal Agencies</title>
<description><![CDATA[<p>On May 27, 2009,&nbsp;<a href="http://csrc.nist.gov/groups/SMA/ispab/index.html">Information Security and Privacy Advisory Board (ISPAB)</a> issued a <a href="http://www.securityprivacyandthelaw.com/uploads/file/ispab-report-may2009.pdf">report entitled &quot;Toward A 21st Century Framework for Federal Government Privacy Policy&quot;</a> (.pdf) that calls&nbsp;on Congress to amend the Privacy Act of 1974, establish the position of Chief Privacy Officer in numerous executive agencies and develop a Chief Privacy Officers&rsquo; Council.&nbsp;ISPAB is a group that advises the <a href="http://www.nist.gov">National Institute of Standards and Technology (NIST)</a>, the <a href="http://www.whitehouse.gov/omb/">Office of Management and Budget (OMB)</a>, and the <a href="http://www.commerce.gov">Commerce Department</a>.</p>
<p>In its report, ISPAB&nbsp;indicates that rising threats to privacy and advancements in computer technology and usage are unaddressed by outdated provisions in the Privacy Act. It also suggests that inattention by policymakers and the absence of guidance from the White House has led to a patchwork of inconsistent approaches by federal agencies. The report concludes that&nbsp;these factorhave contributed to the difficulty agencies have experienced in adapting to technological change. ISPAB urges the creating of a &ldquo;new framework to protect privacy&rdquo; by making the following recommendations:</p>
<ul>
    <li>Amend the Privacy Act of 1974 and Section 208 of the E-Government Act of 2002 to improve Government privacy notices and re-define &ldquo;System of Records&rdquo; based on function and use of data and not merely possession; <br />
    &nbsp;</li>
    <li>Institute Chief Privacy Officers at all &ldquo;CFO agencies;&rdquo; <br />
    &nbsp;</li>
    <li>Institute a Chief Privacy Officers&rsquo; Council; and<br />
    &nbsp;</li>
    <li>Develop uniform privacy policies emanating from the OMB.</li>
</ul>
<p>The Senate Homeland Security and Governmental Affairs Committee report that they intend to <a href="http://www.nextgov.com/nextgov/ng_20090528_3694.php">modernize</a>&nbsp;the law in this area.</p>
<p><u>Links</u>:</p>
<ul>
    <li>The ISPAB Report&nbsp;<u><font color="#0000ff"> &quot;Toward A 21st Century Framework for Federal Government Privacy Policy&quot;</font></u> (.pdf), also available from the NIST&nbsp;website <a href="http://csrc.nist.gov/groups/SMA/ispab/documents/correspondence/ispab-report-may2009.pdf">here</a> (.pdf)</li>
    <li>The <a href="http://csrc.nist.gov/">Computer Security Resource Center website</a> developed by the Computer Security Division of NIST</li>
    <li>News <a href="http://www.nextgov.com/nextgov/ng_20090528_3694.php">report</a>&nbsp;regarding possible Senate action.</li>
</ul>]]></description>
<link>http://www.securityprivacyandthelaw.com/2009/06/articles/recent-legislation-1/privacy-panel-recommends-updates-to-privacy-act-privacy-officers-for-federal-agencies/</link>
<guid isPermaLink="false">http://www.securityprivacyandthelaw.com/2009/06/articles/recent-legislation-1/privacy-panel-recommends-updates-to-privacy-act-privacy-officers-for-federal-agencies/</guid>
<category>ISPAB</category><category>Information Security and Privacy Advisory Board</category><category>Legislation &amp; Regulation</category><category>Privacy Act</category><category>Senate</category><category>Toward A 21st Century Framework for Federal Government Privacy Policy</category><category>White House</category>
<pubDate>Thu, 18 Jun 2009 11:10:00 -0500</pubDate>
<dc:creator>David Pardo</dc:creator>

</item>

</channel>
</rss>
