Re: [Speechsc] stealing biometric tokens

William Meisel <wmeisel@tmaa.com> Mon, 21 July 2008 11:39 UTC

Return-Path: <speechsc-bounces@ietf.org>
X-Original-To: speechsc-archive@optimus.ietf.org
Delivered-To: ietfarch-speechsc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 021883A6A0A; Mon, 21 Jul 2008 04:39:55 -0700 (PDT)
X-Original-To: speechsc@core3.amsl.com
Delivered-To: speechsc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 330EA3A68B1 for <speechsc@core3.amsl.com>; Sat, 19 Jul 2008 10:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.145
X-Spam-Level:
X-Spam-Status: No, score=-3.145 tagged_above=-999 required=5 tests=[AWL=-0.998, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_ADELPHIA=0.456, J_CHICKENPOX_82=0.6, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HMIBPeuxefCo for <speechsc@core3.amsl.com>; Sat, 19 Jul 2008 10:51:46 -0700 (PDT)
Received: from mta10.adelphia.net (mta10.adelphia.net [68.168.78.202]) by core3.amsl.com (Postfix) with ESMTP id C9DD43A680C for <speechsc@ietf.org>; Sat, 19 Jul 2008 10:51:45 -0700 (PDT)
Received: from [192.168.1.100] (really [76.172.208.171]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20080719175546.XCSD20419.mta10.adelphia.net@[192.168.1.100]>; Sat, 19 Jul 2008 13:55:46 -0400
User-Agent: Microsoft-Entourage/12.11.0.080522
Date: Sat, 19 Jul 2008 10:52:18 -0700
From: William Meisel <wmeisel@tmaa.com>
To: Judith Markowitz <judith@jmarkowitz.com>, 'Eric Burger' <eburger@standardstrack.com>, speechsc@ietf.org
Message-ID: <C4A777E2.16A3C%wmeisel@tmaa.com>
Thread-Topic: [Speechsc] stealing biometric tokens
Thread-Index: AcjohHcBCAgkC3qnpUS673kuAg263wBOUV0gAAKcw2Y=
In-Reply-To: <200807191652.m6JGqITT020821@omr12.networksolutionsemail.com>
Mime-version: 1.0
X-Mailman-Approved-At: Mon, 21 Jul 2008 04:39:54 -0700
Subject: Re: [Speechsc] stealing biometric tokens
X-BeenThere: speechsc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Speech Services Control Working Group <speechsc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/speechsc>
List-Post: <mailto:speechsc@ietf.org>
List-Help: <mailto:speechsc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: speechsc-bounces@ietf.org
Errors-To: speechsc-bounces@ietf.org

Hi, Judith.

I agree that ideally the solution is to provide adequate security for any
authentication data, and I hope solutions that insure every company does so
are eventually adopted.

The cited article really addresses a different subject. It says that
biometric identification, when stolen, is worse than having a PIN stolen
because a PIN can be changed, but a fingerprint can't (or a voice can't).
The article even talks about enrolling a different finger.

I think the basic assumption of the article is flawed. It assumes that one
can steal the stored biometric identifier and use that to authenticate
oneself as another. If the company stores the original image of a
fingerprint or the original recording of a voice, then I guess (with some
effort), the voice or fingerprint could be recreated. However, with speaker
verification and with fingerprints (in fact, with every pattern recognition
application I've been involved with since I wrote a book on it in 1972, the
process of storing "features" of the voice or fingerprint or any other
pattern is highly lossy and can't be reversed,in part because one wants to
identify the pattern in the presence of a lot of variation and thus capture
only largely invariant features. When challenged on the telephone to say a
password, having the features stored by the speaker verification system
wouldn't do one any good.

I hate to to have government agencies and companies left with the
misimpression that storing biometric data is somehow more dangerous (and
possibly creates more liability) than storing PINs.

-- Bill 

Bill Meisel
President, TMA Associates
Publisher & Editor, Speech Strategy News
(818)708-0962
www.tmaa.com




> From: Judith Markowitz <judith@jmarkowitz.com>
> Date: Sat, 19 Jul 2008 11:52:12 -0500
> To: William Meisel <wmeisel@tmaa.com>, 'Eric Burger'
> <eburger@standardstrack.com>, <speechsc@ietf.org>
> Subject: RE: [Speechsc] stealing biometric tokens
> 
> Hi Bill, 
> The attached article presents the picture in about as simplistic and naïve a
> way as possible. Consequently, it leads the reader to false conclusions.
> 
> Biometrics can be faked (called "spoofing") but it is generally not a
> trivial process and, in most cases, it is done with the raw biometric data.
> That is, fingerprint or face (etc.) images and voice recordings. It is much
> harder to re-engineer a biometric model/template, although that is not
> impossible. 
> 
> There are a number of ways to capture raw biometrics. The best way is to
> hack a database that stores them. Other methods involve capture at the
> sensor and on the transmission channel.
> 
> If you look at these approaches to capturing biometrics you can easily see a
> theme: security. You also see that the security that is needed (and too
> often missing) has nothing really to do with biometrics, itself. It is the
> same kind of security that is missing for PIN and password systems. So, it
> doesn't really help much to have multi-factor authentication if all of them
> are captured in transit or stolen from a hacked database.
> 
> In short, if government and private industry would take the time and spend
> the money to secure their networks, databases, and other systems many of
> these threats would be eliminated. That's why the data interchange format
> that I'm working on with the American National Standards Institute includes
> encryption and supports other security.
> 
> Judith Markowitz
> 
> -----Original Message-----
> From: speechsc-bounces@ietf.org [mailto:speechsc-bounces@ietf.org] On Behalf
> Of William Meisel
> Sent: Thursday, July 17, 2008 10:15 PM
> To: Eric Burger; speechsc@ietf.org
> Subject: Re: [Speechsc] Just to see if anyone is still out there
> 
> Am I missing something, or does the linked article (and the referenced
> professor) simply misunderstand biometric id? Having the biometric token (a
> fingerprint is the example) should neither allow the thief to recreate the
> fingerprint (assuming it is features of the fingerprint that are
> encoded--hopefully without announcing what each feature is) nor allow the
> thief to access the system, since they would need to have the finger (not
> the token) to do so. It would not be necessary for the individual to
> reenroll a new finger.
> 
> The same is true of speaker authentication.
> 
> -- Bill 
> 
> Bill Meisel
> President, TMA Associates
> Publisher & Editor, Speech Strategy News
> (818)708-0962
> www.tmaa.com
> 
> 
> 
> 
>> From: Eric Burger <eburger@standardstrack.com>
>> Date: Thu, 17 Jul 2008 08:07:08 -0400
>> To: <speechsc@ietf.org>
>> Subject: [Speechsc] Just to see if anyone is still out there
>> 
>> For the folks who care about biometrics:
>> 
> http://www.networkworld.com/newsletters/sec/2008/071408sec1.html?nlhtsecstra
> t=
>> ts_071508&nladname=071508securitystrategiesal
>> _______________________________________________
>> Speechsc mailing list
>> Speechsc@ietf.org
>> https://www.ietf.org/mailman/listinfo/speechsc
>> Supplemental web site:
>> &lt;http://www.standardstrack.com/ietf/speechsc&gt;
> 
> 
> _______________________________________________
> Speechsc mailing list
> Speechsc@ietf.org
> https://www.ietf.org/mailman/listinfo/speechsc
> Supplemental web site:
> &lt;http://www.standardstrack.com/ietf/speechsc&gt;
> 
> 


_______________________________________________
Speechsc mailing list
Speechsc@ietf.org
https://www.ietf.org/mailman/listinfo/speechsc
Supplemental web site:
&lt;http://www.standardstrack.com/ietf/speechsc&gt;