A newer version is available. For the latest information, see the
current release documentation.
Suspicious Execution - Short Program Name
editSuspicious Execution - Short Program Name
editIdentifies process execution with a single character process name. This is often done by adversaries while staging or executing temporary utilities.
Rule type: eql
Rule indices:
- winlogbeat-*
- logs-endpoint.events.*
- logs-windows.*
Severity: medium
Risk score: 47
Runs every: 5m
Searches indices from: now-9m (Date Math format, see also Additional look-back time)
Maximum alerts per execution: 100
References: None
Tags:
- Elastic
- Host
- Windows
- Threat Detection
- Execution
Version: 4
Rule authors:
- Elastic
Rule license: Elastic License v2
Investigation guide
edit## Config If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2, events will not define `event.ingested` and default fallback for EQL rules was not added until 8.2, so you will need to add a custom pipeline to populate `event.ingested` to @timestamp for this rule to work.
Rule query
editprocess where event.type in ("start", "process_started") and length(process.name) > 0 and
length(process.name) == 5 and host.os.name == "Windows" and length(process.pe.original_file_name) > 5