During a routine security review of cloud identity operations, a security analyst discovers that an automated data synchronization process uses a legacy service account configured with a long-lived static API key. The key was inadvertently committed to an internal repository, allowing an unauthorized external entity to request access tokens and enumerate cloud resources. Which of the following operational controls should the security team implement to remediate this vulnerability and secure the service identity lifecycle? (Select TWO.)
- Migrate the automated service identity to use workload identity federation with short-lived, ephemeral tokens instead of hardcoded credentials.Cevap
- BEnforce strict network perimeter firewall rules at the local datacenter border to drop all external authentication requests.
- Configure risk-based conditional access policies to evaluate request context and block token issuance from unexpected locations or anomalous sources.Cevap
- DReassign the service account to a restricted role group while retaining the static key authentication mechanism.
Cevap
The security team should migrate the service account to workload identity federation with short-lived tokens and implement contextual conditional access policies.
Migrating to workload identity federation eliminates static long-lived credentials by issuing short-lived tokens based on trusted identity relationships. Combining this with risk-based conditional access ensures token requests from untrusted origins or anomalous locations are blocked automatically.
Adım Adım Çözüm
Anahtar Kavram
Workload Identity Federation and Conditional Access Control in IAM Operations