They should test whether the recovery flow can authenticate a user with no prior registration at all. If the product still depends on a pre-enrolled passkey, authenticator, or device, those users will fall back to the help desk. The control is only useful when it covers the unenrolled population, not just the easy majority.
What a recovery flow must do for unenrolled users
The question is not whether a verification app is useful for the enrolled majority, but whether the recovery path still works when there is no prior enrollment at all. A good design distinguishes between step-up for existing users and first-time recovery for the unenrolled population, then checks which proofing factors are still available without assuming an app, passkey, or remembered device.
That distinction matters because a recovery flow that silently assumes prior setup will look healthy in testing and still fail the users who need help most. If the only working route is a help-desk override, the product has shifted the security decision from a controlled flow into an identity exception process.
Where recovery fails when the app was never enrolled
Unenrolled users are most likely to fail at the binding point, where the system expects a pre-existing authenticator, device trust, or registration artifact. In practice, that means the product may ask for a code, a device approval, or a passkey that the user never had, then route them into manual support instead of a self-service recovery path.
That is a design flaw, not just a usability issue. The recovery journey should be tested against the actual state model, including users with no app, no backup factor, no trusted device, and no prior proofing record beyond whatever the business can legitimately rely on. Securing Your Apple ID and Google Account Guide is a useful comparison point because consumer recovery flows often expose the same problem: the “forgotten account” path only works if the fallback factors were established earlier.
A practical test is to start with a clean account, no enrolled app, and no remembered device, then walk the exact recovery journey end to end. If the process cannot reach a safe recovery state without ad hoc support, the control is not covering the population it claims to protect.
Designing fallback paths without turning the help desk into the control
Security teams should treat unenrolled recovery as a bounded design problem, not a special case to be handled informally by support staff. The fallback path needs explicit rules for what evidence is acceptable, what gets rejected, what triggers additional review, and when the user must be stopped and re-proofed rather than merely reset.
OWASP ASVS Guide and OWASP ASVS both reinforce the same practical point: recovery, authentication, and session handling are part of the security boundary, so the fallback route must be verified as rigorously as the primary login path. If recovery is looser than sign-in, attackers will target recovery first.
The safest operating model is one where the help desk can assist, but cannot independently decide identity restoration for high-risk cases without controls, logs, and escalation thresholds. That keeps recovery usable for legitimate users while reducing the chance that social engineering or weak exception handling becomes the easiest entry point.
How to know the process is actually covering unenrolled users
Teams should measure recovery success by state, not by aggregate completion rate. A flow that works for already-enrolled users can still be broken for users who arrive with no verification app, so testing must separate enrolled, partially enrolled, and never-enrolled populations and compare their outcomes.
Web Application Security Testing Guide is relevant here because recovery paths need the same kind of negative testing as other business-critical flows: missing factors, invalid assumptions, locked-out states, and alternate branches that only appear when the user has no prior setup. The important signal is whether the user can complete recovery without forcing a manual exception.
What good looks like is simple: the unenrolled user can complete a documented path, the system records which evidence was used, and the resulting account state is consistent with policy. If the only observable outcome is “call support,” then the control exists on paper but not in practice.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP ASVS, NIST SP 800-63, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP ASVS | V6 — Authentication | Recovery flows must authenticate users safely when primary factors are missing. |
| Recommendation — Verify recovery paths for unenrolled users with the same rigor as primary authentication. | ||
| NIST SP 800-63 | Digital Identity Guidelines | Covers identity proofing and recovery assurance when users lack prior authenticators. |
| Recommendation — Apply proofing and recovery assurance rules to unenrolled account recovery. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Recovery often issues, resets, or replaces authenticators after loss or non-enrollment. |
| Recommendation — Control issuance and replacement of authenticators through managed recovery procedures. | ||
| CIS Controls v8 | 5 — Account Management | Account recovery depends on verifying and restoring legitimate access for the right user. |
| Recommendation — Review account recovery and reset processes for gaps that bypass intended access controls. | ||
Practitioner Guidance
What to verify: Test the exact unenrolled journey, not the happy path, and make sure the recovery mechanism works when no prior app enrollment, trusted device, or backup factor exists.
Decision rule: If recovery depends on a pre-enrolled factor to authenticate the user, treat that path as incomplete and add a separate first-time recovery route before relying on it operationally.
Common mistake: Measuring success by how well enrolled users recover while ignoring the users who fall through to manual support because they never set up the app in the first place.
Practitioner takeaway: Recovery is only a security control if it handles the identity state you actually have, including the users who never enrolled anything at all.
Related resources from NHI Mgmt Group
- How should security teams handle TOTP authentication when users want one app for both password management and verification codes?
- How should organisations handle identity verification when deepfakes can mimic real users?
- How should security teams handle SaaS offboarding when users also use AI tools?
- How should security teams handle identity verification when background checks are automated with AI?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org