Soru

Zorluk: OrtaIdentity and Access Management Architecture

An enterprise security architect is designing an Identity and Access Management (IAM) framework to address several distinct security requirements across a hybrid cloud environment. Match each IAM architectural mechanism on the left with its corresponding enterprise use case on the right.

  • Ephemeral Credential Broker (Just-In-Time Access)Granting short-lived cloud infrastructure permissions on demand without distributing persistent static access keys.
  • Vaulted Credential Session ProxyObfuscating root passwords while recording and isolating administrative sessions to legacy infrastructure.
  • SCIM-Based Dynamic Provisioning EngineAutomating real-time user lifecycle identity synchronization across cloud service providers and SaaS applications.
  • Certificate-Based Workload mTLS ArchitectureEstablishing cryptographically verified service-to-service authentication for zero-trust microsegments.

Cevap

Ephemeral Credential Broker matches short-lived cloud permissions. Vaulted Credential Session Proxy matches isolating administrative sessions and obfuscating root passwords. SCIM-Based Dynamic Provisioning Engine matches user lifecycle identity synchronization. Certificate-Based Workload mTLS Architecture matches service-to-service authentication for zero-trust microsegments.
Each IAM architecture mechanism directly addresses its respective enterprise design goal: Ephemeral Brokers enable short-lived Just-In-Time access; Session Proxies secure and audit legacy administrator credentials without revealing passwords; SCIM automates account lifecycle management across external platforms; and Workload mTLS enforces mutual cryptographic authentication in microservice networks.

Adım Adım Çözüm

1
Analyze the IAM architectural mechanisms to determine their functional capabilities.
Categorized mechanisms into short-lived authorization (ephemeral broker), privileged account proxying (session proxy), user identity lifecycle management (SCIM), and machine identity authentication (mTLS).
Evaluating core capabilities allows proper mapping to security requirements.
2
Match each control mechanism to the enterprise scenario that explicitly requires its technical implementation.
Aligned temporary permissions with JIT brokers, legacy session recording with vault proxies, identity synchronization with SCIM, and zero-trust workload traffic security with mTLS.
Ensures architectural alignment between IAM security controls and specific enterprise operational requirements.

Anahtar Kavram

Identity and Access Management Architecture Controls and Protocols
Bu soruyu puanla