Choosing an identity assurance level is a risk decision, not simply a choice between “basic” and “advanced” identity verification. This guide explains NIST IAL1, IAL2, and IAL3 in plain language, compares evidence and verification methods, and provides a practical decision process for selecting, monitoring, and revisiting the right level for a digital identity workflow.
Overview
NIST identity assurance levels, or IALs, describe how confidently an online account can be connected to a real-world person. They are part of the NIST Digital Identity Guidelines and focus on identity proofing: collecting and validating evidence about an applicant, resolving that evidence to a unique individual, and binding the resulting identity information to a digital account.
IAL is only one part of a complete identity system. It should not be confused with:
- Authentication assurance: how strongly a user proves control of an account during login.
- Federation assurance: how much confidence a relying party can place in an identity assertion from another provider.
- Authorization: what an authenticated user is allowed to do.
A strong login does not automatically mean that the person was strongly identity-proofed. Conversely, a carefully proofed account can still be compromised if its authentication controls are weak. Document verification, biometric verification, liveness detection, recovery controls, and credential management should therefore be assessed as connected but separate decisions.
IAL1: little or no identity proofing
IAL1 is appropriate when an application does not need to establish that an account corresponds to a specific real-world person. The user may provide self-asserted information, such as a name or email address, but the organization does not rely on that information as verified identity evidence.
Typical examples include low-risk discussion services, newsletters, basic personalization, or applications where users can participate under a pseudonym. IAL1 can reduce collection of sensitive personal data, which may support a privacy-preserving design. It is not suitable merely because identity verification would be inconvenient if the service makes consequential decisions about a person.
IAL2: meaningful remote or in-person proofing
IAL2 is designed for applications that need reasonable confidence that an applicant is a particular person. The process generally involves collecting identity evidence and validating it through an approved proofing method. Depending on the workflow and applicable version of the NIST guidance, this may involve remote document checks, trusted records, supervised interactions, or other comparable controls.
IAL2 commonly fits services involving financial, employment, education, healthcare, benefits, or account-recovery decisions where impersonation would cause material harm. A vendor’s ability to scan an identity document is not by itself proof that the entire workflow meets IAL2. The organization must assess evidence quality, applicant-to-evidence binding, fraud controls, exception handling, and audit records together.
IAL3: stronger, higher-confidence proofing
IAL3 is intended for situations where the consequences of accepting an impostor are especially serious. It requires stronger evidence and more rigorous proofing than IAL2. The exact acceptable methods depend on the applicable NIST edition, the use case, and the organization’s policy. Enhanced supervision, stronger evidence combinations, biometric comparison, or an equivalent high-confidence process may be relevant, but a biometric check alone does not automatically make a workflow IAL3.
IAL3 should be treated as a high-friction control reserved for genuinely high-risk use cases. Teams should document why the additional collection of personal or biometric data is necessary and how the organization will protect, retain, and delete it.
What to track
Use the following comparison as a planning aid. It is not a substitute for checking the current NIST requirements or a sector-specific rule.
| Level | Evidence and verification | User friction | Fraud resistance | Possible use cases |
|---|---|---|---|---|
| IAL1 | Self-asserted information or no meaningful real-world identity claim | Low | Low for identity impersonation; account security still matters | Low-risk accounts, pseudonymous communities, basic access |
| IAL2 | Validated identity evidence and a process that connects the applicant to that evidence | Moderate | Moderate to strong, depending on evidence, automation, review, and fraud controls | Customer onboarding, workforce access, account recovery, regulated workflows |
| IAL3 | Stronger evidence and a higher-confidence proofing process, with additional controls where required | High | Higher resistance when implemented correctly, though no level eliminates fraud | High-impact systems, sensitive privileges, or severe impersonation risks |
Track the variables behind the level
- Impact of a false acceptance: What happens if an impostor passes?
- Impact of a false rejection: Who is harmed when a legitimate applicant cannot pass?
- Evidence types: Record which documents, records, credentials, or attestations are accepted.
- Verification path: Separate automated document checks, face match verification, liveness detection, trusted-record checks, and human review.
- Exception rates: Monitor manual reviews, retries, abandoned sessions, and successful appeals.
- Fraud signals: Track repeated identities, synthetic documents, device patterns, deepfake attempts, and suspicious recovery activity.
- Privacy exposure: Record what personal or biometric data is collected, why it is needed, where it is stored, and when it is deleted.
- Operational evidence: Preserve consent records, decision logs, vendor configuration, policy versions, and reviewer actions.
For implementation teams, a credential verification API or identity verification software should expose enough event detail to distinguish a failed document check from a failed face match, a liveness concern, a policy rejection, and a technical error. That distinction is essential for both compliance review and fair user support.
Cadence and checkpoints
Identity assurance should be reviewed on a schedule rather than only after an incident. A practical operating rhythm is a monthly operational review, a quarterly risk review, and an event-driven review whenever the workflow or threat environment changes.
Monthly operational review
- Check pass, fail, retry, abandonment, and manual-review rates by country, channel, and user type.
- Review spikes in suspected fraud, duplicate identities, account recovery, or unusual reviewer overrides.
- Confirm that verification webhooks, audit logs, retention jobs, and escalation routes are functioning.
- Sample successful and failed cases to identify inconsistent decisions or accessibility problems.
Quarterly risk and compliance review
- Reassess whether the chosen IAL still matches the harm associated with account misuse.
- Review accepted evidence, vendor settings, biometric processing, consent language, and deletion controls.
- Compare the production workflow with the documented policy and current NIST guidance.
- Confirm that recovery and reproofing controls do not silently bypass the original assurance level.
Event-driven checkpoints
Trigger an additional review after a significant fraud incident, a new product capability, a change to privileged access, entry into a new jurisdiction, a material vendor change, or a revision to the applicable NIST publication or sector regulation. Regional mappings such as eIDAS identity requirements may inform the design, but they should not be treated as automatic equivalents to NIST IALs.
How to interpret changes
A rising failure rate does not automatically mean that the assurance level is too high. It may indicate poor camera guidance, unsupported identity documents, a changed vendor model, accessibility barriers, or a new technical defect. A falling failure rate is not automatically good news either: it could reflect better usability, weaker controls, or an increase in successful fraud.
Interpret results by separating four questions:
- Did the user complete the process? This is a usability measure, not proof of identity quality.
- Was the evidence authentic and valid? Document and credential checks answer only part of this question.
- Was the applicant connected to the evidence? This is where face comparison, liveness, supervised review, or another binding method may matter.
- Was the resulting account protected afterward? Authentication, recovery, session security, and monitoring determine whether the proofed account remains trustworthy.
When a workflow produces too many false rejections, improve instructions, provide an accessible alternative, and strengthen human escalation before lowering the assurance level. When false acceptance or impersonation risk rises, investigate evidence quality, replay and injection attacks, liveness performance, reviewer training, and recovery paths before simply adding more friction.
A simple decision tree
Does the application need to connect the account to a real person? If no, begin by assessing IAL1. If yes, continue.
Would an impostor cause material harm or gain access to sensitive benefits, information, or privileges? If the risk is limited, assess IAL2. If the consequences are severe, assess whether IAL3-level proofing is justified.
Can the organization support the selected process? Check evidence coverage, user support, manual review, privacy safeguards, auditability, accessibility, and recovery. If it cannot, redesign the workflow before launch rather than describing an unimplemented level as a compliance achievement.
When to revisit
Revisit the selected identity assurance level at least quarterly and whenever a material change occurs. The review should be recorded as a short decision memo containing the application’s risk, chosen IAL, accepted evidence, verification methods, exception path, privacy controls, and owner.
Use this implementation checklist:
- Define the harm caused by impersonation, mistaken rejection, and account takeover.
- Choose an IAL based on that risk, not on a vendor’s product label.
- Map each proofing step to the identity claim it supports.
- Document remote, in-person, automated, and human-review paths separately.
- Test recovery, reproofing, and support escalation against the same risk standard.
- Minimize biometric and identity data, set retention limits, and record user consent where required.
- Monitor outcomes monthly and conduct a formal risk review quarterly.
- Check current NIST guidance, applicable regional requirements, and contractual obligations before certifying the workflow.
For related operational controls, see the Digital Identity Verification Audit Checklist, the Account Recovery Identity Verification workflow, and the Biometric Data Retention Policy Template. Treat this article as a recurring review guide: update it when standards change, when measured fraud or user outcomes shift, and whenever the business begins making higher-impact decisions about a digital identity.