This document contains technical specifications for biometric data mandated or allowed in [FIPS]. These specifications reflect the design goals of interoperability, performance and security of the PIV Card and PIV processes.
This specification addresses iris, face and fingerprint image acquisition to variously support background checks, fingerprint template creation, retention, and authentication. These goals are addressed by normatively citing and mandating conformance tobiometric standards and by enumerating requirements where the standards include options and branches. In such cases, a biometric profile can be used to declare what content is required and what is
optional. This document goes further by constraining implementers' interpretation of the standards. Such restrictions are designed to ease implementation, assure conformity, facilitate interoperability, and ensure performance, in a manner tailored for PIV applications.
The biometric data specifications herein are mandatory for biometric data carried in the PIV Data Model (Appendix A
of [800-73, Part 1]). Biometric data used outside the PIV Data Model is not within the scope of this standard.
This document does however specify that most biometric data in the PIV Data Model shall be embedded in the CommonBiometric Exchange Formats Framework [CBEFF] structure of Section 9.
This supports record integrity (using digital signatures) and multimodal encapsulation.
This document provides an overview of the strategy that can be used for testing conformance to the standard. It is not meant to be a comprehensive set of test requirements that can be used for certification or demonstration of compliance to the specifications in this document. NIST Special Publications 800-85A and 800-85-B [800-85] implements those objectives.
http://csrc.nist.gov/publications/nistpubs/800-76-2/sp800_76_2.pdf
Showing posts with label PKI. Show all posts
Showing posts with label PKI. Show all posts
Monday, 15 July 2013
Tuesday, 14 May 2013
Homomorphic Encryption - Cloud Computing compatible with Privacy
Suppose that you want to delegate the ability to process your data, without giving away access to it. Craig Gentry at the IBM T.J. Watson Research Center shows that this separation is possible.
He describes a fully homomorphic encryption scheme that keeps data private, but that allows a worker that does not have the secret decryption key to compute any (still encrypted) result of the data, even when the function of the data is very complex.
In short, a third party can perform complicated processing of data without
being able to see it. Among other things, this helps make cloud computing compatible with privacy.
http://crypto.stanford.edu/craig/easy-fhe.pdf
Subscribe to:
Posts (Atom)