Sysmon File Executable Creation Detected
Detects Portable Executable (PE) files creation events logged by Sysmon in paths monitored by the used Sysmon configuration. This is a high-value detection for catching unauthorized or suspicious executable drops. Alert volume and scope depend entirely on which paths or files are monitored in the Sysmon config. A high noise level or hits from known-legitimate software are a strong signal that the Sysmon configuration is too permissive, not that the detection itself is wrong and probably needs to be tuned to a more restrictive set of paths or files.
Detection logic
selection
EventID: 29Condition
selectionRaw YAML
title: Sysmon File Executable Creation Detected
id: 693a44e9-7f26-4cb6-b787-214867672d3a
status: test
description: |
Detects Portable Executable (PE) files creation events logged by Sysmon in paths monitored by the used Sysmon configuration.
This is a high-value detection for catching unauthorized or suspicious executable drops.
Alert volume and scope depend entirely on which paths or files are monitored in the Sysmon config.
A high noise level or hits from known-legitimate software are a strong signal that the Sysmon configuration is too permissive, not that the detection itself is wrong and probably needs to be tuned to a more restrictive set of paths or files.
references:
- https://learn.microsoft.com/en-us/sysinternals/downloads/sysmon
- https://medium.com/@olafhartong/sysmon-15-0-file-executable-detected-40fd64349f36
author: frack113
date: 2023-07-20
tags:
- attack.defense-impairment
logsource:
product: windows
service: sysmon
detection:
selection:
EventID: 29 # this is fine, we want to match any FileExecutableDetected event
condition: selection
falsepositives:
- Legitimate software writing executables to monitored paths - if this occurs, narrow the Sysmon configuration to more sensitive paths rather than suppressing this rule
level: medium
regression_tests_path: regression_data/rules/windows/sysmon/sysmon_file_executable_detected/info.ymlFalse positives
- Legitimate software writing executables to monitored paths - if this occurs, narrow the Sysmon configuration to more sensitive paths rather than suppressing this rule