Answer: For Defense Access, all accounts that can sign in to the Granted Workspace must have multi-factor authentication enabled, and by December 15, 2026 they must use phishing-resistant multi-factor authentication (FIDO2/WebAuthn security key, passkey, or smartcard/PIV), with email magic-link sign-in disabled. Long-lived static credentials such as API keys must not be used to access the model by the Cutoff Date, and each platform requires short-lived credentials from its native identity service. Status: Confirmed Entry: tool/claude-apps/permissions-and-security/cyber-verification-defense-access-requirements Revision: 2 Digest: sha256:da0dda6bfcd93eb5 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:00:57Z Last changed: 2026-11-18T12:07:10Z (Phishing-resistant MFA methods: — → (i) a FIDO2/WebAuthn security key, (ii) a passkey, on the device or in a password manager, or (iii) a smartcard/PIV) Last verified: 2026-11-20T12:10:45Z Next check: 2026-11-21T12:10:45Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of MFA requirement | multi-factor authentication enabled | [1] | 2026-11-20 Cutoff Date | December 15, 2026 | [1] | 2026-11-20 Phishing-resistant MFA methods | (i) a FIDO2/WebAuthn security key, (ii) a passkey, on the device or in a password manager, or (iii) a smartcard/PIV | [1] | 2026-11-20 Disallowed sign-in | email magic-link sign-in must be disabled | [1] | 2026-11-20 Credential management | downloaded, exported, or otherwise long-lived static credentials, including API keys, must not be used to access the model | [1] | 2026-11-20 Interim API key replacement | replaced at least every 7 days | [1] | 2026-11-20 Approved Users limit | There is no default limit on the number of Approved Users at this Access Level. | [1] | 2026-11-20 Sources: [1] Anthropic. "Cyber Verification Program Security Requirements | Claude Help Center". https://support.claude.com/en/articles/17202708-cyber-verification-program-security-requirements Role: primary. Accessed: 2026-11-20T12:10:45Z Quote: "must have multi-factor authentication enabled" (Supports: MFA requirement) Quote: "By December 15, 2026 (the "Cutoff Date")" (Supports: Cutoff Date) Quote: "(i) a FIDO2/WebAuthn security key, (ii) a passkey, on the device or in a password manager, or (iii) a smartcard/PIV" (Supports: Phishing-resistant MFA methods) Quote: "email magic-link sign-in must be disabled" (Supports: Disallowed sign-in) Quote: "downloaded, exported, or otherwise long-lived static credentials, including API keys, must not be used to access the model" (Supports: Credential management) Quote: "replaced at least every 7 days" (Supports: Interim API key replacement) Quote: "There is no default limit on the number of Approved Users at this Access Level." (Supports: Approved Users limit) Snapshot SHA-256: 7512b4a511b7fa0f52c64a054337011f1ccf94fc56fcd93db7f01e49f9a2b9cc (captured 2026-11-17T12:14:00Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-17T12:14:01Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:10:45Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:10:45Z Last attempt: 2026-11-20T12:10:45Z Notes and limitations: Extracted automatically from a single official source (section "2. Defense Access."). Related: https://latestn.com/tool/claude-apps/permissions-and-security/cyber-verification-defense-individuals-requirements What security requirements apply to Defense Access for Individuals in Claude's Cyber Verification Program? https://latestn.com/tool/claude-apps/permissions-and-security/cyber-verification-red-team-specialized-requirements What are the security requirements for Red Team Access and Specialized Access in Claude's Cyber Verification Program? https://latestn.com/tool/claude-apps/permissions-and-security/deliver-managed-settings How do I deliver managed policy settings for Claude Code in Claude Enterprise? https://latestn.com/tool/claude-apps/permissions-and-security/csam-match-consequences What happens when an image I send to Claude matches known CSAM? https://latestn.com/tool/claude-apps/permissions-and-security/custom-connector-security-privacy What are the security and privacy considerations for custom connectors in Claude? https://latestn.com/tool/claude-apps/permissions-and-security/cyber-verification-all-access-requirements What security requirements must a customer meet for all Cyber Verification Program access levels in Claude? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T12:07:10Z | changed | Phishing-resistant MFA methods: — → (i) a FIDO2/WebAuthn security key, (ii) a passkey, on the device or in a password manager, or (iii) a smartcard/PIV | [1] 2026-11-18T12:07:10Z | changed | Cutoff Date: — → December 15, 2026 | [1] 2026-11-18T12:07:10Z | changed | Approved Users limit: There is no default limit on the number of Approved Users at this Access Level → There is no default limit on the number of Approved Users at this Access Level. | [1] 2026-11-18T12:07:10Z | changed | Non-qualifying methods: SMS, voice, emailed codes, authenticator-app codes, and push approvals do not qualify → — | [1] 2026-11-18T12:07:10Z | changed | Qualifying MFA methods: (i) a FIDO2/WebAuthn security key, (ii) a passkey, on the device or in a password manager, or (iii) a smartcard/PIV → — | [1] 2026-11-18T12:07:10Z | changed | Phishing-resistant MFA cutoff date: December 15, 2026 → — | [1] 2026-11-13T03:00:57Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-apps/permissions-and-security/cyber-verification-defense-access-requirements/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-apps/permissions-and-security/cyber-verification-defense-access-requirements POST: https://latestn.com/dispute/tool/claude-apps/permissions-and-security/cyber-verification-defense-access-requirements with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-apps/permissions-and-security/cyber-verification-defense-access-requirements?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the security requirements for Defense Access in Claude's Cyber Verification Program? Revision 2, last verified 2026-11-20T12:10:45Z. https://latestn.com/tool/claude-apps/permissions-and-security/cyber-verification-defense-access-requirements (accessed 2026-11-21T10:05:27Z). @misc{LatestN_tool_claude_apps_permissions_and_security_cyber_verification_defense_access_requirements_r2, title = {What are the security requirements for Defense Access in Claude's Cyber Verification Program?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-apps/permissions-and-security/cyber-verification-defense-access-requirements}}, note = {Revision 2; digest sha256:da0dda6bfcd93eb5; last verified 2026-11-20T12:10:45Z; accessed 2026-11-21T10:05:27Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-apps/permissions-and-security/cyber-verification-defense-access-requirements