How PKI Readers Verify a Badge at the Door

A smart card can prove it holds a private key without sending that key to the reader. Follow the exchange from the moment someone presents a badge to the access decision.

The challenge and response

Public key infrastructure (PKI) lets the system trust a certificate from a recognized issuer and use the public key in that certificate to check a signature. The private key stays on the card.

  1. Card to Reader

    Present the certificate

    The system reads the card’s certificate and checks that it comes from a trusted issuer. The configured validation process also checks expiration and revocation as required by the deployment.

  2. Reader to Card

    Send a fresh challenge

    The reader sends a new value for this transaction. A signature from an earlier exchange will fail verification against the new value.

  3. Card to Reader

    Return and verify the signature

    The card signs the challenge with its private key. The system checks the signature against the challenge using the certificate’s public key.

Watch the homepage animation

Read NIST’s PIV authentication guidance

What the reader and controller decide

A copied badge number
A copied identifier supplies no proof of the private key. At a door configured to require PKI authentication, that credential fails the challenge.
A verified badge
After successful authentication, the access control system uses the identifier and the door’s permissions to decide whether to grant access. A verified credential can still be denied access to a particular door.
A door that requires an additional factor
Some doors require cardholder verification as well. The selected authentication method may call for a PIN or biometric check in addition to verifying the credential.