Question 840
During an approved controlled collector failure exercise for Amberfield Labs in its SOC dashboard workspace, a detection engineering reviewer reviews the Falcon Next-Gen SIEM workflow. The concrete observation is: A workflow automatically isolates every host when any low-severity SIEM alert appears. The authorized diagnostic packet is NGSIEM-LAB-0210. A stable event identifier and measured ingestion timestamp are present in the evidence. 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 A is best answer to this recurrence prevention question. The repeatable safeguard is: Test negative and critical-asset workflow cases before enabling automated containment. It mitigates The Falcon Fusion trigger lacks severity, detection type or asset criticality conditions limiting the response action, which produced the observed failure (A workflow automatically isolates every host when any low-severity SIEM alert appears). It should continue to be monitored using direct evidence such as A benign test alert is ignored and a confirmed approved pattern enters the correct review path.
Incorrect Answers
Option B would guard against a different condition: Repeated detections launch the same workflow twice and cause duplicate tickets and inconsistent case state. The failure mechanism here is: The Falcon Fusion trigger lacks severity, detection type or asset criticality conditions limiting the response action. The directly relevant recurrence control is: Test negative and critical-asset workflow cases before enabling automated containment.
Option C would guard against a different condition: A case-enrichment workflow closes incidents even when its external threat-intelligence API call fails. The failure mechanism here is: The Falcon Fusion trigger lacks severity, detection type or asset criticality conditions limiting the response action. The directly relevant recurrence control is: Test negative and critical-asset workflow cases before enabling automated containment.
Option D would guard against a different condition: An unattended SIEM reporting job fails after its short-lived access token expires. The failure mechanism here is: The Falcon Fusion trigger lacks severity, detection type or asset criticality conditions limiting the response action. The directly relevant recurrence control is: Test negative and critical-asset workflow cases before enabling automated containment.