> 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/products/high-security/piv-reference.md). # PIV Reference Background on PIV credentials and the US Federal standards behind Gallagher's PIV solution. For the Gallagher solution itself, see High Security Overview. ### What is PIV? Personal Identity Verification is a US Federal standard for identifying personnel and facilitating physical and logical (computer) access. It is used in Federal facilities worldwide and is built on 3-factor authentication: * **Something you have:** the PIV card (encrypted chip data, cryptographic keys) * **Something you know:** a 6 to 8 digit PIN to activate the card * **Something you are:** a biometric stored (encrypted) on the card PIV uses Public Key Infrastructure (PKI) for uses beyond access control. ### PIV credential types | Credential | Issued to | | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- | | CAC (Common Access Card) | US Department of Defense personnel, including active-duty uniformed service, selected Reserve, DoD civilians and eligible contractors | | PIV | Employees and contractors of Federal agencies outside the DoD | | PIV-I (Interoperable) | Non-Federal organisations that need access to government data or locations | | TWIC (Transportation Worker Identification Credential) | Issued by the TSA to workers who need unescorted access to secure maritime facilities and vessels | | CIV (Commercial Identity Verification) | Organisations using Federal PIV-compatible technology under their own policy. Does not follow FIPS 201; follows NIST SP 800-63 | Legacy proximity (PROX) cards do not meet FIPS 201 requirements. ### History and standards **HSPD-12 (August 2004):** mandatory government-wide common identification standard for Federal employees and contractors (physical and logical access). **NIST:** FIPS 201 establishes PIV card criteria. A series of NIST Special Publications (SPs) defines the interface, data elements and cryptographic algorithms. **FICAM (Federal Identity, Credential, and Access Management):** coordinates US federal civilian agencies on policy, standards, architecture, product testing and Federal PKI. **FIPS 201 Evaluation Program:** common government-wide testing for commercial products. Approved products are published on the GSA Approved Products List (APL). **FIPS 201 versions:** * **FIPS 201-1 (2006):** readers-only compliance. * **FIPS 201-2 (2013):** improved testing, approved "Curb-to-Core" systems and the CSEIP training requirement. * **FIPS 201-3 (January 2022):** current standard. Aligns with OMB M-19-17, including derived PIV credentials (federation and mobile) and remote identity proofing. ### Governance (US Federal, OMB M-19-17) Each agency must maintain a single comprehensive ICAM policy, process and technology roadmap aligned with the FICAM architecture and CDM requirements, and designate an integrated agency-wide ICAM office, team and governance structure. ### Acronyms | Acronym | Meaning | | ------- | ---------------------------------------------- | | APL | Approved Products List | | CDM | Continuous Diagnostics and Mitigation | | CSEIP | Certified Systems Engineer ICAM PACS | | FICAM | Federal ICAM | | FIPS | Federal Information Processing Standards | | GSA | General Services Administration | | HSPD | Homeland Security Presidential Directive | | ICAM | Identity, Credential, and Access Management | | NIST | National Institute of Standards and Technology | | OMB | Office of Management and Budget | | PACS | Physical Access Control System | | PKI | Public Key Infrastructure | | SP | Special Publication | --- # 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/products/high-security/piv-reference.md?ask=&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.