Suspicious AppLocker Application Would Have Been Blocked (via applocker)

title: Suspicious AppLocker Application Would Have Been Blocked (via applocker)
id: 3d6ef24d-d8b9-5da6-be61-01b05c06d0aa
status: stable
description: This rule detects when AppLocker "Audit only" enforcement mode reports that an Application, DLL, Script, MSI, or Packaged-App would have been blocked if AppLocker "Enforce rules" enforcement mode was enabled.
references:
    - https://attack.mitre.org/techniques/T1059/007/
    - https://attack.mitre.org/techniques/T1059/006/
    - https://attack.mitre.org/techniques/T1059/005/
    - https://attack.mitre.org/techniques/T1059/003/
    - https://attack.mitre.org/techniques/T1059/001/
    - https://attack.mitre.org/techniques/T1204/002/
    - https://learn.microsoft.com/en-us/windows/security/application-security/application-control/windows-defender-application-control/applocker/what-is-applocker
    - https://learn.microsoft.com/en-us/windows/security/application-security/application-control/windows-defender-application-control/applocker/using-event-viewer-with-applocker
    - https://www.splunk.com/en_us/blog/security/deploy-test-monitor-mastering-microsoft-applocker-part-2.html
    - https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/ee844150(v=ws.11)
author: Huntrule Team
date: 2026-07-18
tags:
    - attack.execution
    - attack.t1204.002
    - attack.t1059.001
    - attack.t1059.003
    - attack.t1059.005
    - attack.t1059.006
    - attack.t1059.007
logsource:
    product: windows
    service: applocker
detection:
    selection:
        EventID:
            - 8003
            - 8006
            - 8021
            - 8024
    condition: selection
falsepositives:
    - Unknown
level: medium