System Processes Run From Unexpected Locations
This search looks for system processes that typically execute from
C:\Windows\SysWOW64. This may indicate a malicious process that is trying to hide as a legitimate process.
This detection utilizes a lookup that is deduped
syswow64 directories from Server 2016 and Windows 10.
During triage, review the parallel processes - what process moved the native Windows binary? identify any artifacts on disk and review. If a remote destination is contacted, what is the reputation?
- Type: Anomaly
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Endpoint
- Last Updated: 2020-12-08
- Author: David Dorsey, Michael Haag, Splunk
- ID: a34aae96-ccf8-4aef-952c-3ea21444444d
Kill Chain Phase
- Actions on Objectives
- CIS 8
1 2 3 4 5 6 7 | tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime FROM datamodel=Endpoint.Processes where Processes.process_path !="C:\\Windows\\System32*" Processes.process_path !="C:\\Windows\\SysWOW64*" by Processes.dest Processes.user Processes.parent_process Processes.process_name Processes.process Processes.process_id Processes.parent_process_id Processes.process_hash | `drop_dm_object_name("Processes")` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `is_windows_system_file` | `system_processes_run_from_unexpected_locations_filter`
The SPL above uses the following Macros:
system_processes_run_from_unexpected_locations_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Supported Add-on (TA)
List of Splunk Add-on’s tested to work with the analytic.
List of fields required to use this analytic.
How To Implement
To successfully implement this search you need to be ingesting information on process that include the name of the process responsible for the changes from your endpoints into the
Endpoint datamodel in the
Known False Positives
This detection may require tuning based on third party applications utilizing native Windows binaries in non-standard paths.
Associated Analytic Story
- Suspicious Command-Line Executions
- Unusual Processes
- Masquerading - Rename System Utilities
|30.0||60||50||A System process $process_name$ is running from $process_path$ on $dest$, potentially non-standard.|
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
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