<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: DHS Biometric Database &#8211; Concerns And A Controversial Solution</title>
	<atom:link href="http://gcaptain.com/maritime/blog/dhs-biometric-database-concerns-and-a-controversial-solution/feed/" rel="self" type="application/rss+xml" />
	<link>http://gcaptain.com/maritime/blog/dhs-biometric-database-concerns-and-a-controversial-solution/</link>
	<description>A Blog About Ships</description>
	<lastBuildDate>Thu, 18 Mar 2010 19:11:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://gcaptain.com/maritime/blog/dhs-biometric-database-concerns-and-a-controversial-solution/comment-page-1/#comment-10725</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 30 Apr 2008 13:45:35 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=1450#comment-10725</guid>
		<description>Excellent comment, thanks John!</description>
		<content:encoded><![CDATA[<p>Excellent comment, thanks John!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://gcaptain.com/maritime/blog/dhs-biometric-database-concerns-and-a-controversial-solution/comment-page-1/#comment-13357</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 30 Apr 2008 11:45:35 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=1450#comment-13357</guid>
		<description>Excellent comment, thanks John!</description>
		<content:encoded><![CDATA[<p>Excellent comment, thanks John!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Pettitt</title>
		<link>http://gcaptain.com/maritime/blog/dhs-biometric-database-concerns-and-a-controversial-solution/comment-page-1/#comment-10520</link>
		<dc:creator>John Pettitt</dc:creator>
		<pubDate>Sun, 27 Apr 2008 00:24:17 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=1450#comment-10520</guid>
		<description>It turns out that &quot;who are you&quot; is a really difficult question to answer reliably.   If you&#039;ve watched mythbusters you&#039;ll know that fingerprint scanner can be defeated pretty easily.     Good security uses two or three independent factors to authenticate users.  Something you have (say and ID), something you know (a PIN or password) and something you are (retina or fingerprint scan).   Single factor security is generally easy to beat.

All of that assumes the right person got entered into the database in the first place.   That&#039;s much more problematic because the source documents we use to prove ID are completely independent of the the actual person (eg a social security card and a birth certificate gets you a drivers license and a passport).

In the commercial world (credit cards are a good example) a certain level of ID fraud is a cost of doing business.   There comes a point where increased security costs more than the losses it&#039;s trying to prevent and the &quot;insult rate&quot; (when legitimate transactions are declined by an over zealous system) becomes a problem.  

John (apart from doing HD-SF.com time-lapse I used to write credit card fraud detection software)</description>
		<content:encoded><![CDATA[<p>It turns out that &#8220;who are you&#8221; is a really difficult question to answer reliably.   If you&#8217;ve watched mythbusters you&#8217;ll know that fingerprint scanner can be defeated pretty easily.     Good security uses two or three independent factors to authenticate users.  Something you have (say and ID), something you know (a PIN or password) and something you are (retina or fingerprint scan).   Single factor security is generally easy to beat.</p>
<p>All of that assumes the right person got entered into the database in the first place.   That&#8217;s much more problematic because the source documents we use to prove ID are completely independent of the the actual person (eg a social security card and a birth certificate gets you a drivers license and a passport).</p>
<p>In the commercial world (credit cards are a good example) a certain level of ID fraud is a cost of doing business.   There comes a point where increased security costs more than the losses it&#8217;s trying to prevent and the &#8220;insult rate&#8221; (when legitimate transactions are declined by an over zealous system) becomes a problem.  </p>
<p>John (apart from doing HD-SF.com time-lapse I used to write credit card fraud detection software)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
