资源 · 24

部署具有安全恢复功能的防钓鱼身份验证。

使用与真实服务绑定的因素,并保护注册、丢失和撤销。

已更新 · 17 min

虚构的无人身份核验室:两把安全密钥、空白卡片和酒红色文件夹 由人工智能生成的编辑插图

本指南有助于实现的目标

  • 绘制访问路径图
  • 选择抗攻击协议
  • 保护注册
  • 演练恢复

快速检查

  • 哪些帐户可以访问关键数据或功能?
  • 验证因子是否与真实服务进行加密绑定?
  • 谁授权新的身份验证器?
  • 如何撤销丢失设备的身份验证?
  • 例外情况是否有所有者和终止日期?

分步指南

  1. 1

    清点访问路径

    列出应用程序、联合身份验证、管理员、紧急帐户和当前方法。 识别仍然接受手动输入代码的登录方式。

    交付成果:帐户、应用程序和验证因子矩阵。

  2. 2

    选择所需的抗攻击能力

    评估绑定到通道或验证器名称的加密协议,例如应用程序支持的 WebAuthn/FIDO2。 NIST 不认为手动输入的 OTP 具有抗钓鱼攻击能力,因为虚假网站可以转发它们。

    交付成果:方法选择和已知局限性。

  3. 3

    试点敏感账户。

    使用代表性用户群体测试浏览器、设备、授权、可能的离线使用和可访问性。 提供多条授权路径,避免累积休眠访问权限。

    交付成果:试点场景和成功标准。

  4. 4

    保护注册

    添加密钥前验证身份和会话,通知用户并记录事件。 测试拒绝来自可疑上下文的注册请求。

    交付成果:注册流程和事件记录。

  5. 5

    制定丢失和撤销计划。

    记录丢失身份验证器的报告、禁用、恢复和身份验证检查流程。 测试在不通过较弱通道绕过保护的情况下完成整个流程。

    交付成果:恢复和撤销演练。

  6. 6

    扩展和监控。

    按组推广,衡量覆盖范围,跟踪故障和异常情况,并在测试的恢复流程允许后停用旧方法。

    交付成果:迁移仪表板和异常登记表。

管理指标

指标衡量内容首要行动
覆盖面敏感账户采用抗性方法扩展部署
注册添加检查和通知修复薄弱路径
恢复模拟丢失无需绕过即可解决重复演练
例外情况保留所有者和过期时间的访问权限停用旧式因素

常见错误

  • 将所有 MFA 方法都称为防钓鱼
  • 确保登录安全,但注册机制薄弱
  • 缺少管理员和紧急账户
  • 在恢复机制生效之前停用旧式方法

常见问题解答

一次性代码是否足够?

NIST 解释说,手动输入的代码可能被冒名顶替服务转发,因此不具备防钓鱼功能。

是否每个人都需要硬件密钥?

选择取决于保障措施和具体情况;某些可同步的 WebAuthn 身份验证器可能适用于某些用途,并提供相应的恢复选项。

设备丢失后该如何处理?

撤销受影响的身份验证器,遵循已验证的恢复流程,并根据服务策略通知用户。

身份:认证要素、会话与恢复

此语言版本的详细参考说明以英语提供。

An authentication method must be assessed alongside enrolment, recovery and the sessions it opens. A passkey label, a phone or a biometric sensor does not by itself establish the assurance level of the entire service.

References use NIST SP 800-63B-4, finalised in July 2025, and WebAuthn Level 3, a W3C Recommendation since 25 August 2026. AALs describe authentication transactions rather than product scores or certifications earned by ticking this table. Application depends on service scope and risk assessment.

Sources consulted on .

空无一人的网络实验室中的两枚无品牌安全密钥 由人工智能生成的编辑插图
Two unbranded keys in an empty lab. Appearance proves neither key non-exportability nor assurance level.

Compare eight methods without confusing their guarantees

Compare eight methods without confusing their guarantees
Method and referenceProperty and conditionsRecovery and dependenciesEvidence to request
Entered password

NIST · Authenticators and password requirements

Knowledge factor; a false site can relay or capture the secret.Depends on the password manager and the password replacement path.Length policy, compromised-secret blocking and a tested replacement journey.
Manually entered TOTP

NIST · Authenticators and password requirements

Possession of a shared secret; manual entry does not bind the output to the legitimate session.Plan for loss of the generator and protection of seeds or provider backups.Authorised enrolment, secret protection and revocation; do not call every OTP phishing-resistant.
SMS or voice code

NIST · Authenticators and password requirements

PSTN out-of-band channel, restricted in the NIST framework; manual codes are not phishing-resistant.The number, carrier and SIM or line changes are dependencies.Channel justification, risk signals, alternatives and number-change procedure.
Simple push approval

NIST · Authenticators and password requirements

Approval without cryptographic verifier-name or channel binding does not establish phishing resistance.Lost phones and application re-enrolment require handling.Actual protocol, user intent and enrolment controls; the push label alone is insufficient.
Syncable WebAuthn with UV

NIST · Syncable Authenticators

W3C · WebAuthn Level 3

Cryptographic binding to the service; user verification (UV) must be requested and checked when required. Syncable keys are exportable in NIST terminology.The sync account, its devices and its recovery enter the trust boundary.Sync and UV requirements. Syncable methods do not fit AAL3, which prohibits key export.
Device-bound WebAuthn with UV

NIST · Authentication Assurance Levels

W3C · WebAuthn Level 3

Service binding and user verification. Device-bound alone does not establish non-exportable hardware protection.Device loss requires another authorised method or controlled recovery.Storage properties, UV, proof of non-exportability when needed and tests of actual clients.
WebAuthn key without UV

NIST · Authenticators and password requirements

W3C · WebAuthn Level 3

Service binding, but possession alone in this case. A touch or user presence (UP) flag is not proof of user verification (UV).Plan a second authorised method and lost-key revocation.UP/UV checks and the factor combination required by the service; hardware form alone does not establish MFA.
Biometrics considered alone

NIST · Authenticators and password requirements

In the NIST framework, biometrics accompany a physical authenticator in MFA; they are neither secrets nor sufficient standalone mechanisms.Provide a non-biometric alternative and protect biometric information appropriately.Comparison location, activation role and accessible alternative; distinguish biometric comparison from cryptographic proof.

Three AALs: distinguish requirements and recommendations

Three AALs: distinguish requirements and recommendations
Level and factorsResistance and key exportOverall reauthentication timeoutInactivity
AAL1

One factor can suffice at this level.

Phishing resistance not imposed by this level; key export permitted.At most 30 days: SHOULD recommendation.No numeric ceiling in this reference; define the service policy.
AAL2

Two distinct factors.

A phishing-resistant option must be offered; key export permitted under applicable conditions.At most 24 hours: SHOULD recommendation; establishing a definite overall limit remains mandatory.At most 1 hour: SHOULD recommendation.
AAL3

Cryptographic authenticator and additional or activation factor.

Phishing resistance and a non-exportable private key required.At most 12 hours: SHALL requirement.At most 15 minutes: SHOULD recommendation.

These values are not cookie lifetimes to copy blindly. NIST distinguishes overall and inactivity limits and then defines reauthentication rules. Applications may choose shorter periods based on risk. IAL concerns identity proofing and FAL federation: AAL does not replace either dimension. NIST §2 →

Passwords: seven precise NIST reference points

Single factor
Minimum 15 characters required.
Within MFA
Minimum 8 characters required when the password is used only in a multifactor process.
Accepted length
Allowing a maximum length of at least 64 characters is recommended.
Composition
No imposed mixture of character types.
Replacement
No arbitrary periodic changes; force a change when there is evidence of compromise.
Secrets to reject
Compare against commonly used, expected or compromised passwords.
Entry assistance
Allow password managers and autofill; permitting paste is recommended.

NIST §3.1.1.2 →

Recovery: four classes and their conditions

Previously saved code
At least 64 random bits in the NIST framework; offline subscriber storage, hashed server storage and invalidation after use.
Code issued on demand
Codes sent by text or voice are valid for at most 10 minutes; email codes for at most 24 hours. Verify addresses and apply the target level’s conditions.
Recovery contact
Organise contact addresses and associated checks; a personal relationship does not replace technical recovery requirements.
Repeated identity proofing
An option for previously identity-proofed accounts. Without prior identity proofing, do not claim to re-verify an unknown identity.

Replacing a forgotten password through another still-valid authenticator is binding a new authenticator rather than necessarily account recovery. Document notifications, delays, revocations and responsibilities so support does not become a bypass. NIST §4 →

Connect authentication, sessions and incidents

Connect authentication, sessions and incidents
StageProposed practical checkObservable evidence
EnrolCheck who authorises a new authenticator and notify the subscriber through a known path.Record of binding, associated method and authorisation basis.
AuthenticateCheck the protocol, expected domain and required factors before granting access.Results on chosen clients, with presence and verification indicators separated.
Manage the sessionDefine overall expiry, inactivity, reauthentication for sensitive actions and logout invalidation.Expired-session, logout and post-revocation access tests.
Report lossIdentify the affected authenticator, preserve useful evidence and decide invalidation based on suspected compromise.Report timeline and observed access result after handling.
RecoverFollow a documented path, notify and prevent an old session from adding a new method without appropriate checks.Successful recovery case and refused bypass case.
Leave the serviceRemove obsolete authenticators and access; address relevant sessions, devices and sync authorisations too.Revoked methods, removed access and remaining dependencies.

WebAuthn: verify the response at the service

The server must correlate the challenge, authorised origin, RP ID hash and signature with the expected ceremony and check required flags. UP signals presence; UV signals user verification. BE and BS describe credential backup eligibility and state without independently certifying the sync system. Use a maintained library and the complete procedures in specification sections 7.1 and 7.2. WebAuthn Level 3 →

Include people who use a different journey

WCAG 2.2 criterion 3.3.8, level AA, addresses cognitive tests during authentication with specific exceptions and assistance mechanisms. Test password managers, paste, labels, keyboard, cancellation and fallback in practice. NIST requires a non-biometric alternative; making it usable is part of design. WCAG 2.2 · 3.3.8 →

Continue with identity governance →

Primary references and scope

Publication and consultation dates are distinct. Proposed tests and evidence are editorial; linked normative texts govern. Vendor documentation describes its own product and does not establish your application’s AAL.

表单:准则、错误与对比度

此语言版本的详细参考说明以英语提供。

Authenticate without avoidable cognitive effort

SC 3.3.8 addresses cognitive tests at each authentication step, with specific alternatives, assistance mechanisms and exceptions. Verify security and usability together.

  • Try password managers and paste where relevant.
  • Examine recovery mechanisms in the actual journey.
  • Do not infer screen accessibility from the chosen authentication technology alone.

Open the WCAG review grid and contrast calculator →

W3C WAI · Understanding SC 3.3.8 · Accessible Authentication (Minimum) · Informative explanation · consulted 2026-10-23

官方参考文献

参考文献支持该方法。 请根据您的实际情况调整检查;它们并非认证。 原始参考文献标题和源文档可能使用其他语言。

参考资料查阅日期 .