Join our Newsletter — 33% off our NHI Course
Home› FAQ› Authentication, Authorisation & Trust› How should teams decide between TOTP and HOTP…
Authentication, Authorisation & Trust

How should teams decide between TOTP and HOTP for step-up authentication in higher-risk applications?

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

Use TOTP when you want the shorter attack window and stronger day-to-day security. It expires quickly, so stolen codes are less useful. Use HOTP when time sync is unreliable or user flow demands longer code validity. In practice, the decision should weigh security requirements, clock synchronization, and usability, because both methods still depend on shared secrets and careful implementation.

How to choose the right OTP factor for step-up use

The right choice is usually about how much freshness you need and how reliably the user device can stay in sync. TOTP is the better default when the goal is to narrow the reuse window for a captured code. HOTP becomes more attractive when a user journey is sensitive to clock drift, offline use, or delayed verification.

That trade-off matters most in step-up flows because the factor is being used to protect a higher-value action, not just the initial sign-in. In that setting, the method should fit the risk of the transaction, the tolerance for replay, and the operational reality of the deployment.

Where TOTP is the stronger default

TOTP fits higher-risk applications when you want codes that lose value quickly. A short-lived code reduces the usefulness of screenshots, relayed prompts, delayed copy-and-paste attacks, and many forms of accidental code reuse. It is also easier to reason about when you need a clear expiry boundary for a step-up challenge.

That does not make TOTP a complete control. It still relies on a shared secret, secure enrollment, and correct clock handling on both sides. If the implementation accepts wide clock drift or weak secret handling, the practical advantage drops fast. For teams standardising their MFA posture, the MFA Guide is the clearest place to anchor the broader factor decision.

When HOTP is the better fit

HOTP is worth considering when time synchronisation is unreliable, or when the workflow needs a code that remains valid until it is consumed. That can help in environments with poor device clocks, interrupted connectivity, or support-heavy flows where users may take longer to complete the challenge.

The trade-off is operational rather than theoretical. Because HOTP does not expire on a timer, the security of the flow depends more heavily on counter management, replay handling, and how aggressively the server advances or resynchronises state. If the counter logic is loose, the attack window can become wider than teams expect.

Step-up design should be driven by attack window, not habit

For higher-risk applications, the best decision is often to treat OTP choice as part of the step-up policy, not as a standalone factor preference. If the action is especially sensitive, the challenge should be time-bounded, strongly bound to the user session, and resistant to replay or delayed use. That is why TOTP is often the more defensible default for step-up.

If the user journey cannot reliably support time-based validation, HOTP can be acceptable, but only when the team has explicit controls for counter drift, resynchronisation, and monitoring. The practical question is not which code type is older or simpler, but which one gives the smaller real-world attack window for the specific transaction.

Risk and Threat Considerations

OTP step-up controls are exposed to replay, phishing relay, code theft, and implementation mistakes that quietly widen the usable window. In higher-risk applications, the main threat is not the code format itself, but the way timing, state, and shared secrets are handled around it.

Failure mechanism: TOTP weakens if the system tolerates large clock drift, while HOTP weakens if counters fall out of sync or replay checks are lax. In both cases, a stolen or intercepted code can remain usable longer than the design intended.

Impact: The attacker gets a broader opportunity to complete step-up and progress into a sensitive transaction, especially if the application does not bind the challenge tightly to the session, action, or recent authentication context.

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 NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-63Digital Identity GuidelinesStep-up authentication and authenticator assurance depend on NIST identity guidance.
Recommendation — Use authenticator assurance and reauthentication guidance to match factor strength to step-up risk.
OWASP ASVSV6 — AuthenticationTOTP and HOTP are authentication mechanisms whose handling affects step-up security.
Recommendation — Verify OTP enrollment, verification, expiry, and replay handling under V6 authentication requirements.
NIST SP 800-53 Rev 5IA-2 — Identification and Authentication (Organizational Users)Step-up OTPs are part of user authentication control for privileged actions.
Recommendation — Enforce strong user authentication before sensitive actions and validate factor freshness.

Practitioner Guidance

What to prioritise: For higher-risk step-up flows, choose the factor that best reduces the usable lifetime of a stolen code while still fitting the user environment. If you can support accurate clocks, TOTP is usually the safer operational default.

What to verify: Check how much clock drift the verifier accepts, how counter resynchronisation works for HOTP, and whether the code is tied to a specific session or action. A factor that is technically correct but loosely validated is not fit for a sensitive step-up boundary.

Practitioner takeaway: The best choice is the one that gives you the smallest exploitable window with the least operational fragility, not the one that is easiest to explain in the abstract.

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