Comparing MFA methods for everyday work
Compare text codes, authenticator apps and phishing-resistant sign-in methods with the devices, recovery paths and services your staff use.

Multi-factor authentication adds checks beyond a password, but the methods don’t all protect you equally. Compare how each method handles phishing, everyday access and recovery for the service you’re securing.
Administrator accounts may need a stronger method than an older application can support. Write down where you’ve accepted a weaker method, and why.
Understand text-message codes
SMS codes are familiar and may be available where other methods aren’t. They depend on access to the phone number and the service’s delivery system.
A code can be entered into a fraudulent site or disclosed to a caller. A number takeover can also redirect messages. Don’t treat a text code as phishing-resistant authentication.
If SMS is the only supported additional check, use it, note the limitation and plan to move to a stronger method once the service supports one.
Separate app codes from app prompts
An authenticator can generate a time-based code, or a service can send a request for approval. These are different interactions.
Generated codes don’t require SMS delivery, but a phishing site can still ask you to disclose one. Repeated approval prompts can pressure someone to approve a sign-in they didn’t start.
Number matching and additional prompt context can reduce accidental approvals. They don’t turn ordinary push authentication into a phishing-resistant method. Staff need a clear way to report unexpected requests.
Check the security-key or passkey protocol
A FIDO-based security key or supported passkey can bind authentication to the legitimate service, making phishing relays harder to use. Don’t go by the label on the device: confirm the protocol and how the service uses it.
The Cyber Centre’s phishing-resistant MFA guidance explains the distinction and the attack paths involved.
Authentication still doesn’t protect every already-signed-in session or a compromised endpoint. Keep device and session controls in the plan.
Test convenience with your own staff
Include people who travel, use shared workstations, need accessibility accommodations or can’t use a personal phone for work. Test browser and mobile compatibility before standardizing.
Compare sign-in time, failure handling and support demand. Don’t assume everyone finds text messages easiest or that everyone can carry and connect the same hardware token.
Make recovery strong enough
Register supported backup methods and document lost-device recovery. Store recovery codes where only the account owner can reach them, and verify identity before resetting enrolment.
Check whether an attacker can bypass the stronger primary method through a weak fallback. A phone-number recovery option may undermine a rollout intended to avoid dependence on phone numbers.
Record the chosen method, remaining exceptions and a review date. Use the passkey migration guide for a rollout plan after the comparison is complete.


