Question 600
During an approved SIEM service health investigation for Horizon Cloud Services in its federated identity audit stream, the log collection owner reviews the Falcon Next-Gen SIEM workflow. The concrete observation is: A CSV lookup lists the same user principal twice with conflicting department values, causing inconsistent enrichment. The authorized diagnostic packet is NGSIEM-LAB-0150. 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 A is best answer to this recurrence prevention question. The repeatable safeguard is: Validate cardinality and source-of-truth precedence on each lookup upload. It mitigates Lookup-file quality checks do not enforce the intended unique key and conflict resolution rule, which produced the observed failure (A CSV lookup lists the same user principal twice with conflicting department values, causing inconsistent enrichment). It should continue to be monitored using direct evidence such as One known test user receives the approved department and a duplicate-key audit finds no unresolved conflicts.
Incorrect Answers
Option B would guard against a different condition: A query joining SIEM events to an IP reputation lookup returns no context although both datasets contain the same address. The failure mechanism here is: Lookup-file quality checks do not enforce the intended unique key and conflict resolution rule. The directly relevant recurrence control is: Validate cardinality and source-of-truth precedence on each lookup upload.
Option C would guard against a different condition: A rule editor expects new detections from a rule set inactive for testing. The failure mechanism here is: Lookup-file quality checks do not enforce the intended unique key and conflict resolution rule. The directly relevant recurrence control is: Validate cardinality and source-of-truth precedence on each lookup upload.
Option D would guard against a different condition: A security engineer uploads a lookup containing real employee password hashes to make a detection dashboard more convenient. The failure mechanism here is: Lookup-file quality checks do not enforce the intended unique key and conflict resolution rule. The directly relevant recurrence control is: Validate cardinality and source-of-truth precedence on each lookup upload.