Files
splunk-security_content/detections/unusually_long_command_line.yml
2020-04-29 13:01:45 +02:00

36 lines
1.6 KiB
YAML

name: Unusually Long Command Line
id: c77162d3-f93c-45cc-80c8-22f6a4264e7f
version: '4.0'
date: '2020-03-16'
description: Command lines that are extremely long may be indicative of malicious
activity on your hosts.
how_to_implement: You must be ingesting endpoint data that tracks process activity,
including parent-child relationships, from your endpoints to populate the Endpoint
data model in the Processes node. The command-line arguments are mapped to the "process"
field in the Endpoint data model.
type: ESCU
references: []
author: David Dorsey, Splunk
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time)
as lastTime FROM datamodel=Endpoint.Processes by Processes.user Processes.dest Processes.process_name
Processes.process | `drop_dm_object_name("Processes")` | `security_content_ctime(firstTime)`|
`security_content_ctime(lastTime)`| eval processlen=len(process) | eventstats stdev(processlen)
as stdev, avg(processlen) as avg by dest | stats max(processlen) as maxlen, values(stdev)
as stdevperhost, values(avg) as avgperhost by dest, user, process_name, process|
`unusually_long_commandlines_filter`| eval threshold = 10 | where maxlen > ((threshold*stdevperhost)
+ avgperhost)'
known_false_positives: Some legitimate applications start with long command lines.
tags:
analytics_story:
- Possible Backdoor Activity Associated With MUDCARP Espionage Campaigns
- Ransomware
- Unusual Processes
- Suspicious Command-Line Executions
kill_chain_phases:
- Actions on Objectives
cis20:
- CIS 8
nist:
- PR.PT
- DE.CM