Refer to the exhibit. The exhibit shows an alert from Microsoft Defender XDR. The security team needs to determine if the file 'invoice.docm' is known malware and if other devices in the organization have this file. What should they do next?
Searching for the file's SHA256 hash in Advanced Hunting is the most effective immediate next step because it allows security analysts to quickly determine the prevalence of the malicious file across the entire organizational environment. Using this unique cryptographic identifier ensures an accurate and comprehensive search, revealing if other endpoints have encountered or executed the same file. This crucial information is essential for understanding the scope of the compromise and prioritizing subsequent containment and eradication efforts.
Why this answer
Searching for the file's SHA256 hash in Advanced Hunting allows the security team to query across all devices in the organization to determine if the file is known malware (by cross-referencing with threat intelligence) and to identify which other devices have the same file. Advanced Hunting in Microsoft Defender XDR supports Kusto Query Language (KQL) queries against the DeviceFileEvents table, enabling hash-based file discovery and reputation checks.
Exam trap
The trap here is that candidates may choose 'Trigger the automated investigation' thinking it will automatically determine malware status and scope, but automated investigation focuses on response actions rather than providing the specific hash-based query results needed to answer both questions.
How to eliminate wrong answers
Option A is wrong because isolating the device prematurely could disrupt business operations and does not answer whether the file is known malware or if other devices have it. Option B is wrong because triggering an automated investigation would start response actions based on the alert, but it does not directly provide the specific information about the file's malware status or its presence on other devices. Option C is wrong because reviewing user jdoe's recent activities focuses on user behavior rather than the file's hash-based identification and propagation across devices.