Question 820
Following the issue — A subscription Contributor cannot retrieve a Key Vault secret and responds by trying to assign subscription Owner. — the team takes this action: Grant the least-privileged supported vault data role to the intended identity. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Keep management-plane and secret data-plane access review separate. This mitigates the control weakness because: Azure resource Contributor does not necessarily include Key Vault secret-value data access. Keep the intervention, Grant the least-privileged supported vault data role to the intended identity., in the approved deployment, monitoring and change governance process.
Incorrect Answers
“Maintain connector-to-detection data source maps for critical analytics rules” addresses a different recurring failure: Different Microsoft connectors expose distinct data sources and have prerequisites. For the condition in this question, maintain “Keep management-plane and secret data-plane access review separate” because azure resource Contributor does not necessarily include Key Vault secret-value data access.
That review protects the control associated with: Detection of exposed credentials does not necessarily perform credential lifecycle remediation. It does not directly prevent the stated recurrence, which concerns: Azure resource Contributor does not necessarily include Key Vault secret-value data access. The appropriate guardrail is “Keep management-plane and secret data-plane access review separate”.
This safeguard is for the dependency described by: A custom regulatory standard's usefulness depends on correct underlying policy assessments. The continuing risk here is determined by: Azure resource Contributor does not necessarily include Key Vault secret-value data access. The targeted safeguard is “Keep management-plane and secret data-plane access review separate”.