# NIST SP 800-53 Rev. 5 IA-2(12) — Acceptance Of Piv Credentials - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-2-12-acceptance-of-piv-credentials - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › IA — Identification and Authentication - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `IA-2(12)`·high·Component: **Identification and Authentication** ## What this control requires > Control mandates that organizations accept and electronically verify Personal Identity Verification (PIV)-compliant credentials, issued per FIPS 201, for logical and physical access control systems. This includes derived PIV credentials (per SP 800-166) and credentials like the DoD Common Access Card, with issuer reliability authorized under SP 800-79-2, aligning with IA-2, IA-5. This control supports the PIV Authentication Solution capability within the Identification and Authentication family. > > — NIST SP 800-53 Rev. 5, Control IA-2(12) ### In plain English Control mandates that organizations accept and electronically verify Personal Identity Verification (PIV)-compliant credentials, issued per FIPS 201, for logical and physical access control systems. In practice, this means you can prove you access management-level controls on a defined cadence. ## Why it matters SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan. Within **Identification and Authentication**, the assessor will trace your implementation back to the catalogue reference (Control IA-2(12)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Physical Security **Inheritance.** For cloud-only operations, inherit physical controls from the provider's SOC 2 / ISO 27001 report and document the inheritance in the SoA. ### Operational checklist - **Access.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Physical.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Authentication.** Document the trigger, the owner and the cadence. - **Scope:** management, access control, authentication, identity, review, capability, piv credentials, verification. ## Evidence to collect - **Identity Scan.** IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in. Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Acceptance Of Piv Credentials. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-171 Rev. 3 3.10.8** — Access Control for Transmission](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-10-8-access-control-for-transmission) - [**CIS Controls v8 6.7** — Centralize Access Control](https://support.icompaas.com/compliance/cis-controls-v8/6-7-centralize-access-control) - [**BSI C5:2020 PS-04** — Physical site access control](https://support.icompaas.com/compliance/bsi-c5-2020/ps-04-physical-site-access-control) - [**SOC 2 (2017 TSC) CC6.1** — Logical Access Controls](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc6-1-logical-access-controls) - [**ISO/IEC 27001:2022 A.5.15** — Access control](https://support.icompaas.com/compliance/iso-27001-2022/a-5-15-access-control) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control IA-8(1)** — Acceptance Of Piv Credentials From Other Agencies](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-8-1-acceptance-of-piv-credentials-from-other-agencies) - [**Control IA-8(5)** — Acceptance Of Piv-I Credentials](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-8-5-acceptance-of-piv-i-credentials) - [**Control IA-4(4)** — Identify User Status](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-4-4-identify-user-status) - [**Control IA-12(4)** — In-Person Validation And Verification](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-12-4-in-person-validation-and-verification) - [**Control PE-2(2)** — Two Forms Of Identification](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-2-2-two-forms-of-identification) - [**Control AC-14** — Permitted Actions Without Identification Or Authentication](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-14-permitted-actions-without-identification-or-authentication) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control IA-2(12)` Topics: identity accessidentity managementaccess reviewprivileged accessphysical security ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.