Phishing-Resistant MFA
Phishing-Resistant MFA 是什么?
Phishing-Resistant MFAMFA methods that cryptographically bind authentication to the legitimate web origin — FIDO2/WebAuthn passkeys, smart cards, and Windows Hello — rendering AiTM proxy phishing, MFA fatigue, and OTP interception ineffective.
Phishing-resistant MFA is the category of authentication methods that cannot be intercepted, replayed, or tricked into authorizing the wrong relying party. The canonical examples are FIDO2 / WebAuthn (security keys, platform passkeys on Apple, Android, and Windows), PIV smart cards, and Windows Hello for Business. All of them share the same security property: the authenticator only generates a signature for the specific RP-ID (origin) it is presented with, so a credential registered with `login.example.com` cannot be coerced into signing a challenge from `login-evil.example.com`, even via a transparent AiTM proxy. They also defeat the lesser-but-common attacks that still work against TOTP and push-based MFA — MFA fatigue, push bombing, OTP-relay phishing kits (EvilProxy, Tycoon, Evilginx) — because there is no human-typed or human-tapped artifact for an attacker to relay. Major U.S. and European regulators (CISA, OMB M-22-09, ENISA, U.K. NCSC) have moved from 'use MFA' to 'use phishing-resistant MFA' guidance, and many enterprises now require it for privileged accounts and for any user accessing federated cloud services.
● 示例
- 01
A bank requires hardware FIDO2 keys for all admin users, eliminating the AiTM-phishing risk that previously affected TOTP and push-MFA accounts.
- 02
U.S. Executive Order 14028 and OMB M-22-09 push federal civilian agencies to phishing-resistant MFA for all interactive logins by 2024.
● 常见问题
Phishing-Resistant MFA 是什么?
MFA methods that cryptographically bind authentication to the legitimate web origin — FIDO2/WebAuthn passkeys, smart cards, and Windows Hello — rendering AiTM proxy phishing, MFA fatigue, and OTP interception ineffective. 它属于网络安全的 身份与访问 分类。
Phishing-Resistant MFA 是什么意思?
MFA methods that cryptographically bind authentication to the legitimate web origin — FIDO2/WebAuthn passkeys, smart cards, and Windows Hello — rendering AiTM proxy phishing, MFA fatigue, and OTP interception ineffective.
Phishing-Resistant MFA 是如何工作的?
Phishing-resistant MFA is the category of authentication methods that cannot be intercepted, replayed, or tricked into authorizing the wrong relying party. The canonical examples are FIDO2 / WebAuthn (security keys, platform passkeys on Apple, Android, and Windows), PIV smart cards, and Windows Hello for Business. All of them share the same security property: the authenticator only generates a signature for the specific RP-ID (origin) it is presented with, so a credential registered with `login.example.com` cannot be coerced into signing a challenge from `login-evil.example.com`, even via a transparent AiTM proxy. They also defeat the lesser-but-common attacks that still work against TOTP and push-based MFA — MFA fatigue, push bombing, OTP-relay phishing kits (EvilProxy, Tycoon, Evilginx) — because there is no human-typed or human-tapped artifact for an attacker to relay. Major U.S. and European regulators (CISA, OMB M-22-09, ENISA, U.K. NCSC) have moved from 'use MFA' to 'use phishing-resistant MFA' guidance, and many enterprises now require it for privileged accounts and for any user accessing federated cloud services.
如何防御 Phishing-Resistant MFA?
针对 Phishing-Resistant MFA 的防御通常结合技术控制与运营实践,详见上方完整定义。
Phishing-Resistant MFA 还有哪些其他名称?
常见的别称包括: FIDO2 MFA, Origin-bound MFA。
● 相关术语
- identity-access№ 458
FIDO2
FIDO 联盟推出的开放认证标准,结合 WebAuthn(浏览器 API)和 CTAP(认证器协议),实现抗钓鱼的无密码登录。
- identity-access№ 1359
WebAuthn
W3C 标准 JavaScript API,允许 Web 应用使用存储在平台或外部认证器上的公钥凭据来注册和认证用户。
- identity-access№ 888
通行密钥 (Passkey)
一种抗钓鱼的 FIDO2/WebAuthn 凭据,使用绑定设备或可同步的非对称密钥对,以加密挑战-响应取代密码。
- identity-access№ 793
多因素认证 (MFA)
在授予访问权限前,要求提供两个或两个以上独立认证因素(通常来自不同类别)的认证方法。
- identity-access№ 750
MFA 疲劳攻击(Push Bombing)
攻击者已获得有效密码后,不断向受害者发起 MFA 推送提示,直至对方因困惑或厌烦而误点同意的攻击。
- identity-access№ 1309
U2F (通用第二因素)
FIDO 联盟提出的开放认证标准,通过 USB、NFC 或蓝牙安全密钥为密码增加硬件第二因素。