<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>CIPP Guide &#187; biometrics</title> <atom:link href="http://www.cippguide.org/tag/biometrics/feed/" rel="self" type="application/rss+xml" /><link>https://www.cippguide.org</link> <description>Your Guide to the CIPP</description> <lastBuildDate>Sat, 11 Feb 2012 07:47:27 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>Identity Theft Task Force Recommendations</title><link>https://www.cippguide.org/2010/04/13/identity-theft-task-force-recommendations/</link> <comments>https://www.cippguide.org/2010/04/13/identity-theft-task-force-recommendations/#comments</comments> <pubDate>Tue, 13 Apr 2010 12:00:56 +0000</pubDate> <dc:creator>jbrook</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Compliance & Regulations]]></category> <category><![CDATA[Privacy]]></category> <category><![CDATA[biometrics]]></category> <category><![CDATA[CIPP/G]]></category> <category><![CDATA[Combatting ID Theft]]></category> <category><![CDATA[Department of Homeland Security]]></category> <category><![CDATA[DHS]]></category> <category><![CDATA[Executive Order]]></category> <category><![CDATA[Federal Trade Commission]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[Identity Theft Task Force]]></category> <category><![CDATA[OMB]]></category> <category><![CDATA[Privacy Act]]></category> <category><![CDATA[Social Security Number]]></category> <category><![CDATA[SSN]]></category><guid
isPermaLink="false">http://www.cippguide.org/?p=1441</guid> <description><![CDATA[In May 2006, an Executive Order of the President created the Identity Theft Task Force. The Task Force includes members of several Federal agencies and departments. In September 2006, the Task Force released a number of recommendations ahead of the May 2007 document “Combatting ID Theft: Strategic Plan” in order to help agencies get a head start on the growing problem of identity [...]]]></description> <content:encoded><![CDATA[<p>In May 2006, an Executive Order of the President created the <a
href="http://www.idtheft.gov/">Identity Theft Task Force</a>. The Task Force includes members of several Federal agencies and departments. In September 2006, the Task Force released a number of recommendations ahead of the May 2007 document “<a
href="http://www.idtheft.gov/reports/StrategicPlan.pdf">Combatting ID Theft: Strategic Plan</a>” in order to help agencies get a head start on the growing problem of identity theft.</p><p>The memorandum issued the following recommendations:</p><p><strong>Data Breach Guidance to Agencies</strong></p><p>The Office of Management and Budget should issue a memorandum guiding agencies on when and how notice must be given to individuals at risk for identity theft due to a security breach. The suggested memorandum, titled “<a
href="http://www.whitehouse.gov/OMB/memoranda/.../task_force_theft_memo.pdf">Recommendations for Identity Theft Related Data Breach Notification</a>” was released almost concurrently with the Task Force’s memorandum.</p><p><strong>Development of Universal Police Report for Identity Theft Victims</strong></p><p>Identity theft victims my require official police reports to contest fraudulent information on their credit reports. A universal identity theft police report ensures that all necessary information is collected. It also allows identity theft victims to print the report from online, fill it out and bring it to their local enforcement agency for verification. Currently, individuals may also <strong><a
href="http://www.ftc.gov/bcp/edu/microsites/idtheft/consumers/filing-a-report.html">file an official complaint</a></strong> with the Federal Trade Commission on the FTC website. A universal form of filing complaints, reduces the strain on law enforcement agencies and  allows streamlining of investigations.</p><p><strong>Extending Restitution for Victims of Identity Theft</strong></p><p>The Task Force recommended to Congress that defendants be required to pay their identity theft victims monetarily for the time lost due to investigating, responding to and correcting fraudulent activity on their credit reports. This created extra penalties for committing identity theft, as well as allowed some renumeration to be paid to identity theft victims for their troubles, in addition to settling any financial disputes related to the fraudulent activity.</p><p><strong>Reducing Access of Identity Thieves to Social Security Numbers</strong></p><p>All agencies in the public sector should limit the use of Social Security Numbers as an individuals main identifier in an information system. The Office of Personnel Management was instructed to assign employee identification numbers for common use to <strong><a
href="http://www.cippguide.org/2010/03/29/guidance-on-protecting-federal-employee-social-security-numbers-and-combating-identify-theft/">eliminate the widespread use of SSN as the primary identifier for government employees</a></strong>. The OPM was also instructed to develop policies for the appropriate use and protection of Social Security Numbers. Further more all agencies were asked to review their use of SSNs in physical and electronic records systems to eliminate and restrict its usage where possible.</p><p><strong>Developing Alternative Methods of Authentication Identities</strong></p><p>The Task Force recommended that agencies confer with privacy and security experts in the private sector to create and implement technologies that use identifiers such as biometrics to authenticate identity. Biometric identifiers are harder for identity thieves to replicate or abuse. Using biometric identifiers in order to access personally identifiable information would significantly increase the protection to sensitive data.</p><p><strong>Improving Data Security in the Government</strong></p><p>The Task Force asked that the Office of Management and Budget and the Department of Homeland Security work together to investigate privacy practices in the Federal government and develop a list of the top mistakes that affect an agency’s ability to adequately protect data. This document was published in 2007 under the title <a
href="http://www.cippguide.org/2010/03/22/common-risks-impeding-the-adequate-protection-of-government-information/">“Common Risks Impeding the Adequate Protection of Government Information.” </a></p><p><strong>Improving the Agencies’ Ability to Respond to Data Breaches in the Government</strong></p><p>Agencies were instructed to develop and publish a “routine use” policy for their systems of records under the <strong><a
href="http://www.cippguide.org/2010/02/10/privacy-act-of-1974/">Privacy Act</a>. </strong>These “routine use” policies would allow agencies to share PII–without the prior consent of the individual–with other agencies in order to respond effectively to security breaches.</p><p><strong>Summary</strong></p><p>In 2006, the Presidential Identity Theft Task Force allowed the U.S. Government to quickly analyze federal information security practices and create appropriate recommendations and plans to increase protection. Of the seven recommendations put forth by the Identity Theft Task force in 2006, several have been fulfilled and/or implemented in to government practice. Today, the Task Force continues to discuss ways in which the U.S. Government can increase the protection of its data holdings to prevent unauthorized disclosure and expose citizens to the threat of identity theft. While only the Federal Government was required to implement many of the guidelines, they serve as a model for institutions in the private sector concerned with identity theft.</p><p><em>CIPP/G Candidate Preparation</em></p><p>In preparation for the Certified Information Privacy Professional Government exam, a privacy professional should be comfortable with topics related to this post including:</p><ul><li>Recommendations of the Identity Theft Task Force, September 2006</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2010/04/13/identity-theft-task-force-recommendations/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Missouri lawmakers follow rebel suit and reject REAL ID</title><link>https://www.cippguide.org/2009/05/16/missouri-lawmakers-follow-rebel-suit-and-reject-real-id/</link> <comments>https://www.cippguide.org/2009/05/16/missouri-lawmakers-follow-rebel-suit-and-reject-real-id/#comments</comments> <pubDate>Sat, 16 May 2009 14:16:23 +0000</pubDate> <dc:creator>jbrook</dc:creator> <category><![CDATA[Compliance & Regulations]]></category> <category><![CDATA[Privacy]]></category> <category><![CDATA[biometrics]]></category> <category><![CDATA[Department of Homeland Security]]></category> <category><![CDATA[DHS]]></category> <category><![CDATA[House Bill 361]]></category> <category><![CDATA[Missouri]]></category> <category><![CDATA[Pass ID]]></category> <category><![CDATA[REAL ID]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">http://www.cippguide.org/?p=595</guid> <description><![CDATA[Missouri state lawmakers overwhelmingly voted Wednesday to pass House Bill 361, effectively rejecting the provisions for compliance with the 2005 REAL ID Act.  If the Governor does sign the legislation, the Show Me State will have a bit of cleanup to do, including what to do with the data already collected after pilot program, and what happens to the $22M in DHS [...]]]></description> <content:encoded><![CDATA[<p>Missouri state lawmakers <a
title="Missouri legislature pass bill repealing participation in REAL ID with potential privacy concerns" href="http://www.kansascity.com/news/politics/story/1195917.html" target="_blank">overwhelmingly voted Wednesday</a> to pass <a
title="Missouri House Bill 361 opts out of REAL ID Act" href="http://www.house.mo.gov/billtracking/bills091/biltxt/truly/HB0361T.HTM" target="_blank">House Bill 361</a>, effectively rejecting the provisions for compliance with the 2005 REAL ID Act.  Missouri now becomes the 13th state to actively ban the national ID card provisions.  This move comes <a
title="PASS ID Act may significantly impact privacy concerns of REAL ID" href="http://www.cippguide.org/2009/04/25/obama-and-congress-maybe-real-id-needs-changes/" target="_blank">amid discussions of the PASS ID legislation</a>, which may significantly alter or repeal entirely the pilot work already performed.  If the Governor does sign the legislation, the Show Me State will have a bit of cleanup to do.  </p><p><a
title="Department of Homeland Security provides $79M in state grants to make REAL ID a reality" href="http://www.dhs.gov/xnews/releases/pr_1213973982746.shtm" target="_blank">Missouri accepted $17 M in DHS grants last year to serve as the lead developer in a REAL ID verification hub</a>.  That grant included an additional $1.2M to each of four other states (Florida, Indiana, Nevada, and Wisconsin) that, as the DHS announced, would use Missouri:</p><blockquote><p>&#8230; as a central router to provide timely, accurate, and cost-effective verification to motor vehicle departments of an applicant&#8217;s source documents. States will be able to seamlessly verify the identity, lawful status and social security number of an applicant through this common interface.</p></blockquote><p>What will happen to any unspent funds, and if there will be any penalties from the DHS for contract breach has yet to be determined.  What is know is part of HB 361 does deal with destroying personally identifiable information collected in the verification hub capacity.  Missouri is taking their privacy role seriously:</p><blockquote><p>Any biometric data previously collected, obtained, or retained in connection with motor vehicle registration or operation, the issuance or renewal of driver&#8217;s licenses, or the issuance or renewal of any identification cards by any department or agency of the state charged with those activities shall be retrieved and deleted from all databases. </p></blockquote><p>A few of the less obvious biometric authentication information are specifically called out in the bill.  Facial patterns, voice, iris patterns, retinal scans and fingerprint information are all part of the popular lexicon, showing up in Hollywood blockbusters over the past couple of decades.  Personally, DNA really has no reason to even be thought of as an option for biometrics with a whole host of associated issues that will no doubt be addressed at a future time.  Those that are a curiosity: eye spacing, gait, and keystroke dynamics.  None of these on their own should be an authentication parameter, as eye spacing and gait are casually observable, and keystroke dynamics vary widely.  Someone hopped up on a Starbucks or late for a plane simply won&#8217;t press the buttons with the same lethargy for accurate measurements.  Using percentages (2 out of 3) to make a better educated guess with these types of observations does makes sense.  This is probably not as big of a deal with a &#8220;driver&#8217;s license&#8221;, but as we covered, opponents of REAL ID expect the card to become the next Social Security Number in terms of ubiquity and <a
title="REAL ID includes unsecured technologies that jeopardize US citizens' privacy" href="http://www.cippguide.org/2009/04/22/snooping-rfid-embedded-drivers-licenses-is-real-id-a-bad-idea/" target="_blank">several features of the Act worry privacy professionals</a>.</p><p>The bill does give some justification as to the motives behind the change of heart, apparently seeing the REAL ID activities as complicating state&#8217;s rights.  As a verification hub, Missouri could be seen as potentially infringing on the rights of other states, or acting as an agent of the US Federal Government.  In all, the MO state legislators decreed:  </p><blockquote><p>No citizen of this state shall have his or her privacy compromised by the state or agents of the state. The state shall within reason protect the sovereignty of the citizens the state is entrusted to protect.</p></blockquote><p>Update:  Follow the current progress of HB 361 through the Missouri Governor&#8217;s desk on the <a
title="Track HB 361 on the Missouri State House of Representatives site" href="http://house.mo.gov/content.aspx?info=/bills091/action/aHB361.htm" target="_blank">MO State House of Representatives site</a>.</p> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2009/05/16/missouri-lawmakers-follow-rebel-suit-and-reject-real-id/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Finland&#039;s Fingerprinting Fiasco? Centralized private records database accessible by police</title><link>https://www.cippguide.org/2009/02/05/finlands-fingerprinting-fiasco-centralized-private-records-database-accessible-by-police/</link> <comments>https://www.cippguide.org/2009/02/05/finlands-fingerprinting-fiasco-centralized-private-records-database-accessible-by-police/#comments</comments> <pubDate>Thu, 05 Feb 2009 19:08:08 +0000</pubDate> <dc:creator>jbrook</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Privacy]]></category> <category><![CDATA[APEC]]></category> <category><![CDATA[biometrics]]></category> <category><![CDATA[EU]]></category> <category><![CDATA[European Union Data Protection Directive]]></category> <category><![CDATA[fingerprint]]></category> <category><![CDATA[Finland]]></category> <category><![CDATA[Information Privacy]]></category> <category><![CDATA[OECD]]></category> <category><![CDATA[regulations]]></category> <category><![CDATA[Singapore]]></category><guid
isPermaLink="false">http://blog.cippguide.org/?p=191</guid> <description><![CDATA[Finland will collect all their citizens' fingerprints, store them in a central database and include them in passport ID chips.  Singapore's been doing this for several years, and the parallels and privacy implications are deeper than [...]]]></description> <content:encoded><![CDATA[<p>A bill expected to be presented to the Finnish Parliament today will require all citizens and anyone who applies for a passport or travel documents through Finland&#8217;s borders to end up in a centralized fingerprint database.  This information will not only be accessible to customs and immigrations officials, but also by police.  The justification for such action lays in the June 28th European Union&#8217;s Member State travel document requirements.</p><p>This seems to fly in the face of EU&#8217;s Privacy Protection Directive, and a long history of pro-privacy government.  Finland was one of the early participants of a group called the Organization for Economic Cooperation and Development (OECD), <a
title="OECD Membership List - including Finland" href="http://www.oecd.org/document/58/0,2340,en_2649_201185_1889402_1_1_1_1,00.html" target="_blank">signing up in 1969</a>.  The <a
title="OECD Privacy Guidelines" href="http://www.oecd.org/document/18/0,3343,en_2649_34255_1815186_1_1_1_1,00.html" target="_blank">OECD&#8217;s eight privacy principals</a> served as a baseline for private data handling within member states and included such items as collecting the minimum amount of information necessary and limitations of use for any data collected.</p><p>Finland&#8217;s not the first country to register this sort of information &#8211; Singapore&#8217;s been doing this for several years.  They keep all of their citizen&#8217;s data (including fingerprints) in one big database called the Central Identification and Registration Information System (CIRIS).  It not only covers Singaporian&#8217;s, but includes anyone that passes through their customs and immigration checkpoints.  Granted, it&#8217;s protected through <a
title="Companies securing Singapore's CIRIS database housing citizens' private data" href="http://www.fleetship.com/fleetnews/CIO100_08_Index.pdf" target="_blank">several security mechanisms</a>, they&#8217;re a much smaller country land-wise and not affiliated with Europe or it&#8217;s wartime past indiscretions, but the population difference is less than 600K in Singapore&#8217;s favor and the economic influence of the tiny island can&#8217;t be ignored.</p><p>Why the parallels to Singapore you may ask?  Pedigree.  Singapore is part of the Asia-Pacific Economic Cooperation and (mostly) abides by the <a
title="APEC Privacy Framework" href="http://www.apec.org/apec/news___media/fact_sheets/apec_privacy_framework.html" target="_blank">APEC privacy framework.</a> The nine principles of the APEC privacy framework mirrors the OECD&#8217;s eight, including both the Collection Limitation and Use Limitation principles.    The CIPP covers all of this history and evolution between the various privacy assurance concepts.</p><p>Finland might look over some of Singapore&#8217;s justifications for private data centralization in selling this to their citizens.  Are they collecting the fingerprints just to have them on file?  Maybe someone somewhere might do something criminal?</p><p>The Google translation of the Finnish government&#8217;s statement is <a
href="http://translate.google.com/translate?hl=en&amp;sl=fi&amp;u=http://www.vn.fi/ajankohtaista/tiedotteet/tiedote/fi.jsp%3Foid%3D252317&amp;sa=X&amp;oi=translate&amp;resnum=1&amp;ct=result&amp;prev=/search%3Fq%3Dhttp://www.vn.fi/ajankohtaista/tiedotteet/tiedote/fi.jsp%253Foid%253D252317%26hl%3Den%26client%3Dfirefox-a%26rls%3Dorg.mozilla:en-GB:official%26hs%3DVZm">here.</a></p> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2009/02/05/finlands-fingerprinting-fiasco-centralized-private-records-database-accessible-by-police/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: www.cippguide.org @ 2012-02-11 03:49:36 -->
