Question 780
During an approved cross-source analytics validation for Elmwood Energy in its log collector staging fleet, the log collection owner reviews the Falcon Next-Gen SIEM workflow. The concrete observation is: A tune-up makes a rule run less often without widening the search window, creating blind periods. The authorized diagnostic packet is NGSIEM-LAB-0195. The change ticket contains a source owner, review date and rollback step. Maintain the intended search-domain and data-retention boundary. Which repeatable safeguard BEST prevents this specific SIEM engineering failure from recurring?
Explanation
Correct Answer
Option B is best answer to this recurrence prevention question. The repeatable safeguard is: Regression-test edge timing whenever schedule or source ingestion changes. It mitigates The schedule and window are no longer aligned to cover source delivery times, which produced the observed failure (A tune-up makes a rule run less often without widening the search window, creating blind periods). It should continue to be monitored using direct evidence such as A delayed fixture arriving near the schedule boundary is detected by the revised rule.
Incorrect Answers
Option A would guard against a different condition: A custom rule joins endpoint and proxy data but the resulting detection contains no references to contributing records. The failure mechanism here is: The schedule and window are no longer aligned to cover source delivery times. The directly relevant recurrence control is: Regression-test edge timing whenever schedule or source ingestion changes.
Option C would guard against a different condition: A scheduled rule floods analysts with permitted backup service activity after an infrastructure migration. The failure mechanism here is: The schedule and window are no longer aligned to cover source delivery times. The directly relevant recurrence control is: Regression-test edge timing whenever schedule or source ingestion changes.
Option D would guard against a different condition: A published rule cannot be rolled back easily because its previous query and threshold are undocumented. The failure mechanism here is: The schedule and window are no longer aligned to cover source delivery times. The directly relevant recurrence control is: Regression-test edge timing whenever schedule or source ingestion changes.