An authentication stack can tick every box for "MFA" and still fail NIST SP 800-63B-4, because revision 4 judges authenticators by phishing resistance, key exportability, retry limits and session timers rather than by factor count. SP 800-63B-4, Authentication and Authenticator Management, was published as final on 31 July 2025 alongside the rest of the revision 4 suite and supersedes SP 800-63B (revision 3, last updated March 2020). Auditors and federal agencies test to it, and many private sector password and MFA policies cite it. This guide is for IAM engineers, architects and assessors who need to map real authenticators, policies and session settings to AAL1, AAL2 and AAL3. The suite overview is in the NIST SP 800-63 Digital Identity Guidelines Guide; this page goes into the requirements and how to run them.
Key takeaways
- AAL2 now has a phishing-resistant floor. Verifiers must offer at least one phishing-resistant option at AAL2, and federal agencies must require it for staff, contractors and partners.
- Synced passkeys stop at AAL2. Syncable authenticators are explicitly allowed up to AAL2 under Appendix B and shall not be used at AAL3, which requires non-exportable keys.
- Password rules are simple and strict. Minimum 15 characters when a password is the only factor, 8 when used within MFA, no composition rules, no forced rotation, and a mandatory blocklist check.
- Codes you type are never phishing-resistant. OTPs and out-of-band codes lack session binding; only channel binding or verifier name binding (as in WebAuthn) qualifies.
- Session timers are part of the AAL. AAL2 reauthentication should be no more than 24 hours overall and 1 hour of inactivity; AAL3 shall be no more than 12 hours overall, with inactivity of 15 minutes or less recommended.
What it is and who it applies to
SP 800-63B-4 sets the technical requirements for authenticators, verifiers, authenticator lifecycle events and authenticated sessions at three authenticator assurance levels (AALs). It is normative for US federal agencies and the CSPs and verifiers that serve them. Outside government it is the reference most often used for password policy, MFA strength claims and passkey acceptance, and frameworks such as SP 800-53 (IA-5) and many sector regulators point to it.
- Normative sections: 2 (AAL requirements), 3 (authenticator and verifier requirements), 4 (authenticator event management, including binding, recovery, loss and expiry), 5 (session management) and Appendix B (syncable authenticators).
- Informative sections: security, privacy and customer experience considerations, and the appendix on password strength.
- Who acts on it: IAM and CIAM teams configuring identity providers, application teams running their own login, help desks handling resets, and assessors checking claims of AAL2 or AAL3.
The AAL itself is chosen in the Digital Identity Risk Management (DIRM) process in the base volume, SP 800-63-4. Federal agencies shall select at least AAL2 when personal information is made available online.
Structure and key requirements
The three AALs
| Requirement | AAL1 | AAL2 | AAL3 |
|---|---|---|---|
| Factors | Single factor allowed (password, look-up secret, OOB, OTP or cryptographic) | Multi-factor authenticator, or two single-factor authenticators including a physical one | Multi-factor cryptographic, or single-factor cryptographic plus password or biometric |
| Phishing resistance | Not required | At least one phishing-resistant option shall be offered; federal workforce shall use it | Required |
| Replay resistance | Not required | At least one authenticator shall be replay-resistant | Required |
| Authentication intent | Not required | Should be shown by at least one authenticator | Shall be shown |
| Key exportability | Any | Syncable authenticators allowed (Appendix B) | Non-exportable keys only; syncable shall not be used |
| FIPS 140 | Approved cryptography; validation not required for authenticators | Federal-procured cryptographic authenticators Level 1 | Authenticators Level 1 overall or higher; verifiers Level 1 or higher |
| Overall reauthentication | Should be 30 days or less | Should be 24 hours or less | Shall be 12 hours or less |
| Inactivity timeout | May apply | Should be 1 hour or less | Should be 15 minutes or less |
At AAL2, after an inactivity timeout but before the overall timeout, the verifier may allow reauthentication with only a password or biometric comparison plus the session secret. At AAL3, reauthentication has the same requirements as initial authentication.
Authenticator type requirements
| Authenticator | Key requirements (Section 3.1) | Phishing-resistant? |
|---|---|---|
| Password | Min 15 characters single-factor, 8 within MFA; max at least 64 should be allowed; no composition rules or periodic change; blocklist check of the full password; allow password managers and autofill (paste should be permitted); no hints or security questions; salted (at least 32 bits) and hashed | No |
| Look-up secret | At least six decimal digits or equivalent; single use; stored hashed | No |
| Out-of-band | Email shall not be used; the secret must be transferred between channels (approve-only prompts are not acceptable); valid 10 minutes; single use; PSTN is a restricted authenticator | No |
| OTP (single and multi-factor) | At least 112-bit key; time-based values change at least every two minutes; each OTP accepted once | No |
| Cryptographic (software or hardware) | Challenge nonce of at least 64 bits; non-exportable keys in a hardware-isolated environment at AAL3 | Yes, when used with channel binding or verifier name binding |
| Biometric | Only with a physical authenticator; FMR 1 in 10,000 or better across demographic groups; voice comparison shall not be used; PAD required for facial recognition | Not a standalone authenticator |
Two retry limits apply. Consecutive failed attempts shall be limited to 100 per authenticator, after which it is disabled and must be rebound. Activation secrets (the PIN or biometric that unlocks a multi-factor authenticator) shall be at least 4 characters, should be 6, and shall disable the authenticator after no more than 10 consecutive failures. The full password rule set and policy wording are in the Password Policy Guide (NIST-aligned).
Phishing resistance, defined precisely
- Channel binding: the authenticator output is bound to the authenticated protected channel, and the verifier validates the binding. Client-authenticated TLS with PIV or CAC is the example given.
- Verifier name binding: the output is cryptographically bound to the verifier's authenticated identifier, for DNS the hostname or a parent domain at least one level below the public suffix. WebAuthn and FIDO2 are the example.
- What does not qualify: any manually entered output, so OTP apps, SMS and push-with-number-match codes are not phishing-resistant, however strong their keys.
Wireless connections between authenticator and endpoint (for example cross-device passkey flows) shall require physical proximity. See the Phishing-Resistant MFA Guide for deployment patterns.
Syncable authenticators (Appendix B)
Appendix B carries forward the requirements NIST first issued in its April 2024 supplement on syncable authenticators (synced passkeys). The main requirements:
- keys exported to a sync fabric shall be stored only in encrypted form, using a key of at least 112 bits; encryption should use a user-controlled secret;
- private-key operations shall happen on the local device;
- access to synced keys shall require AAL2-equivalent multi-factor authentication to the sync fabric;
- verifiers shall request user verification and check the User Verified (UV) flag, and treat the authenticator as single-factor when UV is not set;
- verifiers may use the Backup Eligible (BE) and Backup State (BS) flags to restrict syncable or synced keys, but public-facing applications should not refuse keys on the BS flag alone;
- for federal enterprise use, sync fabrics shall have FISMA moderate protections or equivalent, devices shall be managed to stop syncing to unauthorised fabrics, sync access shall use agency-managed accounts, and attestation should be supported;
- for public-facing applications, assume any syncable authenticator may be shared with others.
Restricted authenticators
At publication the only restricted authenticator is out-of-band authentication over the public switched telephone network (SMS and voice). A CSP using it shall offer at least one unrestricted alternative that meets the required AAL, give subscribers meaningful notice of the risks, address the risk in its assessment and include a migration plan in its Digital Identity Acceptance Statement (DIAS).
Event management and sessions
- Binding (Section 4): the CSP shall keep a record of all bound authenticators and their characteristics (single or multi-factor, phishing-resistant or not) and the date and time of significant lifecycle events. Subscribers should be encouraged to hold at least two authenticators.
- Recovery (Section 4.2): when a subscriber cannot authenticate at the required AAL, the recovery procedures of Section 4.2 shall be used. These include saved recovery codes and issued recovery codes, followed by an account recovery notification.
- Loss and theft: the CSP shall provide a way to invalidate an authenticator immediately on notification of loss, theft or compromise.
- Sessions (Section 5): browser cookies are not authenticators; they are acceptable only as short-term session secrets. Session secrets come from the verifier at authentication and establish continuity until the reauthentication timers fire.
Identity and NHI requirements
SP 800-63B-4 is written for human subscribers. Service accounts, API keys, workload credentials and AI agents are out of scope, and an AAL label on a machine credential means nothing. The volume still shapes NHI practice in three ways:
- Verifier secrets are NHIs. OTP seeds, the keyed-hash key for password storage (which should be held separately in hardware-protected storage) and assertion signing keys are machine secrets. Store them in an HSM or key management service and rotate them; see the Secrets Management Guide.
- Session tokens outlive authentication. A stolen session secret bypasses every AAL control. The CircleCI breach began with a session cookie stolen from an engineer's laptop after 2FA had already been completed. Device-bound sessions and short timers reduce that window; see the Device-Bound Session Credentials Guide.
- Agents acting for users: when an AI agent acts on a user's behalf, the user's AAL applies to the user's sign-in, not to the token the agent holds. Bind delegated tokens to the agent's own credential and keep their lifetime shorter than the user's reauthentication interval.
Implementation steps
- Inventory authenticators per application. For every sign-in path (web, mobile, VPN, admin console, legacy protocol), list the authenticators accepted, recovery methods and session settings. Legacy protocols that accept only a password cap the whole application at AAL1.
- Classify each authenticator. Use the Section 3 type, single or multi-factor, phishing-resistant or not, exportable or not. Record this in the IdP or IGA tool so policy can use it.
- Fix password policy first. Remove composition and expiry rules, raise the minimum to 15 characters for password-only access, add a compromised-password blocklist, allow paste and password managers, and remove security questions. This is low cost and auditors check it early.
- Introduce phishing-resistant options at AAL2. Offer passkeys or platform authenticators to all users, then make them mandatory for administrators and high-risk groups using pilot rings (IT staff, then privileged users, then everyone). Keep an exception group with a review date as rollback. See the Passkey Rollout Guide.
- Separate AAL3 populations. Identify who needs AAL3 (for example tier-zero administrators) and issue device-bound hardware authenticators with attestation. Block synced passkeys for them using the BE flag or authenticator attestation allowlists.
- Restrict PSTN. Where SMS or voice remains, give notice, offer an unrestricted alternative and write the migration plan into the DIAS.
- Set session timers per AAL. Configure IdP and application session lifetimes to match the table above and test that inactivity and overall timers really end the session, including refresh tokens.
- Harden recovery. Make recovery codes or re-proofing the route, never a help desk override on a phone call. Notify subscribers after every recovery and authenticator binding.
Evidence and assessment
| Assessor question | Section | Evidence to keep |
|---|---|---|
| Which AAL does each application claim, and why? | SP 800-63-4 DIRM; 63B Section 2 | DIRM output, application-to-AAL register |
| Is a phishing-resistant option offered at AAL2? | 2.2 | IdP authentication policy export, enrolment statistics |
| Are password rules compliant? | 3.1.1 | Policy configuration, blocklist source and update process, hashing parameters |
| Are retry limits enforced? | 3.2.2, 3.2.10 | Lockout configuration, test results |
| How are syncable authenticators handled? | Appendix B | WebAuthn verifier settings for UV, BE and BS; attestation policy |
| Is PSTN restricted correctly? | 3.2.9 | Subscriber notice, alternatives offered, DIAS migration plan |
| Are lifecycle events recorded? | 4 | Authenticator binding and removal logs with timestamps |
| Do sessions end on time? | 2.1.3 to 2.3.3, 5 | Session configuration and test evidence |
Metrics:
- share of active users with at least one phishing-resistant authenticator, and the share of privileged users with only phishing-resistant methods;
- share of sign-ins (not users) completed with a phishing-resistant method;
- remaining SMS and voice OTP use, trending to the DIAS migration target;
- authenticator resets and recoveries per 1,000 users, with the share done through the help desk;
- median session age at the point of a sensitive transaction;
- passwords rejected by the blocklist at set or change.
Log binding, removal, recovery, lockout and reauthentication events, and alert on new authenticators registered shortly after a recovery or from a new device (ATT&CK T1098.005 Device Registration and T1556.006 Multi-Factor Authentication).
Mapping to other frameworks
| SP 800-63B-4 area | NIST SP 800-53 Rev. 5 | NIST CSF 2.0 | CIS Controls v8.1 | ATT&CK threat addressed |
|---|---|---|---|---|
| MFA at AAL2 and AAL3 | IA-2(1), IA-2(2) | PR.AA-03 | 6.3, 6.4, 6.5 | T1078 Valid Accounts |
| Replay and phishing resistance | IA-2(8) | PR.AA-03 | 6.5 | T1557 Adversary-in-the-Middle; T1111 MFA Interception |
| Password rules | IA-5(1) | PR.AA-01 | 5.2 | T1110 Brute Force |
| Cryptographic authenticators | IA-5(2) | PR.AA-03 | 6.5 | T1621 MFA Request Generation (removed by non-push methods) |
| Reauthentication and session end | IA-11, AC-12, SC-23 | PR.AA-03 | 6.2 | T1539 Steal Web Session Cookie; T1550.004 Web Session Cookie |
ISO/IEC 27001:2022 maps mainly to Annex A 5.17 (Authentication information) and 8.5 (Secure authentication).
Common pitfalls
- Calling push or SMS "phishing-resistant". Number matching reduces MFA fatigue but the code is still relayed by the user, so it fails Section 3.2.5. The Uber breach shows how push prompts are worn down; see the MFA Fatigue and Bypass Guide.
- Allowing synced passkeys for AAL3 administrators. They are exportable by design. Use attestation and the BE flag to keep tier-zero accounts on device-bound keys.
- Ignoring UV. A passkey assertion without the User Verified flag is single-factor under Appendix B.
- Leaving legacy paths open. IMAP, basic authentication or a local admin login with a password only caps the application at AAL1, whatever the main login enforces. The Snowflake breach involved accounts protected by a password alone.
- Long-lived refresh tokens. An IdP set to 24 hours means little if the application's refresh token lasts 90 days.
- Help desk resets that skip Section 4.2. Recovery by phone call reintroduces the weakest factor of all. See the Account Recovery and Help Desk Security Guide.
Practitioner checklist
- Keep an application-to-AAL register backed by the DIRM assessment.
- Classify every authenticator in the IdP by type, factor count, phishing resistance and exportability.
- Apply the Section 3.1.1 password rules, including the blocklist and removal of composition and expiry.
- Offer a phishing-resistant authenticator to every AAL2 user and require it for privileged users.
- Request and check UV on WebAuthn; decide and document your BE and BS policy.
- Restrict AAL3 to non-exportable, attested hardware keys.
- Document PSTN as restricted, with notice, alternatives and a migration plan in the DIAS.
- Set and test session and refresh token lifetimes against the AAL timers.
- Route recovery through recovery codes or re-proofing, and notify subscribers of every recovery.
- Log all authenticator lifecycle events and alert on device registration after recovery.
Standards and references
- NIST: SP 800-63B-4 Authentication and Authenticator Management
- NIST: SP 800-63B-4 Appendix B Syncable Authenticators
- NIST: SP 800-63B-4 PDF
- NIST: SP 800-63A-4 Identity Proofing and Enrollment
- NIST: SP 800-53 Rev. 5 Security and Privacy Controls
- NIST: Cybersecurity Framework 2.0
- MITRE ATT&CK: Steal Web Session Cookie
Related NHI Mgmt Group resources: NIST SP 800-63 Digital Identity Guidelines Guide · Passwordless and Passkeys Guide · NIST SP 800-63A-4 Identity Proofing Guide · NIST SP 800-63C-4 Federation Assurance Levels Guide