Detections

Explore public detection logic contributed by the community across SIEM and rule languages.

25 detections

These queries check telemetry from the Exploit Guard rule: Rule: Block Office applications from creating child processes.
(Rule ID d4f940ab-401b-4efc-aadc-ad5f3c50688a).
Read more about it here: https://docs.microsoft.com/windows/security/threat-protection/windows-defender-exploit-guard/attack-surface-reduction-exploit-guard.
Oftentimes organizations enable this rule in audit mode and check the results before setting block mode.
You can use query #2 to measure the rule impact on your network in audit mode before turning it to block mode.
Query #1 is used after setting it to block mode - to analyze the block stats.
Tags: #ASR.
Query #1: block stats.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
009
Detects the addition of the 'Office test' registry key, specifically the 'Special\Perf' subkey, which allows an arbitrary DLL to be executed every time an Office application is started. This method is used for persistence.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0015
Detects suspicious child processes spawning from microsoft office suite applications such as word or excel. This could indicates malicious macro execution
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
000
Detects the addition of office test registry that allows a user to specify an arbitrary DLL that will be executed every time an Office application is started
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
000
Page 2 of 2