> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/piv-card-support/configuring-a-piv-card-reader.md).

# Configuring a PIV Card Reader

### Introduction

The PIV reader is distributed as a new 'part', separated from standard readers. This procedure describes how to configure a PIV card reader in Command Centre.

Operators require the "Edit Site" privilege in the appropriate division to be able to create, edit and delete PIV Card Readers.

**Note:** The "View Site" privilege in the appropriate division will allow an operator to view (but not edit) PIV Card Readers.

### Procedure

1. Complete the reader configuration as per the procedure for [Creating Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-readers.md), and then go to Step 2 of this procedure.

   **Note:** If configuring an HBUS PIV Terminal, refer to the procedure [Configuring an HBUS Terminal](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/configuring-hbus-terminals/configuring-an-hbus-terminal.md). If configuring an HBUS PIV Contact Card Reader, refer to the procedure [Configuring an HBUS Contact Card Reader](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/configuring-an-hbus-contact-card-reader.md).
2. If you want to restrict the reader to reading PIV cards only, click the **Advanced** tab and deselect all **Permitted Card Technology** checkboxes, except the PIV or PIV Contactless checkbox.

   **Notes:**

   * For the HBUS Contact Card Reader to accept both contact and contactless PIV cards, check the **PIV Contactless** checkbox in the Permitted Card Technology section.
   * You will only be able to do this if you have the "Configure Site" operator privilege as well as the "Edit Site" privilege.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b70d52a0be976f78713228ff34c9aaa4db5877ef%2Fpiv_1.png?alt=media)
3. Click the **PIV Settings** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f39dcccd15d3bed235bcad2eca80f82965558434%2Fpiv_2.png?alt=media)
4. Change the **PIV card data rate** if necessary by selecting another rate from the drop-down list. The PIV reader supports card data rates of 106 (the default), 212, 424 and 848 kbps.

   **Note:** If a card cannot support the selected rate, then the highest supported rate will be used.
5. Select the appropriate Authentication Mode by clicking the relevant radio button. By default, **Require PIV cards to contain a Card Authentication Key (CAK) certificate** is selected.

   **Notes:**

   * Only one authentication mode can be selected.
   * PIV Authentication mode is only valid when using PIV Contactless cards.
   * Regardless of the PIV Authentication mode selected, when the card is inserted at a High Sec T21 Reader, it always looks for CAK and then for PIV key when CAK is absent.
   * When Cards don't have CAK certificate, the cardholder will be prompted to insert the card at a High Sec T21 Reader and prompted to enter PIV PIN to validate the PIV Certificate.
   * The **Allow fallback to CHUID>FASC-N authentication if card contains no CAK certificate (Not FIPS201 compliant)** option allows a reader to fallback to the CHUID> FASC-N when the PIV Card does not contain a CAK certificate, but this is not FIPS201 compliant.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/piv-card-support/configuring-a-piv-card-reader.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
