Question 760
Following the issue — A reporting system uses Azure SQL data masking but privileged database users can still view unmasked salary columns. — the team takes this action: Restrict privileged membership and choose encryption or appropriate application access controls for the true confidentiality requirement. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Review privileged database role members after periodic security policy changes. This mitigates the control weakness because: Masking rules typically do not protect data from users with relevant elevated SQL privileges. Keep the intervention, Restrict privileged membership and choose encryption or appropriate application access controls for the true confidentiality requirement., in the approved deployment, monitoring and change governance process.
Incorrect Answers
That review protects the control associated with: JIT can open constrained management access only for approved requests and durations. It does not directly prevent the stated recurrence, which concerns: Masking rules typically do not protect data from users with relevant elevated SQL privileges. The appropriate guardrail is “Review privileged database role members after periodic security policy changes”.
This safeguard is for the dependency described by: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad. The continuing risk here is determined by: Masking rules typically do not protect data from users with relevant elevated SQL privileges. The targeted safeguard is “Review privileged database role members after periodic security policy changes”.
“Test CMK fault scenarios and vault connectivity before enforcing network restrictions” addresses a different recurring failure: Storage encryption operations depend on continued authorized access to externally managed key material. For the condition in this question, maintain “Review privileged database role members after periodic security policy changes” because masking rules typically do not protect data from users with relevant elevated SQL privileges.