BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

6.2.3 Certificate Identifiers

NIST PIV and digital identity SP 800-217 (Draft)
All changes in this version
first version loaded 6 Protocol Requirements 996 part of 6.2

Title

Certificate Identifiers

Control

The PIV authentication certificate is issued to PIV identity cardholders as part of the PIV Card and can uniquely identify a PIV identity account, as described in [FIPS201] . Within PIV federation, the PIV authentication certificate is not used for primary authentication to the RP, but it can still be referred to from the federation protocol in some important ways. For example, when used as an IdP-managed bound authenticator, the PIV authentication certificate is verified by both the PIV IdP and subsequently by the RP. For this to work, the assertion needs to communicate the identity of the certificate and its included keys in a reliable manner. The exact method of referring to the PIV authentication certificate is out of scope for this document and subject to profiling of the federation technology in use, but some common options include:

• The cryptographic hash of the public key used in the PIV authentication certificate,

• Certificate issuer (CA) and subject identifier

• CA and certificate serial number

• Subject key identifier

• The cryptographic hash of the full certificate

• The full certificate value

Each of these options has different tradeoffs and considerations, and an interoperable technical profile of this specification SHOULD define which of these are supported.