First time seen command line argument
THIS IS A DEPRECATED DETECTION
This detection has been marked deprecated by the Splunk Threat Research team. This means that it will no longer be maintained or supported.
Description
This search looks for command-line arguments that use a /c
parameter to execute a command that has not previously been seen.
- Type: Hunting
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Endpoint
- Last Updated: 2024-08-15
- Author: Bhavin Patel, Splunk
- ID: a1b6e73f-98d5-470f-99ac-77aacd578473
Annotations
ATT&CK
Kill Chain Phase
- Installation
NIST
- DE.AE
CIS20
- CIS 10
CVE
Search
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
| tstats `security_content_summariesonly` min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name = cmd.exe Processes.process = "* /c *" by Processes.process Processes.process_name Processes.parent_process_name Processes.dest
| `drop_dm_object_name(Processes)`
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| search [
| tstats `security_content_summariesonly` earliest(_time) as firstTime latest(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name = cmd.exe Processes.process = "* /c *" by Processes.process
| `drop_dm_object_name(Processes)`
| inputlookup append=t previously_seen_cmd_line_arguments
| stats min(firstTime) as firstTime, max(lastTime) as lastTime by process
| outputlookup previously_seen_cmd_line_arguments
| eval newCmdLineArgument=if(firstTime >= relative_time(now(), "-70m@m"), 1, 0)
| where newCmdLineArgument=1
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| table process]
| `first_time_seen_command_line_argument_filter`
Macros
The SPL above uses the following Macros:
first_time_seen_command_line_argument_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Lookups
The SPL above uses the following Lookups:
Required fields
List of fields required to use this analytic.
- _time
- Processes.process_name
- Processes.process
- Processes.parent_process_name
- Processes.dest
How To Implement
The detection is based on data that originates from Endpoint Detection and Response (EDR) agents. These agents are designed to provide security-related telemetry from the endpoints where the agent is installed. To implement this search, you must ingest logs that contain the process GUID, process name, and parent process. Additionally, you must ingest complete command-line executions. These logs must be processed using the appropriate Splunk Technology Add-ons that are specific to the EDR product. The logs must also be mapped to the Processes
node of the Endpoint
data model. Use the Splunk Common Information Model (CIM) to normalize the field names and speed up the data modeling process.
Known False Positives
Legitimate programs can also use command-line arguments to execute. Please verify the command-line arguments to check what command/program is being executed. We recommend customizing the first_time_seen_cmd_line_filter
macro to exclude legitimate parent_process_name
Associated Analytic Story
- DHS Report TA18-074A
- Suspicious Command-Line Executions
- Orangeworm Attack Group
- Possible Backdoor Activity Associated With MUDCARP Espionage Campaigns
- Hidden Cobra Malware
RBA
Risk Score | Impact | Confidence | Message |
---|---|---|---|
25.0 | 50 | 50 | tbd |
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
Reference
Test Dataset
Replay any dataset to Splunk Enterprise by using our replay.py
tool or the UI.
Alternatively you can replay a dataset into a Splunk Attack Range
source | version: 6