NIST PIV and digital identity SP 800-76-2
All1 Principle (5.1) NC A Defines fingerprint minutiae10 Minimum accuracy specifications11 Conformance to this specification12 References2 Minutia Type (5.2) See Note 13 Version number MF MV 0x30323000 020\0 Second 19794-6 version - not the 2005 standard4 The record should include a single iris. This recommendation exists because one iris can easily satisfy 1:15 Number of iris6 Certification flag MF MV 0x007 Number of eyes8 Facial image data shall be converted to the sRGB color space. As stated in Clause 7.4.3.3 of [FACESTD] this9 Common header for PIV biometric data
| Ref | Title | Text | |
|---|---|---|---|
| 1 | Principle (5.1) NC A Defines fingerprint minutiae | changed here | |
| 2 | Minutia Type (5.2) See Note 1 | [MINUSTD, 5.2] defines minutiae type but contains no normative content 3. Minutia Location : Coordinate System (5.3.1) NC A Minutia placement and angle are influential on accuracy and interoperability. Developers should ensure the listed re | changed here |
| 3 | Version number MF MV 0x30323000 020\0 Second 19794-6 version - not the 2005 standard | 4. Length of record MF MV See NOTE 1 The length (in bytes) of the entire iris image data. 5. Number of iris representations MF MV 1 or 2 Number of iris representations that follow. This value would ordinarily be 1. See NOTE 4. 6. Certificat | changed here |
| 4 | The record should include a single iris. This recommendation exists because one iris can easily satisfy 1:1 | comparison accuracy objectives [IREX-III] and, moreover, a single eye will be read faster and its digital signature can be accessed and verified faster. Two eyes will be useful if one of the images is somehow of poor quality, or if one eye | changed here |
| 5 | Number of iris | representations MF MV 1 Number of iris representations that follow. | changed here |
| 6 | Certification flag MF MV 0x00 | changed here | |
| 7 | Number of eyes | represented MF MV 0 0 indicates laterality is unknown Representation 1: Data for the only eye image follows 8. Representatio d Representation Length MF MV Bytes for this representation including the header + image 9. Capture date and time | changed here |
| 7.1 in 7 |
Scope | [FIPS] establishes requirements and options for agency-collection, storage, and use of a facial image from PIV applicants. The facial imagery shall be stored in the format specified here. The face specification has a very similar format, an | changed here |
| 7.2 in 7 |
Acquisition and format | This Section provides specifications for the retention of facial images. Facial images collected during PIV Registration shall be formatted such that they conform to INCITS 385-2004 [FACESTD]. In addition to establishing a format, [FACESTD] | changed here |
| 8 | Facial image data shall be converted to the sRGB color space. As stated in Clause 7.4.3.3 of [FACESTD] this | requires application of the color profile associated with the camera in use. 7.3 Performance specifications for PIV operations [FIPS] allows automated face recognition for certain authentication purposes. Automated face recognition impleme | changed here |
| 8.1 in 8 |
Scope | This Section guides implementers of biometric enrollment and authentication applications that use biometric sensors. | changed here |
| 8.2 in 8 |
Available specifications and standards | The Biometric Identity Assurance Services standard [BIAS] standardizes remotely invoked biometric services, particularly it defines a framework for deploying and invoking biometrics-based identity assurance capabilities that can be readily | changed here |
| 9 | Common header for PIV biometric data | changed here | |
| 9.1 in 9 |
Scope | All PIV biometric data shall be embedded in a data structure conforming to Common Biometric Exchange Formats Framework [CBEFF]. This specifies that all biometric data shall be digitally signed and uniformly encapsulated. This covers the fol | changed here |
| 9.2 in 9 |
The CBEFF Header | The CBEFF Header specified in Table 14 and its notes has been established by NIST as Patron Format "PIV". This format has been established as a formal Patron Format per the provisions of [CBEFF, 6.2]. It adds definitive data types and the F | changed here |
| 9.3 in 9 |
The CBEFF Signature Block | The CBEFF_SIGNATURE_BLOCK contains the digital signature of the biometric data and thus facilitates the verification of the integrity of the biometric data. The process of generating a CBEFF_SIGNATURE_BLOCK is described as follows. The CBEF | changed here |
| 10 | Minimum accuracy specifications | changed here | |
| 10.1 in 10 |
Scope | This Section establishes specifications for configuration of deployed biometric verification algorithms. In previous sections 23 , this document includes performance specifications for qualification of components that influence recognition | changed here |
| 10.2 in 10 |
Approach | FIPS 140-2 establishes minimum requirements for authentication for activation of cryptographic-modules. This Section defines analogous specifications for biometric person authentication. The specifications implement the primary security obj | changed here |
| 10.3 in 10 |
Operating threshold specification | The threshold applied to scores from the biometric comparison algorithms shall be set to achieve false match rates at or below the respective values in Table 16 . The threshold shall be calibrated in tests conformant to Annex A 27 . Agencie | changed here |
| 10.4 in 10 |
Conformance to accuracy specifications | The false match rate (FMR) requirements shall be assured by submitting biometric comparison algorithms to the test and calibration programs given in Table 17 . Those programs shall provide the algorithm developer with a tabulation of false | changed here |
| 10.4.1 in 10.4 |
Use of multiple samples with fixed thresholds | The thresholds are set to target particular false match rates between single fingers, irises or faces of different individuals. However, if agency policy is to allow two fingers or eyes to be used in an authentication attempt, then false ac | changed here |
| 10.5 in 10 |
Agency consideration of false rejection performance | An authentication transaction may involve several core comparisons each of which will be expected to have failure rates given by false match rates (FMR, for impostors) and false non-match rates (FNMR, for genuine comparisons). These are mat | changed here |
| 11 | Conformance to this specification | changed here | |
| 11.1 in 11 |
Conformance | Conformance to this specification will be achieved if an implementation and its associated data records conform to normative (" shall ") Sections 3 through 10 but not Section 8. The following text summarizes these statements. | changed here |
| 11.2 in 11 |
Conformance to PIV registration fingerprint acquisition specifications | Conformance to Section 3.2 requires the use of an [EBTS, Appendix F] certified scanner to collect a full set of fingerprint images and the application of a segmentation algorithm and the [NFIQ]-based quality assurance procedure. Images shal | changed here |
| 11.3 in 11 |
Conformance of PIV Card fingerprint template records | Conformance to Section 3.2.2 is achieved by conformance to all the normative content of the Section. This includes production of records conformant to [MINUSTD] as profiled in Section 3.2.2 . Conformance shall be tested by inspection of the | changed here |
| 11.4 in 11 |
Conformance of PIV registration fingerprints retained by agencies | Conformance to Section 3.3 is achieved by conformance to all the normative content of the Section. This includes production of records conformant to [FINGSTD] as profiled in Section 3.3 . Conformance shall be tested by inspection of the rec | changed here |
| 11.5 in 11 |
Conformance of PIV background check records | Conformance to Section 3.4 is achieved by conformance to all the normative content of the Section. This necessitates conformance to the normative requirements of the FBI for background checks. These shall be tested by inspection of the tran | changed here |
| 11.6 in 11 |
Conformance to PIV authentication fingerprint acquisition specifications | Conformance to Section 4.7 shall be achieved if certification according to [SINGFING] is achieved, and if the resolution and area specifications are met. The [SINGFING] certification process entails inspection of output images. | changed here |
| 11.7 in 11 |
Conformance of PIV facial image records | Conformance to Section 7 shall be achieved by conformance to all the normative content of the Section. This includes production of records conformant to [FACESTD] as profiled in Section 7.2 . Conformance shall be tested by inspection of rec | changed here |
| 11.8 in 11 |
Conformance of CBEFF wrappers | A PIV implementation will be conformant to Section 9 if all biometric data records, whether or not mandated by this document or [FIPS], are encapsulated in conformant CBEFF records. CBEFF records shall be conformant if: ― The fields of the | changed here |
| 12 | References | 800-73 NIST Special Publication 800-73-4, Interfaces for Personal Identity Verification. There are currently three parts: Pt. 1- PIV Card Application Namespace, Data Model & Representation Pt. 2- PIV Card Application Card Command Interface | changed here |
33 of 33.