Before a system can authenticate you, it must first establish who you are. SP 800‑63A is the volume of the NIST Digital Identity Guidelines suite that defines how organizations collect evidence of identity, validate that evidence, and enroll individuals into their systems, all while balancing security rigor with equitable access (National Institute of Standards and Technology [NIST], 2025a).
Document Background
SP 800‑63A is the “A” volume of the four‑part SP 800‑63 suite. The parent document (SP 800‑63) provides the risk‑management framework. The A volume covers identity proofing and enrollment. The B volume (SP 800‑63B, covered in a separate reference on this site) addresses authentication and authenticator management. The C volume (SP 800‑63C) handles federation and assertions (NIST, 2025a).
Identity proofing answers a deceptively simple question: Is this person really who they say they are? This question must be answered before any credentials are issued. If the proofing process fails, everything built on top of it—passwords, MFA tokens, access permissions—is compromised from the start because you have given the right credentials to the wrong person.
Think of digital identity as a three‑link chain. Link one is identity proofing (63A): proving who you are. Link two is authentication (63B): proving it is still you each time you return. Link three is federation (63C): letting one system vouch for your identity to another. A weak first link undermines the entire chain, no matter how strong the authentication or federation layers are.
What Is Identity Proofing?
Identity proofing is the process of collecting, validating, and verifying information about a person to establish that they are a real individual and that the identity they claim is genuinely theirs. NIST breaks this process into three distinct steps (NIST, 2025a, Section 4).
Resolution
Resolution is the first step. The applicant provides identity information (name, date of birth, address) and evidence (a driver’s license, passport, or other document). The goal of resolution is to distinguish the applicant from all other individuals and arrive at a single claimed identity. If two applicants share the same name and birthdate, resolution uses additional attributes or evidence to tell them apart.
Validation
Validation confirms that the identity evidence itself is genuine and not counterfeit, expired, or revoked. For a physical document, this might mean checking security features (holograms, microprinting, UV features). For an electronic document, it could mean querying the issuing authority’s database to confirm the document number is valid and has not been reported lost or stolen.
Verification
Verification confirms that the applicant is the person described by the validated evidence. This is where the process connects the document to the living person standing in front of you (or appearing on a video call). Verification might involve comparing a photograph on the document to the applicant’s face, confirming a biometric sample, or verifying knowledge that only the true holder of that identity would possess.
When you open a bank account in person, the teller asks for your driver’s license (resolution and evidence collection), examines the license for signs of tampering (validation), and compares the photo on the license to your face (verification). SP 800‑63A formalizes exactly this kind of everyday process into a rigorous framework.
The Three IALs
SP 800‑63A defines three Identity Assurance Levels (IALs) that describe how much confidence an organization has that the person using a system is who they claim to be. The appropriate IAL depends on the risk associated with getting it wrong (NIST, 2025a, Section 3).
| Level | Proofing Requirement | Evidence | Typical Use Case |
|---|---|---|---|
| IAL1 | No identity proofing required. The identity is self‑asserted by the user. | None required | Public comment forums, newsletter sign‑ups, low‑risk government services |
| IAL2 | Remote or in‑person proofing. Evidence is collected and validated; the applicant is verified against the evidence. | One piece of strong evidence (e.g., a passport) or two pieces of fair evidence (e.g., a utility bill plus a state ID) | Tax filing, benefits enrollment, healthcare portals, university account provisioning |
| IAL3 | In‑person or supervised remote proofing. Strong evidence verification with additional safeguards. | Two pieces of strong evidence, with verification by a trained operator in a controlled environment | Federal employee credentialing (PIV cards), law enforcement systems, critical infrastructure access |
A key principle in Rev. 4 is that organizations should select the lowest IAL that adequately addresses their risk. Requiring IAL3 for a low‑risk service creates unnecessary barriers and costs without proportional security benefit. Conversely, using IAL1 for a system that controls access to sensitive personal data leaves the system vulnerable to impersonation (NIST, 2025a).
The parent document, SP 800‑63‑4, provides a detailed risk assessment process for selecting the appropriate IAL. Organizations assess the potential harm from identity proofing failures across six impact categories: inconvenience, financial loss, organizational harm, harm to agency programs, harm to public interests, and civil liberties impact. The worst‑case category determines the minimum IAL.
Evidence and Verification
SP 800‑63A categorizes identity evidence by its strength, which depends on how difficult the evidence is to forge and how reliably it can be verified against an authoritative source (NIST, 2025a, Section 4.3).
Evidence Strength Tiers
-
Unacceptable evidence
Documents that are easily obtained without any identity verification, such as a library card or a store loyalty card. These provide essentially no assurance that the bearer is who they claim to be.
-
Fair evidence
Documents issued by a recognized authority that required some identity verification at issuance. A utility bill, bank statement, or employer ID card falls into this category. Fair evidence is useful as supplementary proof but is not strong enough on its own for IAL2.
-
Strong evidence
Government‑issued documents with robust security features that are difficult to forge, such as a driver’s license, state ID card, or passport. Strong evidence was issued through a process that itself required identity proofing, creating a chain of trust back to authoritative records.
-
Superior evidence
Documents issued under a highly controlled process that includes in‑person appearance and multi‑step verification, such as a U.S. passport issued with the applicant’s in‑person appearance, or a Real ID‑compliant driver’s license. Superior evidence provides the highest level of confidence.
Verification Methods
Once evidence is collected and validated, the applicant must be connected to that evidence. Rev. 4 recognizes several verification methods (NIST, 2025a, Section 4.4):
Physical comparison: A trained operator compares the photograph on the evidence to the applicant’s physical appearance. This is the traditional method used at bank branches, DMV offices, and government service centers.
Biometric comparison: An automated system compares a biometric sample (typically a facial image) captured from the applicant to the image on the evidence or in an authoritative database. Rev. 4 includes detailed requirements for biometric system performance, including presentation attack detection (anti‑spoofing measures).
Address confirmation: An enrollment code is sent to an address of record (physical mail or validated phone number) to confirm the applicant has access to that address. This provides weaker verification than biometric or physical comparison but can supplement other methods.
Equity Considerations in Rev. 4
One of the most significant changes in Rev. 4 is the addition of explicit requirements around equity, inclusion, and accessibility in the identity proofing process. This was a major focus of the public comment period and reflects a growing recognition that identity systems can inadvertently exclude vulnerable populations (NIST, 2025a, Section 5).
The Problem Rev. 4 Addresses
Traditional identity proofing processes often assume that every applicant has a driver’s license, a fixed home address, a smartphone, reliable internet access, and a face that matches their government ID photograph. These assumptions exclude many legitimate users: people experiencing homelessness, individuals in the process of legal name or gender changes, people in rural areas with limited internet connectivity, elderly individuals unfamiliar with video‑based proofing, and people with disabilities that affect biometric capture.
What Rev. 4 Requires
-
Multiple proofing pathways
Organizations should offer both remote and in‑person proofing options wherever feasible. A system that only accepts video‑based proofing excludes people without webcams or reliable internet. A system that requires in‑person visits excludes people with mobility limitations or those far from service centers.
-
Diverse evidence acceptance
Not everyone has a passport or a Real ID‑compliant driver’s license. Rev. 4 encourages organizations to accept a broader range of evidence types and combinations, as long as the overall strength of the evidence meets the required IAL.
-
Biometric performance across demographics
Facial recognition systems have well‑documented disparities in accuracy across different skin tones, ages, and genders. Rev. 4 requires that organizations evaluate the performance of their biometric systems across demographic groups and take steps to mitigate disparities.
-
Accessible processes
Proofing interfaces must be accessible to people with disabilities, consistent with Section 508 requirements. This includes providing alternatives when a step in the process cannot be completed using assistive technology.
Equity is not just a social concern; it is a security concern. When legitimate users are excluded from the identity proofing process, they either abandon the service (reducing the system’s value) or seek workarounds that may be less secure (such as sharing credentials with someone who was able to complete the process). An identity system that does not serve all legitimate users is a system that has failed its mission.
Relationship to SP 800‑63B
SP 800‑63A and SP 800‑63B are designed to work together. The A volume establishes who the person is (identity proofing), and the B volume determines how the system will recognize that person on subsequent visits (authentication). The two volumes are connected through the concept of assurance levels (NIST, 2025a; NIST, 2025b).
IAL and AAL: Two Sides of the Same Coin
Identity Assurance Level (IAL) measures the confidence in the identity proofing process. Authenticator Assurance Level (AAL) measures the confidence in the authentication process. A system that requires high confidence in both dimensions will pair a high IAL with a high AAL. However, the two levels do not have to match.
| Use Case | IAL | AAL | Rationale |
|---|---|---|---|
| Anonymous forum | IAL1 | AAL1 | No real identity needed; single‑factor authentication is sufficient. |
| University student portal | IAL2 | AAL2 | Student identity is verified at enrollment; MFA protects academic records. |
| Federal employee system (PIV) | IAL3 | AAL3 | In‑person proofing with hardware‑bound authenticator for maximum assurance. |
| Pseudonymous health survey | IAL1 | AAL2 | Real identity is not needed, but the account must be protected from takeover because it contains sensitive health data. |
The last row in the table illustrates an important point: you can have strong authentication without strong identity proofing. A system that collects sensitive data from anonymous users still needs to protect those accounts from unauthorized access, even though it never verified the user’s real‑world identity. IAL and AAL are independent dimensions, and organizations should set each one based on the specific risks involved.
Citing This Document (APA 7)
SP 800‑63A‑4 follows the same APA 7 citation pattern as other NIST Special Publications. The issuing agency is the author, the publication number is the report identifier, and the parent department is the publisher.
- Reference list entry
- National Institute of Standards and Technology. (2025). Digital identity guidelines: Identity proofing and enrollment (NIST Special Publication 800‑63A‑4). U.S. Department of Commerce. https://doi.org/10.6028/NIST.SP.800‑63a‑4
- First in‑text citation (introduces the abbreviation)
- (National Institute of Standards and Technology [NIST], 2025)
- Subsequent in‑text citations
- (NIST, 2025)
- Citation referencing a specific section
- (NIST, 2025, Section 4.3)
- Narrative citation
- The National Institute of Standards and Technology (NIST, 2025) defines three Identity Assurance Levels for identity proofing.
When citing multiple volumes of SP 800‑63 in the same paper, distinguish them in the reference list by their subtitles and publication numbers. In‑text, you can use letter suffixes in the year if needed for clarity (e.g., NIST, 2025a for the A volume and NIST, 2025b for the B volume).
References
- National Institute of Standards and Technology. (2025a). Digital identity guidelines: Identity proofing and enrollment (NIST Special Publication 800‑63A‑4). U.S. Department of Commerce. https://doi.org/10.6028/NIST.SP.800‑63a‑4
- National Institute of Standards and Technology. (2025b). Digital identity guidelines: Authentication and authenticator management (NIST Special Publication 800‑63B‑4). U.S. Department of Commerce. https://doi.org/10.6028/NIST.SP.800‑63b‑4
- National Institute of Standards and Technology. (2025c). Digital identity guidelines (NIST Special Publication 800‑63‑4). U.S. Department of Commerce. https://pages.nist.gov/800‑63‑4/