Question 260
During an approved SIEM service health investigation for Cypress Fintech in its log collector staging fleet, a third-party integration specialist reviews the Falcon Next-Gen SIEM workflow. The concrete observation is: A Windows host forwards no logs after maintenance because the configured Falcon Log Collector service remains stopped. The authorized diagnostic packet is NGSIEM-LAB-0065. A stable event identifier and measured ingestion timestamp are present in the evidence. Use only the supported controls in the customer's licensed tenant. 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: Monitor collector service liveness and add startup verification to patch maintenance. It mitigates Host restart did not restore the collector process or its expected service startup configuration, which produced the observed failure (A Windows host forwards no logs after maintenance because the configured Falcon Log Collector service remains stopped). It should continue to be monitored using direct evidence such as A host reboot is followed by healthy collector status and receipt of a test syslog record.
Incorrect Answers
Option A would guard against a different condition: A newly installed Falcon Log Collector service runs but never appears in the intended SIEM tenant's managed collector inventory. The failure mechanism here is: Host restart did not restore the collector process or its expected service startup configuration. The directly relevant recurrence control is: Monitor collector service liveness and add startup verification to patch maintenance.
Option C would guard against a different condition: A collector forwarding over TLS rejects the ingest endpoint certificate after trust store rotation. The failure mechanism here is: Host restart did not restore the collector process or its expected service startup configuration. The directly relevant recurrence control is: Monitor collector service liveness and add startup verification to patch maintenance.
Option D would guard against a different condition: An internal service can programmatically POST JSON events yet the team installs a polling connector requiring a nonexistent service API. The failure mechanism here is: Host restart did not restore the collector process or its expected service startup configuration. The directly relevant recurrence control is: Monitor collector service liveness and add startup verification to patch maintenance.