Direct sources. Clear status. Practical public information.
Reviewed November 4, 2026 · defensive identity security · NIST SP 800-63B-4.
Authorization boundary
Use this drill only on accounts and identity systems you own or are explicitly authorized to administer. Do not test another person’s account, trigger recovery against a third party, request or expose recovery codes, bypass identity proofing, impersonate a user, or place secrets in public AI tools, screenshots, or reports.
What NIST calls account recovery
NIST SP 800-63B-4 describes account recovery as regaining control after losing the authenticators needed to sign in. It identifies recovery approaches such as saved or issued recovery codes, recovery contacts, and repeated identity proofing. NIST also distinguishes account recovery from binding a new authenticator when a subscriber can still authenticate, and says recovery events cause notifications intended to help detect fraudulent use.
The five-stage fire drill
- Owner: identify the accountable owner, authorized administrator, covered account, service criticality, and human approval. Never record the credential itself.
- Route: navigate from the provider’s known official domain or signed-in security settings. Record only the verified URL pattern and provider documentation—not tokens, codes, email contents, or private configuration.
- Test: use a provider-supported test or a low-risk authorized account. Confirm the expected notification path without locking out production users or changing a consequential setting without approval.
- Repair: update stale recovery contacts, remove unauthorized recovery routes, store recovery codes securely, and document the responsible human decision.
- Retest: confirm the official route, expected notification, authorized recovery ownership, and normal service. Preserve a dated non-secret pass/fail receipt.
A safe evidence log
| Keep | Do not keep in public copy or public AI |
|---|---|
| Account alias, owner role, provider, test date, authorized scope, expected notification type, result, repair owner, retest date | Passwords, one-time codes, recovery codes, full email/phone, secret questions, session cookies, tokens, private logs, screenshots with personal data, exploitable configuration |
Human stop points
Stop before a production lockout, identity-proofing change, recovery-contact removal, administrator change, legal hold, child/student account action, or any step affecting another person. Escalate to the responsible owner, provider, parent/teacher, security lead, or qualified professional.
Official sources
- NIST SP 800-63B-4 — Authentication and Authenticator Management
- NIST — Authenticator Event Management
Sources reviewed November 4, 2026. Provider features and contractual duties vary; verify the current official route and your authorization.
Public-information notice: This Pulse is a dated, source-linked research summary for general educational use. It reports what the cited sources state or what the identified public record shows as of the date reviewed. Citation does not mean endorsement, partnership, certification, or independent confirmation of every third-party assertion. This is not individualized legal, medical, tax, accounting, investment, insurance, cybersecurity, licensing, regulatory, procurement, employment, real-estate, or other professional advice. Rules, facts, availability, and eligibility can change. Verify the controlling source, jurisdiction, effective date, and your own facts, and consult the responsible agency or a qualified professional before a consequential decision. External links are provided for attribution and may change. Use this information and any reader-controlled checklist at your own discretion and risk.
