Federal public sign-in and identity assurance: M-26-18, NIST SP 800-63-4 and Login.gov
| Source and part | Who | Requirement | Level | Deadline |
|---|---|---|---|---|
| OMB M-26-18, Section I.A: Login.gov for authentication1 | WhoAgencies (44 U.S.C. 3502(1)) with public-facing websites where members of the public sign in, other than sites used only by organizations or by people acting for someone else; the statutory mandate does not cover the Department of War, national security systems or the intelligence community1 | RequirementOffer Login.gov as a sign-on option; other solutions may be offered alongside it only for needs Login.gov cannot fully meet or to avoid burden on many existing users, with Login.gov promoted as the default for new accounts1 | LevelAgencies select assurance levels and seek parity between Login.gov and any other solution offered1 | DeadlineWithin one year on High Impact Service Provider websites and within two years on all in-scope websites, or a notice to OMB with the agency head's certification1 |
| OMB M-26-18, Sections I.B and III: identity verification1 | WhoAgencies whose public-facing websites require identity verification as well as sign-in1 | RequirementUse Login.gov's identity verification service unless it does not meet the user base, risk profile or operations of the service1 | LevelAgencies set the IAL for each service and should accept all suitable Login.gov offerings at that IAL1 | DeadlineNo separate date for this duty; a Digital Identity Risk Management process, including selection of assurance levels, within 240 days1 |
| NIST SP 800-63-4: Identity Assurance Levels2 | WhoFederal agencies implementing the guidelines, which must also meet FISMA duties; other organizations may use them voluntarily2 | RequirementChoose an identity proofing level through the Digital Identity Risk Management process2 | LevelIAL1: core attributes validated against authoritative or credible sources; IAL2: more evidence and stricter validation; IAL3: adds an on-site attended session with a trained proofing agent and a biometric2 | DeadlineThe base volume sets no compliance date; published July 2025, superseding SP 800-63-32 |
| NIST SP 800-63-4: Authentication Assurance Levels2 | WhoFederal agencies implementing the guidelines; voluntary for other organizations2 | RequirementChoose an authentication level through the Digital Identity Risk Management process2 | LevelAAL1: single- or multi-factor; AAL2: two distinct factors, with phishing-resistant options offered; AAL3: phishing-resistant public-key authenticator with a non-exportable private key2 | DeadlineThe base volume sets no compliance date2 |
| NIST SP 800-63-4: Federation Assurance Levels2 | WhoFederal agencies implementing the guidelines; voluntary for other organizations2 | RequirementChoose a federation level through the Digital Identity Risk Management process2 | LevelFAL1: protects against forged assertions; FAL2: also against injection attacks; FAL3: protects against identity provider compromise2 | DeadlineThe base volume sets no compliance date2 |
| Login.gov: Authentication only3 | WhoAgency partners whose applications do not need a user's real-world identity3 | RequirementEmail, password and multi-factor authentication; no identity verification4 | LevelAAL1 (any MFA, device remembered up to 30 days) or AAL2 (MFA at every sign-in, optionally phishing-resistant only or government employee ID only), set by the partner5 | DeadlineNot applicable: a service level; partners select it from their own risk assessment3 |
| Login.gov: Basic identity verification3 | WhoAgency partners whose services call for identity verification but not IAL23 | RequirementIdentity verification without facial matching; address can be verified by mail if phone verification fails4 | LevelIAL1 aligned to NIST SP 800-63-43 | DeadlineNot applicable: a service level; partners select it from their own risk assessment3 |
| Login.gov: Enhanced identity verification3 | WhoAgency partners needing greater assurance, for example where users can view or change financial information3 | RequirementAdds facial matching (a selfie in the remote flow); phone verification required, with no address verification by mail4 | LevelIAL2, compliant with NIST SP 800-63-3 and aligned to SP 800-63-43 | DeadlineNot applicable: a service level; partners select it from their own risk assessment3 |
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
Three sources compared on who each part applies to, what it requires, the assurance level involved and any deadline: the M-26-18 memorandum PDF, the NIST SP 800-63-4 base volume PDF, and three articles in Login.gov's partner help center, read through the help center's public article feed because its web pages refused automated access. Every cell was taken from one of these documents, opened on 2026-11-14. Login.gov rows describe its own published service levels, not rules.
Notes
- M-26-18 is dated August 31, 2026; its appendix states each deadline as a period (within 60 days, 240 days, one year, two years) without naming the day it starts.
- Login.gov's identity verification overview describes the authentication-only levels against NIST SP 800-63-3, while its assurance level page refers to SP 800-63-4; the table quotes each page as written.
Sources
- Office of Management and Budget, Executive Office of the President. M-26-18, Scaling Use of Login.gov to Deliver a Universal Sign-on for Public Services. Checked .
- National Institute of Standards and Technology. NIST SP 800-63-4, Digital Identity Guidelines (July 2025). Checked .
- Login.gov, General Services Administration. Determining your assurance level. Checked .
- Login.gov, General Services Administration. Identity verification overview. Checked .
- Login.gov, General Services Administration. Customizing MFA configuration. 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.