FBI Biometrics

***Agencies transitioning from the EFTS to the new EBTS standard are encouraged to contact the FBI CJIS Biometric Services Section’s Customer Service Group at (304) 625-5590, or via e-mail at liaison@leo.gov prior to implementation.

The FBI Criminal Justice Information Services Division is moving toward a system that will contain a complete biometric and biographic profile of the subject records in its databases. Though fingerprints will continue to be the FBI’s primary mode of identification for the near future, the scope of the EBTS has been expanded over previous versions to include additional biometric modalities (e.g., palmprint, facial, and iris) in recognition of the rapidly developing biometric identification industry. The most recent update to the American National Standards Institute (ANSI)/National Institute of Standards and Technology (NIST)-Information Technology Laboratory (ITL) 1-2007 standard includes new record types to facilitate data sharing for new biometric modalities. Integrating biometric data in accordance with the ANSI/NIST standard, the FBI EBTS provides a description of all requests and responses associated with electronic fingerprint and other biometric identification services.

The process of updating an FBI implementation of the ANSI/NIST ITL1-2007 standard involves many considerations as well as iterations of reviews and approvals. The EBTS is governed by the Advisory Policy Board (APB) process. Specifically, there is an IAFIS Interface Evaluation Task Force (IIETF) that reviews drafts to the EBTS for approval. This group provides comments, ranging from very specific to broad, to enhance the standard. The standard process takes into account the impact on legacy users, IAFIS contributors, and interoperability stakeholders particularly when adding new information and changing functionalities. The resultant changes directly affect cost considerations, business objectives, and other factors that need to be projected and reconciled accordingly.

*You must have Adobe Reader to view a PDF file.

Tech Specifications Document for RISC Prototype Project, Oct 1, 2009
EBTS Version 9.0 Nov 30, 2009.
Use comment form to submit input.
- EBTS Version 9.0
- EBTS Version 9.0 W/CHANGES

The purpose of this compliance tool is to provide users with mandatory fields for the type of transaction (TOT) selected. Type 1 TOT requirements are static but Type 2 and optional information requirements will change depending on the TOT selected.

To use the tool at the button, first select a TOT and then the requirements will be identified.

Note: The mandatory and optional fields listed also apply to EBTS XML. However, please realize that the Logical Record Length for all record types is not required (actually not represented) for EBTS XML.

Although the official comment period expired January 15, 2010, provided below are links to the two XML representations of the EBTS v9.0 specification. The first representation is the LEXS 4.0-based EBTS XML, while the second is an FBI CJIS EBTS IEPD. End users and stakeholders were requested to review both representations and provide feedback by January 15 to CJIS on which XML implementation works best for them, and which should be implemented by NGI. This feedback was based on assessments of cost, complexity, risk and any other objective evaluation factors, such as interoperability, for each alternative they saw as critical to their decisions associated with their XML implementation. Although the comment period has expired, you may provide comments which may be reviewed but not included in the analysis.

OPTION 1:

EBTS v9.0 (LEXS-based) IEPD

LEXS was created to support the primary objectives of the DOJ Law Enforcement Information Sharing Program (LEISP), and to minimize the impact of the changing requirements and varied demands for information sharing on the sources and consumers of law enforcement data. While LEXS originated from law enforcement needs, it has been designed for a broad audience and is not limited to use by the law enforcement community. LEXS is a NIEM-compliant specification that prescribes a common format for information sharing. Please click below for the comment form.

Stakeholders and end users were requested to review the EBTS 9.0 (LEXS-based) IEPD, comment review period closed on January 15, 2010. Though the comment period has closed, you may still make comments. However, your comment may not be included in the analysis.

OPTION 2:

EBTS v9.0 XML IEPD

This document contains the XML representation of EBTS Version 9.0. Stakeholder and end user review of the EBTS v9.0 XML IEPD was requested, with comments due no later than January 15, 2010. Please click below for the comment form. Though the comment period has closed, you may still make comments. However, your comment may not be included in the analysis.

OPTION 1:

EBTS v9.0 (LEXS-based) IEPD

OPTION 2:

EBTS v9.0 XML IEPD

Archive