Question 390
During an approved SIEM rollout rehearsal for Trellis Energy in its federated identity audit stream, the log collection owner reviews the Falcon Next-Gen SIEM workflow. The concrete observation is: One firewall emits client_ip and another source uses src_address, leaving correlated connections unmatched. The authorized diagnostic packet is NGSIEM-LAB-0098. A synthetic event and a signed baseline configuration are available for the test. Document any remaining uncertainty in the engineering review record. Which independently observable result BEST demonstrates this particular SIEM engineering issue has been corrected?
Explanation
Correct Answer
Option C is best answer to this acceptance evidence question. The directly observable acceptance result is: A test lookup on the normalized address finds both logs and retains each original raw field. This verifies that Implement source-specific extraction into a shared CPS IP field using correct parsing validation addresses the specific observation (One firewall emits client_ip and another source uses src_address, leaving correlated connections unmatched). The technical distinction is: The parsers assign different source names instead of the common CPS source address representation.
Incorrect Answers
Option A would verify a separate condition: Operating-system logs arrive with a host alias but SIEM results omit the normalized host name. The observed issue here is: One firewall emits client_ip and another source uses src_address, leaving correlated connections unmatched. The necessary acceptance evidence is: A test lookup on the normalized address finds both logs and retains each original raw field.
Option B would verify a separate condition: A collector mixes milliseconds since epoch and ISO timestamps without normalizing event time. The observed issue here is: One firewall emits client_ip and another source uses src_address, leaving correlated connections unmatched. The necessary acceptance evidence is: A test lookup on the normalized address finds both logs and retains each original raw field.
Option D would verify a separate condition: A security appliance sends Common Event Format records but field extraction treats the extension as plain prose. The observed issue here is: One firewall emits client_ip and another source uses src_address, leaving correlated connections unmatched. The necessary acceptance evidence is: A test lookup on the normalized address finds both logs and retains each original raw field.