--- name: implementing-identity-verification-for-zero-trust description: Implements continuous, risk-adaptive identity verification for zero trust using phishing-resistant MFA (FIDO2/WebAuthn), risk-based conditional access, and identity governance aligned with NIST SP 800-207 and the CISA Zero Trust Maturity Model Identity Pillar. Use when designing zero trust identity controls, deploying phishing-resistant MFA, or building conditional access policies based on device posture, behavior, and location. domain: cybersecurity subdomain: zero-trust-architecture tags: - zero-trust - identity - authentication - mfa - identity-verification version: '1.0' author: mahipal license: Apache-2.0 atlas_techniques: - AML.T0052 nist_ai_rmf: - GOVERN-1.1 - GOVERN-1.7 - MAP-1.1 nist_csf: - PR.AA-01 - PR.AA-05 - PR.IR-01 - GV.PO-01 mitre_attack: - T1078 - T1190 - T1059 - T1566 - T1598 mitre_f3: version: '1.1' tactics: - initial-access - positioning - reconnaissance techniques: - id: F1006 name: Account Takeover tactic: initial-access source: f3 - id: T1110.004 name: 'Brute Force: Credential Stuffing' tactic: initial-access source: attack - id: T1111 name: Multi-Factor Authentication Interception tactic: initial-access source: attack - id: T1557 name: Adversary-in-the-Middle tactic: initial-access source: attack - id: T1539 name: Steal Web Session Cookie tactic: positioning source: attack - id: T1598 name: Phishing for Information tactic: reconnaissance source: attack --- # Implementing Identity Verification for Zero Trust ## Prerequisites - Understanding of zero trust principles (NIST SP 800-207) - Familiarity with identity providers (Azure AD, Okta, Ping Identity) - Knowledge of authentication protocols (SAML 2.0, OIDC, FIDO2) - Understanding of MFA and passwordless authentication ## Overview Identity is the foundational pillar of zero trust architecture. NIST SP 800-207 mandates that all resource authentication and authorization are dynamic and strictly enforced before access is allowed. Identity verification in zero trust goes beyond traditional username/password by implementing continuous, risk-adaptive authentication using multiple signals including device posture, behavioral biometrics, location, and network context. This skill covers implementing phishing-resistant MFA, continuous identity verification, risk-based conditional access, and identity governance aligned with the CISA Zero Trust Maturity Model Identity Pillar. ## When to Use - When deploying or configuring implementing identity verification for zero trust capabilities in your environment - When establishing security controls aligned to compliance requirements - When building or improving security architecture for this domain - When conducting security assessments that require this implementation ## Prerequisites - Familiarity with zero trust architecture concepts and tools - Access to a test or lab environment for safe execution - Python 3.8+ with required dependencies installed - Appropriate authorization for any testing activities ## Architecture ### Identity Verification Flow ``` User Access Request │ v ┌───────────────────────┐ │ Primary Authentication │ │ - FIDO2/WebAuthn key │ │ - Certificate-based │ │ - Passwordless │ └──────────┬────────────┘ v ┌───────────────────────┐ │ Contextual Assessment │ │ - Device posture │ │ - Network location │ │ - Geo-velocity check │ │ - Time of access │ │ - Behavioral baseline │ └──────────┬────────────┘ v ┌───────────────────────┐ │ Risk Scoring Engine │ │ - Aggregate signals │ │ - Calculate risk score │ │ - Compare to threshold │ └───┬──────────┬────────┘ │ │ Low Risk High Risk │ │ v v ┌────────┐ ┌──────────────┐ │ Grant │ │ Step-up Auth │ │ Access │ │ - Hardware key│ │ │ │ - Biometric │ │ │ │ - Manager OK │ └────────┘ └──────────────┘ ``` ### Identity Provider Architecture 1. **Primary IdP**: Azure AD / Okta / Ping Identity for centralized identity management 2. **FIDO2 Authenticators**: Hardware security keys (YubiKey) or platform authenticators (Windows Hello, Touch ID) 3. **Risk Engine**: Adaptive access using identity threat detection (Microsoft Entra ID Protection, Okta ThreatInsight) 4. **Identity Governance**: Lifecycle management, access reviews, just-in-time provisioning 5. **Privileged Identity**: Separate verification for elevated access (CyberArk, BeyondTrust) ## Key Concepts ### Phishing-Resistant MFA FIDO2/WebAuthn eliminates phishable credentials by binding authentication to the origin domain. Hardware security keys and platform authenticators provide cryptographic proof of identity without transmitting secrets. ### Continuous Identity Verification Rather than authenticating once at session start, zero trust requires ongoing verification through session token evaluation, behavioral analytics, and periodic re-authentication challenges based on risk signals. ### Risk-Based Conditional Access Conditional access policies evaluate multiple signals (user risk level, sign-in risk, device compliance, location) to dynamically adjust authentication requirements and access grants. ### Identity Threat Detection AI-driven analytics detect compromised identities through impossible travel detection, anomalous sign-in patterns, credential stuffing detection, and token replay attacks. ## Workflow ### Phase 1: Identity Infrastructure 1. **Consolidate Identity Providers** - Audit all identity sources across the organization - Federate to a single authoritative IdP using SAML 2.0 or OIDC - Configure SCIM for automated provisioning and deprovisioning - Eliminate local accounts and shared credentials 2. **Deploy Phishing-Resistant MFA** - Enroll all users in FIDO2/WebAuthn with hardware security keys - Configure platform authenticators (Windows Hello for Business, macOS Touch ID) - Disable SMS and voice call as MFA methods (phishable) - Create conditional access policy requiring phishing-resistant methods for all sign-ins 3. **Configure Conditional Access Policies** - Require compliant device for access to sensitive applications - Block legacy authentication protocols (basic auth, IMAP, POP3) - Require MFA for all users from untrusted locations - Enforce session time limits with re-authentication - Block or require additional verification for high-risk sign-ins ### Phase 2: Risk-Based Authentication 4. **Enable Identity Threat Detection** - Activate Microsoft Entra ID Protection or Okta ThreatInsight - Configure risk levels: low (allow), medium (require MFA), high (block and investigate) - Enable impossible travel detection and anomalous token alerts - Integrate identity risk signals with SIEM/SOAR 5. **Implement Step-Up Authentication** - For sensitive operations (privilege elevation, financial transactions), require additional verification - Configure step-up policies: re-authenticate with hardware key - Integrate with PAM for privileged session approval workflows - Log all step-up events for audit trail ### Phase 3: Continuous Verification 6. **Deploy Continuous Access Evaluation (CAE)** - Enable Continuous Access Evaluation Protocol (CAEP) for real-time token revocation - Configure critical event triggers: user disabled, password changed, location change - Test that token revocation occurs within minutes (not hours) of security event - Monitor CAE event logs for operational health 7. **Implement Session Controls** - Configure session duration limits based on application sensitivity - Enable sign-in frequency controls (re-authenticate every N hours) - Implement persistent browser session controls - Configure app-enforced restrictions for unmanaged devices ### Phase 4: Identity Governance 8. **Automate Identity Lifecycle** - Configure joiner-mover-leaver workflows with HR system integration - Automate access provisioning based on role and department - Enable just-in-time access for temporary elevated permissions - Configure automatic access expiration for contractors and guests 9. **Implement Access Reviews** - Schedule quarterly access certification campaigns - Configure automated reminders and escalation - Require manager approval for continued access - Auto-revoke access for unreviewed certifications ## Validation Checklist - [ ] Single authoritative IdP with all applications federated - [ ] FIDO2/WebAuthn enrolled for all users - [ ] SMS and voice MFA methods disabled - [ ] Legacy authentication protocols blocked - [ ] Conditional access policies enforced for all applications - [ ] Identity threat detection active with risk-based policies - [ ] Continuous Access Evaluation enabled and tested - [ ] Step-up authentication configured for sensitive operations - [ ] Identity lifecycle automated with HR integration - [ ] Quarterly access reviews scheduled and operational - [ ] Identity events streaming to SIEM ## References - NIST SP 800-207: Zero Trust Architecture - NIST SP 800-63B: Digital Identity Guidelines - Authentication - CISA Zero Trust Maturity Model v2.0 - Identity Pillar - FIDO Alliance WebAuthn Specification - Microsoft Entra Conditional Access Documentation --- Source attribution: mukul975 Original project: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-identity-verification-for-zero-trust/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Dave AI resource metadata Creator / publisher: mukul975 Original project: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-identity-verification-for-zero-trust/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Operations Roles: IT Operations, Security Engineer Specialties: Specialty not specified Tools: Azure Ad, Okta, Ping Identity Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 5c1aacff18df6c62c2659234f133c16511629626387c20e23ca6ddd401838f50