---
title: "Legacy Factors Fail in CIAM. Passkeys Are the Answer"
description: "Discover why legacy MFA fails against automated attacks and how phishing-resistant authentication and passkeys protect your modern CIAM architecture."
authors:
  - name: "Gareth Davies"
    url: "https://auth0.com/blog/authors/gareth-davies/"
  - name: "Chitra Dharmarajan"
    url: "https://auth0.com/blog/authors/chitra-dharmarajan/"
  - name: "Mathew Woodyard"
    url: "https://auth0.com/blog/authors/mathew-woodyard/"
date: "Nov 18, 2026"
category: "Identity & Security"
tags: ["passkeys", "security", "authentication"]
url: "https://auth0.com/blog/legacy-factors-fail-in-ciam-passkeys-are-the-answer/"
---

# Legacy Factors Fail in CIAM. Passkeys Are the Answer

<style>
    
  /* Increases spacing between bullet points */   
    li {padding-bottom: .7em; }
/* Style a table with grey background. Add borders, compact width, and reduce font size. */
table {
  width: 100%;
  max-width: 1100px; /* Adjust this value (e.g., 350px, 400px) to make the table smaller */
  margin: 2.4rem auto !important; /* Change '0' to 'auto' if you want it centered */
  border-collapse: collapse;
  font-size: .7em;
  table-layout: fixed; /* Forces the browser to obey the size constraints */
}

table, td, th {
  border: 1px solid;
}

table th {
  line-height: normal;
  padding: .8em;
}

td {
  padding: .8em;
  line-height: normal;
}
</style>
Your login page guards what your customers value most, like loyalty points and gift card balances. According to the [National Retail Federation’s 2026 analysis](https://nrf.com/blog/2026-top-100-retailers), the holdings of the top ten retailers alone [total nearly $10 billion](https://nrf.com/research-insights/top-retailers/top-100-retailers/top-100-retailers-2026-list). Using passwords as a sole factor is insufficient for the modern Customer Identity and Access Management (CIAM) platform. Attackers test reused, stolen credentials against sign-in flows constantly, automatically, and at scale. Introducing factors like SMS, email, and Time-based One-Time Passwords (TOTPs) improves your users’ security posture, but attackers employ commodity tooling that has multi-factor authentication (MFA) circumvention built in. Defending against today’s threat landscape now requires a shift to phishing-resistant authentication.

## Credential Stuffing Tools Are Cheap and Available

Running credential stuffing attacks takes little skill or money. As Okta Threat Intelligence [recently showed](https://www.okta.com/blog/threat-intelligence/credential_stuffing_attacks_poised_to_accelerate_with_ai/), underground markets sell everything an attacker needs off the shelf, proving a cheap, effective and frequently successful way to take over accounts.

Configuration files (configs) bring this together as code, directing attacker automation to specific sign-in flows specifying which endpoints to call, in what order, and how to recognize a successful login. Just how cheap are they? Our [threat analysis](https://www.okta.com/blog/threat-intelligence/credential_stuffing_attacks_poised_to_accelerate_with_ai/#anchor-subtitle-3) showed underground markets selling config files targeting specific organizations for as low as US$5.99, with low-end configs given away free as teasers for paid offerings.

These costs are likely to keep falling. Commonly-used tools now ship with an [MCP server](https://docs.openbullet.dev/docs/configs/mcp-coding-agents) that lets AI coding agents write configs from natural language prompts. We are already seeing attackers use AI to produce working configs in the wild. If you've used an agent, you know how fast it can map out sites to automatically log you in. Attackers have that power, too.

This is why we are seeing more frequent attacks against a broad range of customer-facing services. The most effective way to stop these automated attacks is to reduce the role passwords play in your login flow.

## Credential Guard Is a Non-Negotiable Control When Passwords Are Allowed

Until your users stop relying on passwords, assume some of their passwords are already circulating. Stolen credentials flow constantly from data breaches, infostealer malware, and phishing, and attackers test them against login pages soon after they surface. Detection that waits for breach data to go public is too slow. [Auth0 Breached Password Detection](https://auth0.com/features/breached-passwords?_gl=1*vhc7e*_ga*MTY0OTU2MzU4OS4xNzg5Njc4OTUz*_ga_QKMSDV5369*czE3OTI3MDU2MDEkbzIkZzEkdDE3OTI3MDYxOTUkajMyJGwwJGgw#credential-guard) relies on published breach data and can take seven to thirteen months to flag a compromised credential. Credential Guard, part of the [Attack Protection](https://auth0.com/docs/secure/attack-protection) add-on for Enterprise plans, draws on breach data gathered from criminal communities and detects compromised credentials within hours of being leaked.

Detection only helps if you act on it. With no response actions configured, breached password detection runs in monitoring mode and logs breached password usage to your tenant logs. Turn on blocking for compromised credentials at login, signup, and password reset today, so a matched account can't be used until its owner changes the password. This is a non intrusive, low friction way to protect your customers and your business. This won't stop every attack, yet it reduces the damage a reused password has while you migrate to more secure authentication factors.

## Commodity Phishing Kits Are Built to Defeat MFA

Phishing kits have been accounting for MFA for years, as shown in Auth0’s own [comprehensive guide](https://auth0.com/blog/comprehensive-guide-auth0-security-identity-attacks/#MFA-Bypass). Attackers no longer rely on static fake pages that simply harvest passwords. They use Adversary-in-the-Middle (AiTM) reverse proxies that sit between your user and your actual authentication endpoint. It mirrors your legitimate login page, forwards requests in real time, and prompts the user for a phishable second factor (like an SMS OTP or an authenticator code). Once the user completes the prompt, the identity provider issues a session cookie. The proxy intercepts that cookie and hands it to the attacker, granting full access.

This is not bespoke malware employed by well-heeled actors and targeted at high-value, large firms. Back in 2025, Okta Threat Intelligence documented [phishing campaigns](https://www.okta.com/blog/threat-intelligence/attackers-target-hotelier-accounts-in-malvertising-and-phishing-/) that targeted modest hoteliers. Attackers bought search ads for cloud-based hotel management platforms, funneling front-desk staff to lookalike domains. The phishing kits were specifically built to capture SMS verification codes and session data live during the sign-in attempt.

The rise of AI-powered attacks bends attackers’ cost curve bending ever and lower makes relying on phishable second factors for customer logins less defensible than ever. If a factor can be typed into a form or confirmed out-of-band without origin binding, an automated proxy can steal it.

## Passkeys Solve These Problems

The lowest-friction, highest security solution is **migrating to passkeys**. 

Passkeys replace phishable shared secrets with cryptographic key pairs tied to the user's device. Because the browser and operating system cryptographically bind authentication ceremonies to the origin domain, passkeys are fundamentally immune to phishing.

Passkeys also eliminate risk introduced by external breaches. When you use passkeys, credential dumps from third-party sites do not expose your application because there is no shared credential to stuff.

## Move to Phishing Resistant Factors Now

Ready to implement phishing resistant factors? Follow [our passkeys documentation](https://auth0.com/docs/authenticate/database-connections/passkeys) to get started.

Do not have an Auth0 tenant yet? [Start for free](https://a0.to/blog_signup) today and build an application with passkeys right from the start. We look forward to building something secure together!

*These materials and any recommendations within are not legal, privacy, security, compliance, or business advice. These materials are intended for general informational purposes only and may not reflect the most current security, privacy, and legal developments nor all relevant issues. You are responsible for obtaining legal, security, privacy, compliance, or business advice from your own lawyer or other professional advisor and should not rely on the recommendations herein. Okta is not liable to you for any loss or damages that may result from your implementation of any recommendations in these materials. Okta makes no representations, warranties, or other assurances regarding the content of these materials. Information regarding Okta's contractual assurances to its customers can be found at okta.com/agreements.* 