VulCode
Two-step sign-in in a business app: authenticator codes and backup codes
Technology

Two-step sign-in in a business app: authenticator codes and backup codes

An authenticator app code, an SMS and single-use recovery codes: how each method works and what the app has to do when a phone goes missing

DualFroz - VulCode CEODualFroz - VulCode CEO·17 November 2026·1 min read

An authenticator app code is a TOTP: the phone derives it from a secret saved at setup and the current time, by default in 30-second steps (RFC 6238), and it has at least 6 digits. No signal is needed. An SMS code travels through the carrier's network, which is why NIST SP 800-63B lists SMS and voice calls as its only restricted authenticator.

Three ways to take the second step

MethodHow it worksWhat to keep in mind
App code (TOTP)a new code every 30 seconds, made on the phonea lost phone means using a backup code
SMSa code sent through the carriera restricted method under NIST
Backup codesingle-use, kept away from the phonestops working once used

Backup codes

Under NIST guidance a backup code works only once, is stored only as a hash, allows a limited number of attempts, and issuing a new recovery code notifies the account owner. An account in the Flaem client panel has an app code at every password sign-in, passkeys, single-use recovery codes, active sessions with sign-out everywhere and a sign-in history.

In the panels we build to order, two-factor sign-in takes a TOTP app code or an SMS, every login lands in an audit log with a timestamp, IP address and user ID, and an IP that keeps entering wrong passwords gets blocked. A suspicious session token can be revoked at once. With Google or Microsoft sign-in, the identity provider handles the password and two-step verification.

Sign-in security in a custom panel is covered on our panels and dashboards page.