Join our Newsletter — 33% off our NHI Course
Home› FAQ› Authentication, Authorisation & Trust› What is the difference between passkey login and…
Authentication, Authorisation & Trust

What is the difference between passkey login and OTP-based step-up for account actions?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 2, 2026 Domain: Authentication, Authorisation & Trust

Passkey login proves the user has the enrolled device and can complete a phishing-resistant sign-in. OTP-based step-up adds a separate verification event for sensitive actions such as registering or modifying passkeys. In practice, passkeys can secure the primary login path, while OTP can serve as an additional control for higher-risk account management steps.

How passkey login differs from OTP step-up

Passkey login and OTP-based step-up solve different problems in the account journey. Passkey login is the primary sign-in method, it is designed to be phishing-resistant and bound to the enrolled device or authenticator. OTP step-up is an additional verification event used only when the action is higher risk, such as enrolling a new passkey, changing recovery settings, or approving account management changes.

The practical difference is that passkeys answer, “Is this the legitimate user signing in?” while OTP step-up answers, “Should this sensitive action be allowed right now?” That means passkeys can reduce friction at login, while OTP can still be used as a separate control for specific account actions when the organisation wants a second check before changing the account itself.

Passkeys also change the attack surface. Because the login ceremony relies on the authenticator and origin-bound cryptography, it resists common phishing and replay patterns better than shared secrets or one-time codes. OTP remains useful as a separate signal for actions that deserve extra scrutiny, but it does not provide the same phishing resistance and can still be exposed to relay, social engineering, or code theft if used as the only secondary control.

Where each control fits in the account lifecycle

Think of passkey login as the control for routine access and OTP step-up as the control for exceptional account management. A user may authenticate with a passkey every day, yet still be prompted for OTP when they try to add a new authenticator, modify recovery information, or perform another action that could widen access or reduce account assurance. That separation helps preserve a strong login path without making every privileged account action depend on the same factor.

This distinction matters because account actions are not all equal. Logging in establishes an authenticated session, but changing the account’s authentication methods can affect future access, recovery, and takeover resistance. A separate step-up event gives the service a chance to re-check intent before allowing a durable security change, especially when the new state could make future sign-ins easier for an attacker.

Good designs keep the two flows deliberately different. The login flow should be as simple and phishing-resistant as possible, while the step-up flow should be reserved for sensitive changes and should fail closed if the user cannot satisfy the extra check. That way, a strong passkey experience does not remove the opportunity to challenge risky administrative or recovery actions.

Why the distinction matters for recovery, enrollment, and abuse resistance

The most sensitive moments are usually not ordinary sign-in, but enrollment, recovery, and account modification. If an attacker can enroll a new passkey, change a recovery factor, or weaken the existing assurance model, they may be able to turn a one-time foothold into durable access. OTP step-up is often used here because it forces an additional proof event before the account state changes.

For practitioners, the key judgment is whether the step-up factor is truly independent from the primary login method. If the same device, app, or recovery channel can satisfy both with little additional resistance, the step-up may add only modest security value. Where the action can meaningfully change future access, the organisation should treat step-up as a control boundary, not just a user experience prompt.

For a broader view of phishing-resistant sign-in, recovery trade-offs, and roll-out decisions, see Passwordless and Passkeys Guide and Authentication Guide. For step-up design patterns and transaction-sensitive verification, OAuth Step-Up Authentication Challenge Guide and OTP security are useful complements.

Risk and Threat Considerations

The main risk is assuming that any second factor is equivalent. OTP can be effective as an added hurdle, but it is weaker when the attacker can intercept, relay, socially engineer, or reuse the code quickly enough to complete the action. If the same account action that protects the account can also be used to weaken future protections, a compromised session or exposed code can create a durable takeover path.

Failure mechanism: An attacker gains access to the current session, tricks the user into sharing a code, or abuses a recovery path, then uses the step-up event to authorize a change that improves long-term persistence, such as enrolling a new authenticator or resetting the recovery method.

Impact: The account may remain compromised even after the original login session ends, because the attacker has altered the trust and recovery settings that govern future access.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-63, OWASP ASVS and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-63Digital Identity GuidelinesDefines authenticator assurance and phishing-resistant authentication for passkey login.
Recommendation — Use phishing-resistant authenticators for primary sign-in and require higher assurance for sensitive account actions.
OWASP ASVSV6 — AuthenticationPasskeys and OTP step-up are authentication mechanisms with different assurance and phishing resistance properties.
V7 — Session ManagementAccount-action step-up depends on session freshness and reauthentication before sensitive changes.
Recommendation — Verify the login method and step-up method each meet the required authentication assurance. Require fresh reauthentication before allowing sensitive account modifications.
CIS Controls v85 — Account ManagementThe distinction affects how accounts are authenticated, modified and recovered across their lifecycle.
Recommendation — Separate routine access from higher-risk account changes and review recovery paths regularly.

Practitioner Guidance

What to verify: Confirm that the passkey login flow and the account-action step-up flow are actually distinct, with separate policy decisions and separate failure handling. If the same ceremony is reused for both, the control boundary is too thin to protect sensitive changes.

Decision rule: Use passkeys for the primary login path wherever possible, then require step-up only for actions that can change account assurance, recovery, or privilege state. If the action can alter who may sign in next week, treat it as a higher-risk event than ordinary authentication.

Common mistake: Treating OTP as a universal “extra security” label instead of checking whether it meaningfully raises the bar for the exact action being protected. A step-up factor that is easy to relay or socially engineer may still be useful, but it should not be mistaken for phishing resistance.

Practitioner takeaway: The security value comes from separating routine sign-in from high-risk account changes, not from stacking factors indiscriminately.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org