# Why SMS MFA Is Being Replaced—and What to Use Instead

> SMS-based MFA doesn't fail because of a flaw in the code itself. It fails because it depends on the telephone network's identity verification, which was never designed to be a security control.

- URL: https://firewallsync.com/posts/why-sms-mfa-is-being-replaced-and-what-to-use-instead/
- Site: FirewallSync (https://firewallsync.com/)
- Topic: Identity & Access
- Tags: authentication, iam
- Published: 2026-11-20
- Author: FirewallSync Editorial


SMS-based one-time codes don't fail because of a flaw in the code itself — a six-digit number sent over SMS is cryptographically no different from one generated by an authenticator app. They fail because the delivery channel depends entirely on the security of the telephone network and carrier identity-verification processes, neither of which were designed with this kind of security use case in mind, and both of which have well-documented, actively exploited weaknesses.

## SIM swapping: attacking the delivery channel, not the code

A SIM swap attack doesn't try to intercept or guess the code at all — it targets the carrier's own account-verification process, social-engineering or bribing a carrier representative into transferring a victim's phone number to a SIM card the attacker controls. Once that transfer succeeds, every SMS-based code meant for the victim goes straight to the attacker instead, with the victim's actual security practices being entirely irrelevant to the outcome. This has become an industrialized service on criminal forums, with SIM swaps available for purchase against specific carriers at a set price, rather than requiring a skilled individual attacker for each target.

## SS7 interception: a deeper protocol-level weakness

Beyond SIM swapping, the SS7 signaling protocol underlying much of global telecom infrastructure has known weaknesses that allow message interception with the right network-level access, without needing to compromise the victim's SIM at all. This has been demonstrated and exploited against real banking customers, and it's a weakness in the telecom infrastructure itself, not something any individual organization sending SMS codes can mitigate on their own end.

## Real-time phishing relay defeats SMS the same way it defeats any OTP

Independent of carrier-level attacks, an adversary-in-the-middle phishing kit can simply ask the victim to type their SMS code into a fake login page and relay it to the real service in real time — this works against any one-time code delivered through any channel, SMS included, because the code itself carries no information about which site it's legitimately being used on. This is the same structural weakness that affects authenticator-app codes and any other OTP-based MFA that isn't cryptographically bound to the origin — SMS just adds the carrier-level attack surface on top of this shared weakness.

## What regulators and standards bodies actually say

NIST classified SMS as a "restricted" authenticator in its digital identity guidelines as early as 2017 — a designation requiring organizations to specifically assess and accept the risk and maintain a migration plan away from it, short of an outright ban. Later revisions to NIST's guidance have continued to discourage it further for higher-assurance use cases, and a growing number of regulators internationally — in banking and financial services particularly — have moved to require phishing-resistant authentication for higher-risk transactions specifically, under which SMS OTP does not qualify. The direction of travel across standards bodies and regulators is consistent even where the specific timelines and requirements differ by jurisdiction and industry.

## What to actually migrate to

**Passkeys (FIDO2/WebAuthn)** are the strongest realistic default for most organizations, providing genuine phishing resistance through origin-bound cryptographic challenges rather than a transmittable code — covered in more depth in comparing passkeys against dedicated hardware keys.

**TOTP authenticator apps** (Google Authenticator, Authy, or similar) remain an acceptable intermediate step where passkeys aren't yet supported by a given system — they remove the carrier-dependency and SIM-swap risk entirely, since the code is generated locally on the device from a shared secret rather than transmitted over the telecom network, though they remain vulnerable to real-time phishing relay the same as SMS is, just without the additional carrier-level attack surface.

**Hardware security keys** for the highest-sensitivity accounts, for the reasons covered in the passkeys comparison — key material that never leaves a dedicated physical device, for the specific set of accounts where that additional assurance is worth the operational overhead.

## Migration practicalities

**Prioritize by account sensitivity, not by ease of migration.** Administrative and high-privilege accounts should move off SMS first, even if a broader rollout across the full user base takes longer — the accounts where a successful SIM-swap or interception attack would matter most shouldn't wait for a company-wide rollout to be scheduled.

**Don't leave SMS as a silent fallback option after migrating.** A user who has enrolled a passkey but still has SMS configured as a recovery or fallback method hasn't actually closed the gap — an attacker will simply target whichever method is weakest, and a strong primary factor with a weak fallback is still exploitable through the fallback path.

**Expect a longer tail than the initial rollout suggests.** Some legacy systems, some third-party integrations, and some lower-priority internal tools may not support modern authentication methods at all, meaning a full SMS-elimination effort often takes longer than the headline migration to passkeys for primary systems — track this explicitly rather than considering the migration complete once the main identity provider is updated.

The reason to move off SMS isn't that it provides zero protection — it's meaningfully better than no second factor at all. It's that meaningfully stronger, similarly convenient alternatives now exist, and the specific attack patterns SMS remains vulnerable to (SIM swapping, SS7 interception) are active, documented, and increasingly accessible to attackers without specialized skill.

Image credit: Photo by [Franck](https://unsplash.com/photos/DoWZMPZ-M9s) on Unsplash
