2 Application of Cryptography in FIPS 201-3 (was: Application of Cryptography in FIPS 201-2)
All changes in this version
Title changed
Before · SP 800-78-4
Application of Cryptography in FIPS 201-2
After · SP 800-78-5
Application of Cryptography in FIPS 201-2201-3
Control changed
Before · SP 800-78-4
FIPS 201-2 employs cryptographic mechanisms to authenticate cardholders, secure information stored on the PIV Card, and secure the supporting infrastructure.
FIPS 201-2 and its supporting documents specify a suite of keys to be stored on the PIV Card for personal identity verification, digital signature generation, and key management. The PIV cryptographic keys specified in FIPS 201-2 and SP 800-73-4 are:
+ the asymmetric PIV Authentication key;
+ an asymmetric Card Authentication key;
+ a symmetric Card Authentication key;
+ an asymmetric digital signature key for signing documents and messages;
+ an asymmetric key management key, supporting key establishment or key transport, and up to twenty retired key management keys;
+ a symmetric PIV Card Application Administration Key; and
+ an asymmetric PIV Secure Messaging key, supporting the establishment of session keys for use with secure messaging.
The cryptographic algorithms, key sizes, and parameters that may be used for these keys are specified in Section 3.1 . PIV Cards must implement private key computations for one or more of the algorithms identified in this section.
Cryptographically protected objects specified in FIPS 201-2, SP 800-73-4, and SP 800-76-2 include:
+ the X.509 certificates for each asymmetric key on the PIV Card, except the PIV Secure Messaging key;
+ a secure messaging card verifiable certificate (CVC) for the PIV Secure Messaging key;
+ an Intermediate CVC for the public key needed to verify the signature on the secure messaging CVC;
+ a digitally signed Card Holder Unique Identifier (CHUID);
+ digitally signed biometrics using the Common Biometric Exchange Formats Framework (CBEFF) signature block; and
+ the SP 800-73-4 Security Object , which is a digitally signed hash table.
The cryptographic algorithms, key sizes, and parameters that may be used to protect these objects are specified in Section 3.2 . Certification authorities (CA) and card management systems that protect these objects must support one or more of the cryptographic algorithms, key sizes, and parameters specified in Section 3.2 . Applications may be designed to use any or all of the cryptographic keys and objects stored on the PIV Card. Where maximum interoperability is required, applications should support all of the identified algorithms, key sizes, and parameters specified in Sections 3.1 and 3.2 .
FIPS 201-2 requires CAs and Online Certificate Status Protocol (OCSP) responders to generate and distribute digitally signed certificate revocation lists (CRL) and OCSP status messages, respectively. These certificate status mechanisms support validation of the PIV Card, the PIV cardholder, the cardholder’s digital signature key, and the cardholder’s key management key.
The signed certificate status mechanisms specified in FIPS 201-2 are:
+ X.509 CRLs that specify the status of a group of X.509 certificates; and
+ OCSP status response messages that specify the status of a particular X.509 certificate.
The cryptographic algorithms, key sizes, and parameters that may be used to sign these mechanisms are specified in Section 4 . Section 4 also describes rules for encoding the signatures to ensure interoperability.
FIPS 201-2 permits optional card management operations. These operations may only be performed after the PIV Card authenticates the card management system. Card management systems are authenticated through the use of PIV Card Application Administration Keys. The cryptographic algorithms and key sizes that may be used for these keys are specified in Section 5 .
After · SP 800-78-5
FIPS 201-2201-3 employs cryptographic mechanisms to authenticate cardholders, secure information stored on the PIV Card, and secure the supporting infrastructure.201-2201-3 and its supporting documents specify a suite of keys to be stored on the PIV Card for personal identity verification, digital signature generation, and key management. The PIV cryptographic keys specified in FIPS 201-2201-3 and SP 800-73-4800-73 are:+• theThe asymmetric PIV Authentication key;,+• anAn asymmetric Card Authentication key;,+• aA symmetric Card Authentication key; (deprecated),+• anAn asymmetric digital signature key for signing documents and messages;,+• anAn asymmetric key management key, supportingthat supports key establishment or key transport, and up to twenty20 retired key management keys;,+• aA symmetric PIV Card Application Administration Key;, and+• anAn asymmetric PIV Secure Messaging key, supportingthat supports the establishment of session keys for use with secure messaging and cardholder authentication using the SM-AUTH authentication mechanism as defined in [SP800-73] .
The cryptographic algorithms, key sizes, and parameters that may be used for these keys are specified in SectionSec. 3.1 . PIV Cards must implement private key computations for one or more of the algorithms identified in this section.
Cryptographically protected objects specified in FIPS 201-2201-3, SP 800-73-4800-73, and SP 800-76-2800-76 include:+• theThe X.509 certificates for each asymmetric key on the PIV Card, except for the PIV Secure Messaging key;,+• aA secure messaging card verifiable certificate (CVC) for the PIV Secure Messaging key;,+• anAn Intermediate CVC for the public key needed to verify the signature on the secure messaging CVC;,+• aA digitally signed Card Holder Unique Identifier (CHUID);,+• digitallyDigitally signed biometrics using the Common Biometric Exchange Formats Framework (CBEFF) signature block;, and+• theThe SP 800-73-4800-73 Security Object , which is a digitally signed hash table.TheSec. 3.2 specifies the cryptographic algorithms, key sizes, and parameters that may be used to protect these objects are specified in Section 3.2 . Certification authorities (CA) and card management systems that protect these objects must support one or more of the cryptographic algorithms, key sizes, and parameters specified in SectionSec. 3.2 .
Applications may be designed to use any or all of the cryptographic keys and objects stored on the PIV Card. Where maximum interoperability is required, applications should support all of the identified algorithms, key sizes, and parameters specified in SectionsSec. 3.1 and 3.2 .201-2201-3 requires CAs and Online Certificate Status Protocol (OCSP) responders to generate and distribute digitally signed certificate revocation lists (CRL) and OCSP status messages, respectively. These certificate status mechanisms support validation of the PIV Card, the PIV cardholder, the cardholder’s digital signature key, and the cardholder’s key management key.
The signed certificate status mechanisms specified in FIPS 201-2201-3 are:+• X.509 CRLs that specify the status of a group of X.509 certificates; and+• OCSP status response messages that specify the status of a particular X.509 certificate.
The cryptographic algorithms, key sizes, and parameters that may be used to sign these mechanisms are specified in SectionSec. 4 . Section, 4which also describes rules for encoding the signatures to ensure interoperability.
FIPS 201-2201-3 permits optional card management operations. These operations may only be performed after the PIV Card authenticates the card management system. Card management systems are authenticated through the use of PIV Card Application Administration Keys. The cryptographic algorithms and key sizes that may be used for these keys are specified in SectionSec. 5 .