What is a CBEFF and why do I c

Fingerprint Standard Update Workshop
Copyright © 2004 by SAFLINK C

CBEFF

Common Biometric Exchange Form

Workshop – Feb 1999

Jan 2001

NISTIR 6529

Apr 2004

NISTIR 6529-A

Feb 2005

ANSI INCITS 

Aug 20
Copyright © 2004 by SAFLINK C

CBEFF Purpose

 CBEFF describes a set of data el

necessary to support biometric tecommon way.

 Features

o Facilitates biometric data interchan

different system components or sy

o Promotes interoperability of biome

application programs and systems

o Provides forward compatibility for t

improvements

o Simplifies the software and hardwa

process
Copyright © 2004 by SAFLINK C

CBEFF in a Nutshe

 Defines Basic Field

Biometric Data

– Security– Useful Biometric P– Biometric Data

 Doesn’t constrain t

data

 Registration of Bio

IBIA

 Allows for new ada CBEFF compliance 

“Patrons and Clien

Standard

Biometric 

Header

Digital

Signature
Copyright © 2004 by SAFLINK C

CBEFF Data Struct

HEADER

(SBH)

BIOMETRIC DATA BLOC

(BDB)

Format OwnerFormat Type

Requiredheader field

- May be st- Published - Raw, inte- For enroll

identificat

- One or m- One or m- Clear/enc

signed/un

Receiving component (application or technology) reads Format ID and determines:- Ability to interpret/process- Decision as to where to route the data

Identifies 

detailed succeed
Copyright © 2004 by SAFLINK C

Format Owners

 INCITS M1:0x001B ISO/IEC SC37: 0x0101 NIST: 0x000F
Copyright © 2004 by SAFLINK C

M1 Format Types

Format Format 

Type 0x0201 Minutiae (basic) 

0x0202 Minutiae (with extension) 0x0301 Finger pattern (basic) 

0x0302 Finger pattern (extended) 

0x0401 Finger image 

0x0501 Face image 0x0601 Iris (basic) 0x0602 Iris (with extension) 0x0701-6 Signature (various) 0x0801-2 Hand Geometry (basic/ext) 
Copyright © 2004 by SAFLINK C

Patron/Client Mod

CBEFF Patron: An organization 

that has defined a standard or specification incorporating biometric data object that meets CBEFF requirements.

CBEFF Client: An entity that 

defines a specific biometric data structure (e.g., a BDB format owner) that meets CBEFF requirements. This would include any vendor, standards committee, working group, or industry consortium that has registered itself with IBIA and has defined one or more BDB format types.

Exam• Bio• ISO • SCExam• INC• Bio• Irid• Ide
Copyright © 2004 by SAFLINK C

Patron/Client Relation

CBEFF

BioAPI

BIR

X9.84

Biometric 

Object

Fut

D

Patron’s

Formats

Company A’s 

Biometric 

Data

(BSMB)

Format 

Owner

&

Format Type

Standard Body B’s

Biometric 

Data Format

(BSMB)

Client’s

Data

Derives From

Places Data 

Into

Identified By

Format 

Owner

&

Format Type

• En• Ad

• 

BIR: Biom

BDB: 
Copyright © 2004 by SAFLINK C

Header Data Eleme

 Mandatory

– SBH Security Options– Format Owner– Format Type

 Optional

– Integrit– CBEFF – Patron – Biomet– Biomet– Biomet– Biomet– Biomet– Biomet– Validity – Creato– Index– Challen– Payloa– Subhea– Produc– Patron 

Patrons can make 

optional elements 

mandatory.
Copyright © 2004 by SAFLINK C

$64,000 Question

Which patron format to use, when? Generally, application dependent

– Can be specified in a profile– Example: Draft SP 800-76

 INCITS data format standards req

defined record be incorporated wdata structure

 SC37 joint ad hoc recommended 

informative guidance document b

How can the ANSI/NIST format be u

conjunction with a CBEFF structu
Copyright © 2004 by SAFLINK C

Can’t we all just get a

 Can/should it become a patron? 

owner?

– Patron would define it’s own hea– Format owner would define it’s o

 Can/should there be a BDB for ea

type?

 Discussion during the workshop m

to some of these questions.
Copyright © 2004 by SAFLINK C

Catherine J. TiltonSAFLINK Corp.1875 Campus Commons Dr, Suite 301Reston, VA 20191

ctilt

703CelFax