Question 160
During an approved controlled collector failure exercise for Larkspur Electronics in its incident automation boundary, a SIEM platform engineer reviews the Falcon Next-Gen SIEM workflow. The concrete observation is: A vendor connector shows enabled status but its last successful event is several days old. The authorized diagnostic packet is NGSIEM-LAB-0040. A synthetic event and a signed baseline configuration are available for the test. Do not disable production detections without authorized approval. 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: Require periodic synthetic event checks for critical connectors. It mitigates Administrative enablement is not equivalent to verified source delivery and parser success, which produced the observed failure (A vendor connector shows enabled status but its last successful event is several days old). It should continue to be monitored using direct evidence such as The exact test event is visible with expected timestamp, source and fields inside the agreed latency window.
Incorrect Answers
Option B would guard against a different condition: A data source integration is healthy but retrieves no events from one subsidiary tenant. The failure mechanism here is: Administrative enablement is not equivalent to verified source delivery and parser success. The directly relevant recurrence control is: Require periodic synthetic event checks for critical connectors.
Option C would guard against a different condition: A third-party application log appears with a generic product label and no accountable data owner. The failure mechanism here is: Administrative enablement is not equivalent to verified source delivery and parser success. The directly relevant recurrence control is: Require periodic synthetic event checks for critical connectors.
Option D would guard against a different condition: A cloud-native connector reports unauthorized errors after its service account was given dashboard read access only. The failure mechanism here is: Administrative enablement is not equivalent to verified source delivery and parser success. The directly relevant recurrence control is: Require periodic synthetic event checks for critical connectors.