An enterprise security architect is evaluating modern Identity and Access Management (IAM) controls to enforce Zero Trust principles and streamline federated access across a multi-cloud enterprise. Match each identity architecture protocol or mechanism on the left to its corresponding architectural implementation on the right.
- Continuous Access Evaluation Protocol (CAEP)Shares real-time session state events and posture changes between systems to enable immediate access revocation.
- System for Cross-domain Identity Management (SCIM)Automates user identity lifecycle management and attributes synchronization between an identity provider and cloud SaaS applications.
- Privileged Access Management (PAM) with Ephemeral CredentialsEliminates static administrative credentials by dynamically issuing short-lived, just-in-time access rights.
- OAuth 2.0 Demonstration of Proof-of-Possession (DPoP)Cryptographically binds access tokens to a specific client key pair to prevent token theft and unauthorized replay attacks.
Answer
Continuous Access Evaluation Protocol (CAEP) matches real-time session state and posture event sharing; System for Cross-domain Identity Management (SCIM) matches automated identity lifecycle provisioning across SaaS applications; Privileged Access Management (PAM) with Ephemeral Credentials matches eliminating static administrative credentials via short-lived access rights; and OAuth 2.0 Demonstration of Proof-of-Possession (DPoP) matches cryptographically binding tokens to client key pairs to prevent replay attacks.
Continuous Access Evaluation Protocol (CAEP) allows identity providers and relying parties to exchange real-time security events such as session revocation or risk score changes. System for Cross-domain Identity Management (SCIM) standardizes user provisioning workflows to automate account lifecycle events between identity stores and SaaS applications. Privileged Access Management (PAM) with ephemeral credentials reduces attack surfaces by dynamically issuing short-lived administrative credentials on demand rather than maintaining standing privileges. OAuth 2.0 Demonstration of Proof-of-Possession (DPoP) secures API access by binding OAuth tokens to a client's private key, preventing intercepted bearer tokens from being replayed.
Step-by-Step Solution
Key Concept
Enterprise IAM Architecture Protocols and Control Frameworks