Question 1160
Following the issue — An analytics rule references a Sentinel table that has stopped receiving data and continues reporting zero matches as if the threat disappeared. — the team takes this action: Restore collection or correct the query and confirm data freshness before trusting the rule. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Alarm on stale data sources used by high-priority detection rules. This mitigates the control weakness because: Scheduled analytics require timely relevant ingested data to produce meaningful results. Keep the intervention, Restore collection or correct the query and confirm data freshness before trusting the rule., in the approved deployment, monitoring and change governance process.
Incorrect Answers
This safeguard is for the dependency described by: Overlapping management identities can fragment security evidence for the same workload. The continuing risk here is determined by: Scheduled analytics require timely relevant ingested data to produce meaningful results. The targeted safeguard is “Alarm on stale data sources used by high-priority detection rules”.
“Reassess active exemptions and their business owners each month” addresses a different recurring failure: Exceptions reduce effective policy coverage and need explicit accountability. For the condition in this question, maintain “Alarm on stale data sources used by high-priority detection rules” because scheduled analytics require timely relevant ingested data to produce meaningful results.
That review protects the control associated with: Instance-only remediation can be undone when insecure source images are reused. It does not directly prevent the stated recurrence, which concerns: Scheduled analytics require timely relevant ingested data to produce meaningful results. The appropriate guardrail is “Alarm on stale data sources used by high-priority detection rules”.