Identity proofing and authentication levels: NIST SP 800-63-4 and the rules that use them
| Rule | Level or method required | Scope | Source |
|---|---|---|---|
| NIST SP 800-63-4: identity assurance levels (IAL1 to IAL3)1 | Level or method requiredIAL1: core attributes validated against authoritative or credible sources and linked to the applicant. IAL2: additional evidence and a more rigorous process for validating evidence and verifying identity. IAL3: adds a trained proofing agent in an on-site attended session and the collection of at least one biometric.1 | ScopeGuidelines for identity proofing; organizations must document a process for selecting initial assurance levels based on the potential impact of failures in the digital identity system.1 | SourceNIST SP 800-63-4 (July 2025), sections 3.3.2.1 and 3.3.31 |
| NIST SP 800-63-4: authentication assurance levels (AAL1 to AAL3)1 | Level or method requiredAAL1: single-factor or multi-factor authentication. AAL2: proof of two distinct authentication factors, approved cryptography. AAL3: a public-key cryptographic authenticator with a non-exportable private key that provides phishing resistance.1 | ScopeGuidelines for authentication; NIST's summary links AAL2 to services where users can view or change their own personal information.1 | SourceNIST SP 800-63-4 (July 2025), section 3.3.2.2 and Table 21 |
| NIST SP 800-63-4: federation assurance levels (FAL1 to FAL3)1 | Level or method requiredFAL1: protects against forged assertions. FAL2: also protects against assertion injection. FAL3: protects against identity provider compromise.1 | ScopeGuidelines for federation between identity providers and relying parties; NIST's summary links FAL2 to access to personal information with AAL2 or above.1 | SourceNIST SP 800-63-4 (July 2025), section 3.3.2.3 and Table 31 |
| OMB M-26-18, Login.gov universal sign-on2 | Level or method requiredNo single level set. Agencies should weigh their own risks, user populations and desired outcomes, consistent with NIST guidelines, to set an appropriate IAL for each service or transaction, and within 240 days conduct a Digital Identity Risk Management process, including selection of assurance levels, for public-facing digital services with authentication or verification, consistent with NIST SP 800-63-4.2 | ScopePublic-facing agency websites for services the public reaches through user authentication.2 | SourceOMB Memorandum M-26-18 (August 31, 2026), section III and Appendix2 |
| IRS Publication 1075, control IA-23 | Level or method requiredMulti-factor authentication for privileged accounts (except direct terminal access from within a restricted area) and non-privileged accounts. For remote access, one factor must come from a device separate from the system gaining access, and that device must meet AAL2 per NIST SP 800-63.3 | ScopeOrganizational users (employees, contractors and similar) of agency systems that handle federal tax information.3 | SourceIRS Publication 1075 (Rev. 11-2021), IA-2, control enhancements CE-1, CE-2 and CE-63 |
| IRS Publication 1075, public-facing systems3 | Level or method requiredIAL2 when an account is established and AAL2 at each login; FAL2 may be used for federated identities. The publication cites NIST SP 800-63-3.3 | ScopePublic-facing systems through which members of the public can access federal tax information.3 | SourceIRS Publication 1075 (Rev. 11-2021), section 3.3.83 |
| CJIS Security Policy v6.1, IA-5 j (AAL2 specific requirements)4 | Level or method requiredCredential service providers authenticating at AAL2 are assessed on criteria including: a multi-factor authenticator or two single-factor authenticators (one a memorized secret, one possession-based), approved cryptography, and at least one replay-resistant authenticator. IA-2 (1) and (2) require multi-factor authentication for privileged and non-privileged accounts.4 | ScopeCredential service providers authenticating claimants at AAL2 under the CJIS Security Policy.4 | SourceCJIS Security Policy v6.1 (June 25, 2026), IA-5 j and IA-2 (1), (2)4 |
| FTC Safeguards Rule5 | Level or method requiredMulti-factor authentication for any individual accessing any information system, unless the Qualified Individual approves in writing reasonably equivalent or more secure access controls. Multi-factor means at least two of knowledge, possession and inherence factors. No NIST assurance level is named.5 | ScopeFinancial institutions subject to 16 CFR part 314, Standards for Safeguarding Customer Information.5 | Source16 CFR 314.2(k) and 314.4(c)(5)5 |
| NYDFS Cybersecurity Regulation, section 500.126 | Level or method requiredMulti-factor authentication for any individual accessing any information system. Entities with the limited exemption must use it for remote access to their systems, remote access to third-party applications with nonpublic information, and all privileged accounts other than service accounts that prohibit interactive login. If the covered entity has a CISO, the CISO may approve in writing reasonably equivalent or more secure compensating controls, reviewed at least annually. No NIST assurance level is named.6 | ScopeCovered entities under 23 NYCRR Part 500. The limited exemption covers entities with fewer than 20 employees and independent contractors (counting affiliates), less than $7,500,000 in gross annual revenue in each of the last three fiscal years, or less than $15,000,000 in year-end total assets (including affiliates).6 | Source23 NYCRR 500.1(j), 500.12 and 500.19(a)6 |
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
Method
We read the level definitions in NIST SP 800-63-4 (sections 3.3.2 and 3.3.3), then each rule that points to them, or to multi-factor authentication generally, in its official text: OMB M-26-18 on whitehouse.gov, the current IRS Publication 1075 PDF (Rev. 11-2021, which cites SP 800-63-3), the FBI's CJIS Security Policy v6.1 PDF, dated 06/25/2026 (section 1.5 says version 6.0 and later may be posted and shared without restrictions), 16 CFR part 314 through the eCFR, and the DFS copy of 23 NYCRR Part 500. Each cell says only what the source says; where a rule names no NIST level, the cell says so. All sources were opened and every cell checked on 2026-11-14. The CJIS row was first written from version 6.0 (12/27/2024); IA-2 (1) and (2) and the IA-5 j criteria cited here read the same in version 6.1 (IA-5 j (6) now names federal government agencies). The FBI's CJIS resource center page still could not be opened on 2026-11-14, so whether a version after 6.1 exists was not checked. This table explains the rules; it is not legal advice.
Notes
- NIST's level summaries (Tables 1 to 3 of SP 800-63-4) give control objectives and typical user profiles for each level; the companion volumes SP 800-63A, 63B and 63C provide the requirements for identity proofing, authentication and federation at each level.
Sources
- National Institute of Standards and Technology. NIST SP 800-63-4, Digital Identity Guidelines (July 2025). Checked .
- Office of Management and Budget. M-26-18, Scaling Use of Login.gov to Deliver a Universal Sign-on for Public Services. Checked .
- Internal Revenue Service. IRS Publication 1075 (Rev. 11-2021), Tax Information Security Guidelines for Federal, State and Local Agencies, section 3.3.8 and control IA-2. Checked .
- Federal Bureau of Investigation, Criminal Justice Information Services Division. Criminal Justice Information Services (CJIS) Security Policy, version 6.1 (June 25, 2026), IA-2 and IA-5. Checked .
- Federal Trade Commission. 16 CFR part 314, Standards for Safeguarding Customer Information, sections 314.2(k) and 314.4(c)(5). Checked .
- New York State Department of Financial Services. 23 NYCRR Part 500, Cybersecurity Requirements for Financial Services Companies, sections 500.1, 500.12 and 500.19 (DFS copy; DFS notes it is not an official version). Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed .
Spotted an error? Tell us and we will check it and correct the table where needed.