NIST SP 800-53 Rev. 5 IA-12(2) — Identity Evidence

What this control requires

Control mandates requiring individuals to present evidence of identification, such as documents or biometrics, to the registration authority to reduce fraudulent identity risks, aligned with system roles and privileges. This control supports the Identity Verification System capability within the Identification and Authentication family.

In plain English

Control mandates requiring individuals to present evidence of identification, such as documents or biometrics, to the registration authority to reduce fraudulent identity risks, aligned with system roles and privileges. 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-12(2)) and look for objective evidence on the latest two assessment cycles.

How to implement

1. Write a short policy stating intent, scope and named owner.
2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy.
3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it.
4. Review on a documented cadence and capture the review in the risk register or compliance tracker.

Operational checklist

• Access. 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.
• System. Document the trigger, the owner and the cadence.
• Identity. Document the trigger, the owner and the cadence.
• Scope: management, authentication, system, identity, review, capability, registration, evidence.

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: Identity Evidence.

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.5.1 — User Identification and Authentication
• CIS Controls v8 6.1 — Establish an Access Granting Process
• ISO/IEC 27001:2022 A.5.16 — Identity management
• SOC 2 (2017 TSC) CC6.2 — Access Provisioning

Related controls in NIST SP 800-53 Rev. 5

• Control IA-12(3) — Identity Evidence Validation And Verification
• Control IA-5(3) — In-Person Or Trusted External Party Registration
• Control IA-12(4) — In-Person Validation And Verification
• Control IA-5(16) — In-Person Or Trusted External Party Authenticator Issuance
• Control IA-4 — Identifier Management
• Control IA-4(7) — In-Person Registration

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control IA-12(2)

Topics: governance riskidentity accessprivileged accessidentity managementaccess review