 |
False match or acceptance: This occurs when the system decides that the two biometrics (the one stored in the database and
the one provided now) are the same, when in reality they are not. The rate of false matches is known as False Matching
Rate (FMR) or False Acceptance Rate (FAR). False acceptance is a confidentiality and integrity risk. |
 |
False nonmatch or rejection: This is expressed as False Rejection Rate (FRR), and False Nonmatching
Rate (FNMR). False nonmatch is when the system erroneously decides that biometrics are from different identities while in
reality they are from the same person. False rejection is an availability risk. |
 |
Universality: Every relevant person should have an identifier. |
 |
Uniqueness: Each relevant person should have only one identifier, and no two people should have the same
identifier. |
 |
Permanence: The identifier should not change, nor should it be changeable. |
 |
Indispensability: The identifier should be one or more natural characteristics, which each person has and
retains. |
 |
Collectibility: The identifier should be collectible by anyone on any occasion. |
 |
Storability: The identifier should be storable in manual and in automated systems. |
 |
Exclusivity: No other form of identification should be necessary or used. |
 |
Precision: Every identifier should be sufficiently different from every other identifier that mistakes are
unlikely. |
 |
Simplicity: Recording and transmission should be easy and not errorprone. |
 |
Cost: Measuring and storing the identifier should not be unduly costly. |
 |
Convenience: Measuring and storing the identifier should not be unduly inconvenient or time-consuming. |
 |
Acceptability: Its use should conform to contemporary social standards. |
 |
Biometric technology is inherently focused on individuals and interfaces easily to database technology, making privacy
violations easier and more damaging. |
 |
Biometric systems are useless without a well-considered threat model. |
 |
Biometrics are no substitute for quality data about potential risks. |
 |
Biometric identification is only as good as the initial ID. |
 |
Biometric identification is often overkill for the task at hand. |
 |
Some biometric technologies are discriminatory. |
 |
Biometric systems accuracy is impossible to assess before deployment. |
 |
The cost of failure is high. |
 |
The Common Biometric Exchange File Format (CBEFF) describes a set of data elements necessary to support biometric
technologies in a unified way, and provides for the exchange of security, processing, and biometric data in a single file. The
U.S. National Institute for Standards and Technology (NIST) describes CBEFF as facilitating interoperability between
different systems or system components, forward compatibility for technology improvement, and software/ hardware integration
[25]. |
 |
BioAPI and Human Authentication API. BioAPI and HA-API efforts merged in 1999 under the umbrella of the BioAPI
Consortium. The current version of the BioAPI Specification is Version 1.1, which aims to provide a "standardized
Application Programming Interface (API) that will be compatible with a wide range of biometric applications and a
broad spectrum of biometrics technologies" [26]. |
 |
The Open Group's Human Recognition Services (HRS) is a module of the Common Data Security Architecture
(CDSA), which in particular is used in Apple's Mac OS X. HRS is compatible with the CBEFF and, thanks to the CDSA modular and
layered approach, can use services provided by other CDSA modules [28]. |
 |
Biometrics Management and Security for the Financial Services Industry (ANSI X9.84-2000) specifies minimum
security requirements for effective use of biometrics data in the U.S. financial services industry, including collection,
distribution, and processing of biometrics data. In particular, it specifies the security of the physical hardware used
throughout the biometric life cycle; the management of the biometric data across its life cycle; the use of biometric
technology for verification or identification of bank clients and employees; and other aspects. The data objects specified in
X9.84 are compatible with CBEFF [29]. |
 |
The American Association of Motor Vehicle Administrations (AAMVA) Driver's License and Identification
(DL/ID) standard provides a uniform way to identify holders of driver license cards within the United States and Canada. This
standard specifies identification information on drivers' license and ID card applications, provides for inclusion of
fingerprint data, and is compatible with BioAPI and CBEFF [30]. |
 |
ANSI/NIST Data Format for the Interchange of Fingerprint, Facial, Scar Mark, and Tattoo Information (ANSI/NIST-ITL
1-2000). This standard defines the content, format, and measurement units for the exchange of the specified information that
may be used for identification of persons, and it is mainly directed at U.S. law enforcement agencies and government. [31] |
1. |
User |
2. |
Path from the user to the sensor |
3. |
Biometric sensor |
4. |
Path from sensor to the general-purpose computer |
5. |
Network |
6. |
The central database |
1. |
The user should be accurately identified or the declared identity should be verified; the sensor should be able to
differentiate between a live human being providing live biometric and a biometric replica, such as an iris photograph or a
gelatin finger. This includes, inter alia, reasonable assurance of the physical presence of the whole individual and not just
the particular biometric at a particular point in time (hence, in part, the need for multimodal authentication involving not
only what you are but also what you know or what you have). |
2. |
The sensor should be sufficiently tamper-proof to withstand a defined set of attacks by a defined class of attackers, which
would of course differ from environment to environment. |
3. |
The communication protocol used between the sensor and the general-purpose computer should be simple, well-defined, and
verified. |
4. |
The role of the (untrusted) general-purpose computer and its software in such a system should be kept to a minimum. The
biometric data acquired by the sensor should be cryptographically protected (encrypted and signed with the device key, for
instance) inside the same sensor, without any dependence on action or inaction of the general-purpose computer. Their only role
in this play should be to relay the bits from the sensor to the central authentication server for verification. Confidentiality
and integrity of the biometric data should not be affected by a malicious, general-purpose computer or its software; the worst
that can happen is the nondelivery of such data to the central authentication database. |