Join our Newsletter — 33% off our NHI Course
Home› FAQ› Architecture & Implementation› How do passkeys fit into step-up authentication and…
Architecture & Implementation

How do passkeys fit into step-up authentication and zero trust?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 31, 2026 Domain: Architecture & Implementation

Passkeys fit best when step-up is driven by transaction risk, not by a one-size-fits-all login rule. In a zero-trust model, the authenticator should be selected and challenged according to context, so stronger proof is used where the access decision warrants it.

How passkeys support step-up without turning login into a blanket hurdle

Passkeys work well when step-up is triggered by risk, sensitivity, or transaction context rather than every sign-in. That lets you keep low-friction access for ordinary sessions and reserve stronger proof for high-impact actions, unusual devices, or suspicious conditions. In practice, passkeys become one authenticator in a broader authentication policy, not the policy itself.

The main design question is what you are stepping up for. A passkey can satisfy a strong authentication requirement, but the decision to prompt for it should be driven by the business action, the current assurance level, and the trust state of the session. That is what makes passkeys fit naturally into adaptive authentication rather than static login rules.

For teams standardising this pattern, the important move is to treat passkeys as the preferred phishing-resistant authenticator where step-up is justified, not as a universal replacement for every additional control. A well-designed flow can still use other signals and authenticators where recovery, device loss, or cross-channel verification need a fallback. Passwordless and Passkeys Guide explains the rollout and recovery trade-offs in more detail.

Why zero trust changes the step-up decision

Zero trust shifts the question from “has the user already logged in?” to “should this request be trusted right now?” That matters because step-up is strongest when it is tied to the current request context, the sensitivity of the resource, and the amount of privilege being exercised. In that model, passkeys are useful because they can raise assurance at the point of risk without assuming the initial session stays trustworthy.

A zero-trust implementation should not rely on one durable sign-in event for all future actions. It should re-evaluate access when context changes, including device posture, network conditions, session freshness, and whether the user is attempting a privileged or irreversible action. Zero Trust Identity Guide is useful here because it frames identity as a continuous policy input rather than a one-time gate.

That is also why passkeys and zero trust complement each other well. Passkeys improve the quality of the authentication event, while zero trust determines when that event should happen and how much confidence it must provide. If the action is low risk, keep the interaction light. If the action changes entitlements, exposes data, or moves value, step up to stronger proof.

Where passkeys fit best in a risk-based authentication flow

The cleanest use of passkeys is at the point where risk-based authentication decides that the current session needs stronger assurance. That could be a password reset, a high-value transfer, a change to recovery settings, or access from an unfamiliar environment. The passkey then becomes the preferred proofing step because it is resistant to phishing and replay in a way passwords and one-time codes are not.

Passkeys also fit well when you want to reduce the dependence on vulnerable fallback paths. If a workflow still allows weaker recovery methods, those paths can become the real weak link even if the primary sign-in is strong. Risk-Based and Adaptive Authentication Guide shows how to use signals and thresholds so step-up is selective rather than constant.

In higher-risk consumer and enterprise flows, passkeys can also support transaction authorisation rather than only session entry. That distinction matters because the real security objective is often not “did the user authenticate?” but “did the right principal approve this specific action?” Transaction Authorisation Guide covers that boundary between stronger login and stronger approval.

Risk and Threat Considerations

Step-up that is tied to the wrong trigger can create both security gaps and user fatigue. If you challenge too often, users learn to expect prompts and may rush through them. If you challenge too rarely, an attacker who steals a session or abuses a weak recovery path may never face the stronger proof you intended to require.

Failure mechanism: The control fails when policy treats the initial login as sufficient evidence for later privileged actions, or when weak recovery and session reuse bypass the intended step-up point. That leaves the strongest authenticator unused where it matters most.

Impact: Attackers can convert a stolen session, an abused help-desk flow, or a low-friction login into access to sensitive actions without ever meeting the higher-assurance standard. The result is not just account compromise, but compromise of the decisions that follow the sign-in.

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, NIST Zero Trust (SP 800-207) and OWASP ASVS set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-63Digital Identity GuidelinesStep-up authentication and passkeys hinge on authenticator assurance and phishing-resistant auth.
Recommendation — Use assurance levels to require stronger authenticators only when the request risk warrants them.
NIST Zero Trust (SP 800-207)Zero Trust ArchitectureZero trust determines when to re-evaluate trust and trigger step-up based on context.
Recommendation — Continuously evaluate each request and enforce stronger authentication when context changes.
OWASP ASVSV6 — AuthenticationPasskeys are an authentication control choice, especially for phishing-resistant login.
V7 — Session ManagementStep-up depends on session freshness and when a session must be revalidated.
Recommendation — Verify authentication requirements so the highest-risk flows use phishing-resistant methods. Revalidate sessions for sensitive actions instead of trusting a long-lived login state.

Practitioner Guidance

What to verify: Confirm that your step-up policy is attached to specific actions, not just to “suspicious login” events. The best test is whether a high-risk action will still force stronger proof even if the current session was recently established.

Decision rule: If the action changes money, permissions, recovery settings, or protected data, require the strongest available phishing-resistant authenticator and recheck freshness. If the action is routine and reversible, avoid forcing the same friction into every session.

What good looks like: Users sign in with passkeys for normal access, then encounter step-up only when the request context crosses a risk threshold. Recovery paths are still available, but they are clearly more controlled than the main authentication path.

Practitioner takeaway: Passkeys are most valuable in zero trust when they are the preferred stronger proof for risky actions, not a blanket replacement for all authentication challenges. The security win comes from pairing a strong authenticator with precise policy about when to ask for it.

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 October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org