Implement continuous identity verification for zero trust using phishing-resistant
SKILL.md
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
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.