NIST Special Publication 800-63, "Digital Identity Guidelines," sets technical requirements for identity proofing, authenticators, authentication protocols and federation for people interacting with US government information systems over a network. The current revision, SP 800-63-4, was published in July 2025. It supersedes SP 800-63-3 — originally published in June 2017, with Update 2 issued 2 March 2020 — which NIST formally withdrew on 1 August 2025. The guidelines do not define identity itself; they define how confident a system can be that a specific digital credential belongs to the person, device or service presenting it, and they split that confidence into three separately-scored dimensions.
Key takeaways
- A system's overall posture is typically expressed as a triple — e.g.
- SP 800-63-4 is a substantive revision, not an editorial update.
- Consumer IoT rules reach the same place from a different direction.
- Synthetic example, for illustration only.
A four-document suite
SP 800-63-4 is the base volume that introduces shared concepts and the assurance-level model; three companion volumes carry the detailed technical requirements for each stage of a digital identity transaction:
| Volume | Covers |
|---|---|
| SP 800-63-4 | Base document — identity model, risk assessment, assurance-level overview |
| SP 800-63A-4 | Identity proofing and enrollment |
| SP 800-63B-4 | "Authentication and Authenticator Management" — authenticators and credential lifecycle, including the three Authenticator Assurance Levels |
| SP 800-63C-4 | Federation and assertions between identity providers and relying parties |
Three assurance-level scales
Rather than a single score, SP 800-63-4 keeps identity proofing, authentication and federation strength on three separate 1–3 scales, so a system can be tuned independently on each axis instead of forcing one blended rating:
| Level | Identity Assurance Level (IAL) | Authenticator Assurance Level (AAL) | Federation Assurance Level (FAL) |
|---|---|---|---|
| 1 | Validates core attributes against authoritative sources; supports "the real-world existence of the claimed identity." | "Basic confidence that the claimant controls an authenticator bound to the subscriber account," single- or multi-factor. | "A basic level of protection for federation transactions," supporting a wide range of use cases. |
| 2 | "Requires collecting additional evidence and a more rigorous process for validating the evidence and verifying the identity." | "High confidence"; proof of possession and control of two distinct authentication factors is required. | "A high level of protection," including defenses against attempts to inject assertions. |
| 3 | Adds a trained representative who interacts directly with the applicant and collects at least one biometric. | "Very high confidence," requiring a public-key cryptographic authenticator that provides phishing resistance. | "Very high confidence that the information communicated in the federation transaction matches what was established by" the identity and credential service providers. |
A system's overall posture is typically expressed as a triple — e.g. IAL2/AAL2/FAL1 — rather than one number, since a service might need strong proof of who someone is at enrollment (IAL2) without requiring federation at all (no FAL applicable).
What changed from SP 800-63-3?
SP 800-63-4 is a substantive revision, not an editorial update. Beyond the three-volume renumbering (each companion document moved from -3 to -4), the base document and its NIST summary describe several structural changes:
- IAL1 repurposed to explicitly address synthetic-identity and compromised-information attacks, rather than only describing a low-rigor proofing tier.
- Phishing resistance emphasized as an explicit authenticator property, with new guidance steering AAL3 implementations toward phishing-resistant authenticators specifically.
- Risk-based rather than compliance-oriented framing — the revision promotes selecting assurance levels and controls based on an organization's own risk analysis instead of treating the levels as a fixed checklist.
- Baseline tailoring mechanisms that let an organization adjust controls within a level based on documented risk decisions.
- Continuous evaluation expectations, including performance metrics for identity programs over time rather than a one-time assessment.
- Preparation for newer credential formats, including mobile driver's licenses and verifiable credentials, which did not exist in meaningful deployment when SP 800-63-3 was written in 2017.
Why this matters beyond federal IT
SP 800-63-4's assurance-level vocabulary (IAL/AAL/FAL) has become a common reference point well beyond the federal systems it formally governs, including for device manufacturers deciding how strongly to authenticate firmware updates, cloud-connected companion apps, or API keys embedded in a product. A device maker evaluating its own authentication design can use the AAL definitions above as an external, numbered yardstick — e.g. "does our default pairing flow meet AAL1, or does it rely on a shared secret with no proof of possession at all" — without needing to adopt the full federal identity-proofing process the proofing volume (SP 800-63A-4) describes.
Which SP 800-63B-4 rules translate directly to a connected device?
SP 800-63B-4 was written for people signing in to government services, but several of its normative requirements map cleanly onto the accounts that ship with a device: the local web admin page, the companion app, the cloud portal and the service technician login. The HTML edition of SP 800-63B-4 states them as SHALL/SHOULD statements:
| SP 800-63B-4 requirement | What it means for a device maker |
|---|---|
| Single-factor passwords SHALL be at least 15 characters; passwords used only inside multi-factor authentication SHALL be at least 8 | A device admin page protected by a password alone needs a 15-character minimum, not the 8 characters many embedded web servers still enforce |
| No composition rules (mixtures of character types) and no forced periodic changes; a change is forced when there is evidence of compromise | Drop "one upper case, one symbol" rules from the setup wizard; add a "change password now" path tied to breach or tamper events |
| Chosen passwords are checked against a blocklist of common, expected or compromised values | Ship a compact blocklist in firmware or check at the cloud portal; reject the product name, model number and serial number |
| Rate limiting when the secret is shorter than 64 bits | Lock-out or back-off on the local login and on any PIN-based pairing flow |
| AAL2 verifiers SHALL offer at least one phishing-resistant option | The cloud portal and companion app should support a passkey or hardware security key, even if passwords remain available |
| AAL3 requires a phishing-resistant authenticator with a non-exportable key; syncable authenticators SHALL NOT be used at AAL3 | Fleet-administration and code-signing consoles are good AAL3 candidates: keep the keys on hardware tokens |
| Reauthentication at AAL2: overall timeout no more than 24 hours, inactivity no more than 1 hour; at AAL3: 12 hours and 15 minutes | Set session lifetimes on the cloud console and the local admin page deliberately instead of keeping sessions alive until reboot |
How does this line up with IoT baselines such as ETSI EN 303 645 and UK PSTI?
Consumer IoT rules reach the same place from a different direction. ETSI EN 303 645 provision 5.1-1 bans universal default passwords: where passwords are used in any state other than factory default, they must be unique per device or defined by the user. The UK Product Security and Telecommunications Infrastructure regulations, Schedule 1 turn the same idea into a legal requirement for consumer connectable products sold in Great Britain.
NIST's own IoT work complements SP 800-63. NISTIR 8259A lists device identification and logical access to interfaces among the core device cybersecurity capabilities, and NISTIR 8259 describes the activities a manufacturer performs before and after sale. A practical split: use NISTIR 8259A and EN 303 645 to decide whether each interface needs authentication, and SP 800-63B-4 to decide how strong that authentication has to be.
Not every device interface involves a person. Device-to-cloud identity (a per-device certificate or key provisioned at manufacture) sits outside SP 800-63, which covers human subjects; treat the guidance as the reference for human logins and use your PKI design for machine identity.
Worked example: assigning assurance levels to a smart thermostat
Synthetic example, for illustration only. The product and decisions are invented.
A maker of a Wi-Fi thermostat lists five interfaces and picks a target level for each, recording the risk reasoning as SP 800-63-4's risk-based approach expects:
Local setup page (first boot)Unique per-device setup code printed on the label, then the owner chooses a password of at least 15 characters checked against a blocklist. Target: AAL1. Companion app for ownersPassword plus a passkey option, sessions reauthenticated at least every 24 hours, 1-hour inactivity timeout for settings changes. Target: AAL2. Installer portal (can change heating schedules for many homes)Mandatory phishing-resistant authenticator. Target: AAL2 with phishing resistance required, not just offered. Fleet console that can push firmwareHardware security keys with non-exportable keys, 12-hour session limit, 15-minute inactivity limit. Target: AAL3. Debug UART on the boardDisabled in production units; not a login at all, so the decision is recorded as "removed", not "assigned a level".
Writing this table down is the main deliverable. It gives reviewers, customers and auditors a single place to see why each interface is protected the way it is.
What are the common pitfalls when device teams borrow SP 800-63?
- Copying the federal level wholesale. IAL and FAL are about proofing real-world identity and federating it; most device makers only need the AAL vocabulary for their own accounts.
- Keeping 8-character minimums for single-factor logins. The -4 revision raised the single-factor minimum to 15 characters.
- Forcing password rotation. SP 800-63B-4 says verifiers SHALL NOT require periodic changes; rotate only on evidence of compromise.
- Treating passkeys as AAL3. Syncable passkeys export their private key to a sync fabric, so they stop at AAL2.
- Forgetting the service and factory accounts. Hidden technician logins and shared factory credentials undo every other decision; EN 303 645 and the PSTI regulations treat universal defaults as non-compliant.
- Ignoring session lifetime. A strong login with a session that never expires is a weak login.
SoftWSP's firmware and device assessments check authenticator design (default credentials, key management, update signing) against external baselines like SP 800-63B-4 rather than against an internal, unstated bar: see device firmware security.
This guide summarises a public NIST publication; it does not constitute legal or compliance advice.
Put this guide to work
Frequently asked questions
What is NIST SP 800-63?
NIST Special Publication 800-63, "Digital Identity Guidelines," sets technical requirements for identity proofing, enrollment, authenticators, authentication protocols, federation and related assertions for people interacting with US government information systems over a network. The current revision, SP 800-63-4, was published in July 2025, superseding SP 800-63-3, which was withdrawn on 1 August 2025.
What is the difference between SP 800-63A, 800-63B and 800-63C?
They are the three companion volumes that make up the suite: SP 800-63A-4 covers identity proofing and enrollment; SP 800-63B-4, titled "Authentication and Authenticator Management," covers authenticators and credential management and defines the three Authenticator Assurance Levels; and SP 800-63C-4 covers federation and assertions between identity providers and relying parties. SP 800-63-4 itself is the base volume that introduces the shared concepts and assurance-level model the other three build on.
What are IAL, AAL and FAL?
The three assurance-level scales SP 800-63-4 defines, each running 1 to 3 with higher numbers meaning stronger assurance. Identity Assurance Level (IAL) describes confidence that a claimed identity is real and tied to the applicant — IAL1 validates core attributes against authoritative sources, IAL2 adds more rigorous evidence collection and validation, and IAL3 adds in-person-equivalent verification by a trained representative plus at least one biometric. Authenticator Assurance Level (AAL) describes confidence that the claimant controls their authenticator — AAL1 is single- or multi-factor, AAL2 requires proof of possession of two distinct factors, and AAL3 requires a public-key cryptographic authenticator that provides phishing resistance. Federation Assurance Level (FAL) describes the strength of protection on a federated assertion passed between an identity provider and a relying party, from FAL1's basic protection up to FAL3's very-high-confidence binding.
Does SP 800-63-4 apply outside the US federal government?
Not as a legal requirement. It is written for "government information systems," and NIST's revision history confirms SP 800-63-3 (originally published June 2017, last updated 2 March 2020) was formally withdrawn and superseded by SP 800-63-4 only on 1 August 2025. Private-sector identity programs, including device and service authentication for IoT fleets, commonly adopt the IAL/AAL/FAL vocabulary and specific control requirements voluntarily as a de facto baseline, but nothing in the document itself extends it as a binding standard beyond federal systems.
Sources
- NIST: SP 800-63-4, Digital Identity Guidelines (final, July 2025) — resource page
- NIST: SP 800-63-4, Digital Identity Guidelines (full text PDF)
- NIST: SP 800-63B-4, Authentication and Authenticator Management (final, July 2025) — resource page
- NIST: SP 800-63-3 Update 2 (withdrawn 1 August 2025) — resource page
- NIST: SP 800-63B-4 HTML edition (password length, rate limiting, AAL2/AAL3 reauthentication, syncable authenticators)
- ETSI EN 303 645 V3.1.3: Cyber Security for Consumer Internet of Things — Baseline Requirements
- UK legislation: Product Security and Telecommunications Infrastructure (Security Requirements for Relevant Connectable Products) Regulations 2023, Schedule 1
- NIST: NISTIR 8259A, IoT Device Cybersecurity Capability Core Baseline
- NIST: NISTIR 8259, Foundational Cybersecurity Activities for IoT Device Manufacturers
About this guide
SoftWSP Firmware Security Desk
Covers the Firmware vulnerabilities & fixes cluster: 129 guides.

In this cluster
Questions about this page?
