Date Published: August 2014
Comments Due:
Email Questions to:
Supersedes:
SP 800-85B-1 (09/11/2009)
Author(s)
Ramaswamy Chandramouli (NIST), Hildegard Ferraiolo (NIST), Ketan Mehta (NIST), Jason Mohler (Electrosoft Services), Lam Ly (Electrosoft Services), Gregory Hollenbaugh (Electrosoft Services)
Announcement
NIST has produced a revised version of NIST Special Publication (SP) 800-85B, PIV Data Model Conformance Test Guidelines. The revisions include additional tests necessary to test new features added to the PIV Data Model in SP 800-73-4 Part 1. This document, after a review and comment period, will be published as NIST SP 800-85B-4.
NOTE: NIST has made a one-time change in the revision number of SP 800-85B (skipping revision numbers 2 and 3) so we can align the current publication revision to SP 800-73-4.
FIPS201 describes a variety of data model components as a part of the PIV logical credentials. Such components include biometric elements in the form of fingerprint information and facial imagery and security elements such as electronic keys, certificates, and signatures. FIPS201 incorporates by reference NIST Special Publication 800-73-4 (SP80073), which specifies elements related to the PIV card interface, NIST Special Publication 800-76, which specifies the biometric requirements, and NIST Special Publication 800-78, which specifies acceptable cryptographic algorithms and key sizes for PIV systems. A robust testing framework and guidelines to provide assurance that a particular component or system is compliant with FIPS201 and supporting standards should exist to build the necessary PIV infrastructure to support common unified processes and systems for government-wide use. NIST developed test guidelines in two parts. The first part addresses test requirements for the interface to the PIV card, which are provided in NIST Special Publication 800-85A. The second part provides test requirements for the PIV data model and is provided in this document. This document specifies the derived test requirements, and the detailed test assertions and conformance tests for testing the PIV data model.
FIPS201 describes a variety of data model components as a part of the PIV logical credentials. Such components include biometric elements in the form of fingerprint information and facial imagery and security elements such as electronic keys, certificates, and signatures. FIPS201 incorporates by...
See full abstract
FIPS201 describes a variety of data model components as a part of the PIV logical credentials. Such components include biometric elements in the form of fingerprint information and facial imagery and security elements such as electronic keys, certificates, and signatures. FIPS201 incorporates by reference NIST Special Publication 800-73-4 (SP80073), which specifies elements related to the PIV card interface, NIST Special Publication 800-76, which specifies the biometric requirements, and NIST Special Publication 800-78, which specifies acceptable cryptographic algorithms and key sizes for PIV systems. A robust testing framework and guidelines to provide assurance that a particular component or system is compliant with FIPS201 and supporting standards should exist to build the necessary PIV infrastructure to support common unified processes and systems for government-wide use. NIST developed test guidelines in two parts. The first part addresses test requirements for the interface to the PIV card, which are provided in NIST Special Publication 800-85A. The second part provides test requirements for the PIV data model and is provided in this document. This document specifies the derived test requirements, and the detailed test assertions and conformance tests for testing the PIV data model.
Hide full abstract
Keywords
biometrics; certificate conformance test; FIPS 201; identity credential; implementation under test (IUT); PIV data model; Personal Identity Verification (PIV); BER-TLV testing; smart cards
Control Families
Assessment, Authorization and Monitoring; System and Information Integrity; System and Services Acquisition
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
