An enterprise security architecture team is evaluating modern Identity and Access Management (IAM) components to enhance security across hybrid environments. Based on enterprise security best practices, how should each IAM standard or architecture component be matched to its primary architectural role?
- SCIM (System for Cross-domain Identity Management)Automating user account provisioning and deprovisioning across external SaaS applications
- OAuth 2.0 Token ExchangePropagating delegated user context and security tokens securely across internal microservices
- Privileged Access Management (PAM) with Ephemeral CredentialsEliminating static admin secrets by issuing short-lived dynamic credentials for system access
- FIDO2 / WebAuthn FrameworkProviding phishing-resistant multi-factor authentication bound to hardware security keys
Answer
Each IAM architectural component correctly aligns with its core functionality: SCIM handles automated identity provisioning, OAuth 2.0 Token Exchange propagates identity across microservices, PAM with ephemeral credentials eliminates static admin credentials, and FIDO2/WebAuthn delivers phishing-resistant authentication.
SCIM automates cross-domain provisioning; OAuth 2.0 Token Exchange securely transfers delegative identity context across API endpoints; PAM with ephemeral credentials removes persistent privileged secrets; and FIDO2/WebAuthn provides hardware-backed, domain-bound authentication resistant to phishing.
Step-by-Step Solution
Key Concept
Identity and Access Management Architecture Components and Protocols
Estimated Time:2m 0s