Question 280
During an approved Falcon API integration test for Maplecrest Fintech in its third-party event connector service, a third-party integration specialist reviews the Falcon Next-Gen SIEM workflow. The concrete observation is: A retired server still appears as an active fleet-managed log collector long after it was decommissioned. The authorized diagnostic packet is NGSIEM-LAB-0070. The reviewer has the prior parser version plus a sanitized regression fixture. Keep events from other unaffected source integrations available. 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: Include collectors in the enterprise asset retirement workflow. It mitigates Fleet inventory was not reconciled to service retirement and last-heartbeat records, which produced the observed failure (A retired server still appears as an active fleet-managed log collector long after it was decommissioned). It should continue to be monitored using direct evidence such as The inventory no longer reports the decommissioned collector as active and replacement coverage is verified.
Incorrect Answers
Option A would guard against a different condition: A syslog sender transmits to a collector's old address after the server is moved to a different subnet. The failure mechanism here is: Fleet inventory was not reconciled to service retirement and last-heartbeat records. The directly relevant recurrence control is: Include collectors in the enterprise asset retirement workflow.
Option C would guard against a different condition: A regional operator can change every collector across global subsidiaries using a single administrative assignment. The failure mechanism here is: Fleet inventory was not reconciled to service retirement and last-heartbeat records. The directly relevant recurrence control is: Include collectors in the enterprise asset retirement workflow.
Option D would guard against a different condition: Fleet dashboard lists a collector as online although its last event is old and its queue has stopped draining. The failure mechanism here is: Fleet inventory was not reconciled to service retirement and last-heartbeat records. The directly relevant recurrence control is: Include collectors in the enterprise asset retirement workflow.