B.1.5 Derived PIV Authentication Mechanisms
All changes in this version
Title
Derived PIV Authentication Mechanisms
Control
The derived PIV application supports the following validation steps:
• Credential validation (CredV) is established by verifying the certificates retrieved 986 987 988
989 990 991 992
993 994 995 996
997
998 999
1000
1001 1002
1003 1004 1005 1006 1007 1008
1009
1010
1011
1012
1013
1014
1015
1016
1017 1018 1019 from the derived PIV application and checking the validity and revocation status of these certificates.
• Derived PIV application holder validation (HolderV) is established when the authenticator holder proves knowledge of the derived PIV activation secret associated with the derived PIV credential that contains valid and unrevoked certificates.
The derived PIV application facilitates a single authentication mechanism, which is a cryptographic challenge and response authentication protocol that uses the derived PIV authentication private key as described in Appendix B.1.2 of [SP800-73pt1] with the following translations:
• References to “PIV application” are replaced with “derived PIV application.”
• References to “PIV auth certificate” are replaced with “derived PIV authentication certificate.”
• References to “PIV Card app ID” are replaced with “derived PIV application ID.”
Authentication can also be performed wirelessly over a virtual contact interface (VCI) if a VCI has been established with the derived PIV application.