资源 · 11
身份和帐户恢复:管理完整的生命周期
将帐户的创建、更改、权限、恢复和关闭与可验证的证据和预先演练的决策联系起来。
已更新 · 17 min
本指南有助于实现的目标
- 将每个帐户与个人或服务关联
- 降低常驻权限
- 保护恢复请求
- 快速撤销帐户而不中断连续性
快速检查
- 谁批准帐户创建和角色变更?
- 旧因素能否单独重置帐户?
- 共享帐户操作是否可归因?
- 权限是否会过期?
- 是否已执行手机丢失保护?
分步指南
- 1
清点身份和依赖关系
列出个人帐户、服务帐户、共享帐户、联合帐户和紧急帐户。 将它们与应用程序、所有者、身份验证方法和可访问数据关联起来。
交付成果:身份、帐户、系统和所有者注册表。
- 2
将生命周期与事件关联起来
定义新用户注册、移动办公、缺勤、角色变更、离职和删除的触发器。 衡量事件发生与有效访问权限变更之间的延迟。
交付成果:事件和操作矩阵。
- 3
降低权限
将日常使用与管理权限分离,限制高级访问权限的持续时间,并根据服务风险审查权限。
交付成果:角色目录和带日期标注的例外情况。
- 4
强化恢复机制
对于异常请求,使用独立证据、安全渠道、适当的延迟和人工升级机制。
交付成果:恢复决策树。
- 5
为丢失和泄露做好准备
规划会话、因素和设备撤销、服务台沟通、备用访问和适当的跟踪保留。
交付成果:锁定和恢复操作手册。
- 6
演练和改进
测试紧急离职、手机丢失和身份冒用尝试。 观察决策、时间安排、证据和运营影响。
交付成果:演练报告和补救计划。
虚构示例
示例情境
管理员在值班期间丢失了身份验证设备。 支持人员检查预先约定的证明,获得恢复的二次批准,并使受影响的会话失效。
决策及预期证据
该演练检查服务连续性,并保留请求、批准、替换因素和事后审查记录。
管理指标
| 指标 | 衡量内容 | 首要行动 |
|---|---|---|
| 归属帐户 | 关联到活跃所有者的帐户 | 优先处理无所有者帐户 |
| 撤销延迟 | 从事件发生到访问权限移除的时间 | 自动化可靠步骤 |
| 临时权限 | 具有持续时间和理由的提升访问权限 | 默认过期授权 |
| 验证恢复 | 每次请求都基于预期的证明 | 审查每次绕过 |
常见错误
- 将个人问题视为强有力的证据
- 允许支持人员在没有双重控制的情况下绕过多因素身份验证 (MFA)
- 忘记服务帐户
- 分配后保留权限
常见问题解答
多因素身份验证 (MFA) 是否足够?
不够。它降低了一些风险,但生命周期、恢复、会话和权限仍然可能存在漏洞。
是否应该禁止所有共享帐户?
优先使用个人身份。 如果仍然需要共享帐户,请记录原因、限制其使用范围并确保每次使用都可追溯。
应该首先执行哪些操作?
主要因素丢失以及高权限人员的紧急离职会迅速暴露真正的依赖关系。
身份:认证要素、会话与恢复
此语言版本的详细参考说明以英语提供。
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 .
Compare eight methods without confusing their guarantees
| Method and reference | Property and conditions | Recovery and dependencies | Evidence to request |
|---|---|---|---|
| Entered password | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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. |
No method matches the filters.
Three AALs: distinguish requirements and recommendations
| Level and factors | Resistance and key export | Overall reauthentication timeout | Inactivity |
|---|---|---|---|
| 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.
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
| Stage | Proposed practical check | Observable evidence |
|---|---|---|
| Enrol | Check who authorises a new authenticator and notify the subscriber through a known path. | Record of binding, associated method and authorisation basis. |
| Authenticate | Check the protocol, expected domain and required factors before granting access. | Results on chosen clients, with presence and verification indicators separated. |
| Manage the session | Define overall expiry, inactivity, reauthentication for sensitive actions and logout invalidation. | Expired-session, logout and post-revocation access tests. |
| Report loss | Identify the affected authenticator, preserve useful evidence and decide invalidation based on suspected compromise. | Report timeline and observed access result after handling. |
| Recover | Follow 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 service | Remove 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.
- NIST SP 800-63B-4 · final publication · Publication :
- NIST · Authentication Assurance Levels · Publication :
§2.1–2.3 - NIST · Authenticators and password requirements · Publication :
§3.1.1; §3.2.3; §3.2.5 - NIST · Authenticator Event Management · Publication :
§4.1; §4.2; §4.6 - NIST · Session Management · Publication :
§5 - NIST · Syncable Authenticators · Publication :
Appendix B - W3C · WebAuthn Level 3 · Publication : · W3C Recommendation
§6.1; §7.1–7.2 - W3C · Accessible Authentication (Minimum) · Publication :
WCAG 2.2 · 3.3.8 · AA
扩展:权限与访问
此语言版本的详细参考说明以英语提供。
Robust authentication does not describe extension access
Phishing resistance does not remove the need to examine what runs in the browser after a session opens. A manifest provides clues about cookies, scripting, debugging and identity without establishing collection.
- Test approved extensions in a profile dedicated to sensitive operations.
- For identity, inspect OAuth scopes and recipients; this permission does not enumerate identity-provider rights.
- Distinguish session revocation, token revocation, extension disablement and native-component removal.
Read the permission directory and manifest examples →
Google Chrome · Stay secure · Documentation consulted 2026-10-23; browser behaviour remains version-dependent
官方参考文献
参考文献支持该方法。 请根据您的实际情况调整检查;它们并非认证。 原始参考文献标题和源文档可能使用其他语言。
参考资料查阅日期 .
- NIST — SP 800-63B, Authentication and Lifecycle Management
- NIST — Cybersecurity Framework 2.0
- NIST SP 800-63B-4 · final publication
- NIST · Authentication Assurance Levels
- NIST · Authenticators and password requirements
- NIST · Authenticator Event Management
- NIST · Session Management
- NIST · Syncable Authenticators
- W3C · WebAuthn Level 3
- W3C · Accessible Authentication (Minimum)
- Google Chrome · Declare permissions
- Google Chrome · Stay secure
