Question 940
Following the issue — A Defender for Cloud custom recommendation is based on a tag that has no authorized definition, causing inconsistent compliance scores. — the team takes this action: Define the expected tagging policy and assessment criteria before using it as a compliance control. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Govern custom recommendation semantics and version changes. This mitigates the control weakness because: Posture findings require a stable control definition to be comparable across assets. Keep the intervention, Define the expected tagging policy and assessment criteria before using it as a compliance control., in the approved deployment, monitoring and change governance process.
Incorrect Answers
“Review Sentinel-specific role grants and external analyst accounts regularly” addresses a different recurring failure: Security operations authorization is distinct from broad Azure resource inspection permissions. For the condition in this question, maintain “Govern custom recommendation semantics and version changes” because posture findings require a stable control definition to be comparable across assets.
This safeguard is for the dependency described by: Risk-driven remediation needs environmental exposure and business impact beyond a simple count of alerts. The continuing risk here is determined by: Posture findings require a stable control definition to be comparable across assets. The targeted safeguard is “Govern custom recommendation semantics and version changes”.
“Reconcile playbook and Sentinel permission boundaries after workspace changes” addresses a different recurring failure: Automation rule conditions and playbook resource authorization must both allow invocation. For the condition in this question, maintain “Govern custom recommendation semantics and version changes” because posture findings require a stable control definition to be comparable across assets.