A transit SOC analyst has a rare destination domain and a file hash from last night's parking-meter malware. What is the right way to see whether those values appear on the ISAC indicator list already loaded as a lookup?
Select an answer to reveal the explanation.
Short Explanation
An ISAC list is just a lookup table wearing a threat-intel badge. Pipe dest and file_hash into lookup and Splunk stamps a match if last night's parking-meter indicators are on the list. Grouping a day's traffic or rewriting the URL does not magically consult that table.
Full Explanation
Technical indicators such as domains and hashes are matched in analysis with lookup against a threat-intel table. For a transit parking-meter sample, looking up dest and file_hash attaches ISAC match fields when those IoCs are present. rex does not query intel. transaction does not classify malice by time span, and replacing live events with makeresults skips the actual telemetry that needs matching.