Two-factor authentication
In Arabic التحقق بخطوتين
Two-factor authentication (2FA) is a sign-in method that requires a second proof of identity, such as a one-time code from a phone, in addition to the password.
In plain words
Passwords leak, get reused and get guessed. With a second factor, a stolen password alone is not enough: the attacker also needs the user’s phone. That makes it one of the simplest protections an ERP holding customer and financial data can switch on.
The usual second factor is an authenticator app that shows a six-digit code changing every 30 seconds, entered after the password. Backup codes kept somewhere safe let the user in if the phone is lost, and an administrator can reset it.
The common mistake is making 2FA optional and never checking who uses it. The accounts with the most access, administrators and finance staff, are often the ones that skip it. Require it for them first.
- Password
- Correct
- Code shown on the phone
- 481 927
- Code entered
- 481 927
- Entered within
- 30 seconds
- Sign-in
- Allowed
In Axon Suite
How Axon Suite handles it
Axon Suite can require office users to enter an authenticator-app code after the password, with ten backup codes for a lost phone and a reset by the admin. Field reps’ devices are controlled from the office instead.
Feature
Sign-in that resists guessing
Repeated wrong passwords lock the account. A reused session token ends the session outright. Office users can be asked for an authenticator code, and the office can sign a rep’s phone out remotely.
Open: Sign-in that resists guessing