Question 790
During an approved authorized ingestion troubleshooting session for Quartz Research in its enterprise detection engineering environment, a detection engineering reviewer reviews the Falcon Next-Gen SIEM workflow. The concrete observation is: A vendor sends a severity integer but SIEM reporting presents it as the exact built-in Falcon severity scale. The authorized diagnostic packet is NGSIEM-LAB-0198. The diagnostic packet contains only sanitized source events and an approved before-and-after record. Do not broaden Falcon role permissions to fix an unrelated issue. Which independently observable result BEST demonstrates this particular SIEM engineering issue has been corrected?
Explanation
Correct Answer
Option A is best answer to this acceptance evidence question. The directly observable acceptance result is: A known vendor severity fixture shows both its original rating and justified normalized value. This verifies that Preserve native severity and apply documented mapping with a distinguishable normalized scale addresses the specific observation (A vendor sends a severity integer but SIEM reporting presents it as the exact built-in Falcon severity scale). The technical distinction is: The parser or dashboard conflates vendor-native prioritization with platform-normalized severity.
Incorrect Answers
Option B would verify a separate condition: A SIEM case displays an endpoint-like alert ingested from a network appliance as if Falcon detected it. The observed issue here is: A vendor sends a severity integer but SIEM reporting presents it as the exact built-in Falcon severity scale. The necessary acceptance evidence is: A known vendor severity fixture shows both its original rating and justified normalized value.
Option C would verify a separate condition: A scheduled rule floods analysts with permitted backup service activity after an infrastructure migration. The observed issue here is: A vendor sends a severity integer but SIEM reporting presents it as the exact built-in Falcon severity scale. The necessary acceptance evidence is: A known vendor severity fixture shows both its original rating and justified normalized value.
Option D would verify a separate condition: A custom rule joins endpoint and proxy data but the resulting detection contains no references to contributing records. The observed issue here is: A vendor sends a severity integer but SIEM reporting presents it as the exact built-in Falcon severity scale. The necessary acceptance evidence is: A known vendor severity fixture shows both its original rating and justified normalized value.