An organization is upgrading its access control infrastructure to allow third-party contractors temporary access to cloud-hosted management portals and APIs. The security team mandates that credentials must not be statically stored on client devices, identity assertions must be centralized via modern web standards, and access decisions must not rely on internal network perimeter position. Which of the following security mechanisms should be incorporated into this Identity and Access Management (IAM) architecture? (Select TWO.)
- Deploying OpenID Connect (OIDC) with OAuth 2.0 to handle federated authentication and short-lived scoped token issuanceCevap
- Implementing a Privileged Access Management (PAM) system configured for Just-In-Time (JIT) access and ephemeral credential generationCevap
- CConfiguring a static RADIUS server with MAC Authentication Bypass (MAB) at the network perimeter boundary
- DApplying discretionary access control (DAC) lists at the network firewall layer to restrict traffic based on contractor client IP addresses
Cevap
The architectural requirement is met by combining OpenID Connect (OIDC) with OAuth 2.0 for federated web/API authentication and a Privileged Access Management (PAM) system utilizing Just-In-Time (JIT) ephemeral credentials.
Combining OpenID Connect (OIDC) with OAuth 2.0 provides standard, federated identity assertions and scoped access tokens for modern cloud portals and APIs. Integrating Privileged Access Management (PAM) configured for Just-In-Time (JIT) access ensures credentials are generated dynamically on demand and automatically invalidated, satisfying the prohibition against static credentials.
Adım Adım Çözüm
Anahtar Kavram
Privileged Access Management (PAM) with Just-In-Time (JIT) Provisioning and OIDC/OAuth2 Federated Architecture