An organization is designing an updated Identity and Access Management (IAM) architecture for its enterprise applications. The security team needs to support automated user account lifecycle management (creation, updates, and deprovisioning) across multiple third-party SaaS platforms. Additionally, they must implement a fine-grained access control mechanism capable of making real-time authorization decisions based on dynamic contextual attributes such as user location, device security posture, and time of access. Which of the following technologies should the security architect incorporate into the IAM architecture to satisfy these requirements? (Select TWO.)
- System for Cross-domain Identity Management (SCIM) for automated identity provisioning across cloud platformsAnswer
- Attribute-Based Access Control (ABAC) for evaluating dynamic contextual risk factors during authorization decisionsAnswer
- CSecurity Assertion Markup Language (SAML) 2.0 Web Browser SSO profile for batch user lifecycle database synchronization
- DImplicit network perimeter IP address whitelisting to grant internal directory access based on network location
Answer
The architecture should incorporate System for Cross-domain Identity Management (SCIM) for user account provisioning and Attribute-Based Access Control (ABAC) for dynamic authorization based on contextual attributes.
The correct options are System for Cross-domain Identity Management (SCIM) and Attribute-Based Access Control (ABAC). SCIM automates user identity exchange and lifecycle provisioning across disparate cloud systems. ABAC enables policy rules based on subject, resource, and environmental attributes (such as location and device posture), allowing real-time context-aware authorization.
Step-by-Step Solution
Key Concept
IAM protocols and access control models for cloud identity provisioning and dynamic authorization.