:no_entry: 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.

Try in Splunk Security Cloud

Description

This search detects writes to the 'System Volume Information' folder by something other than the System process.

  • Type: Hunting
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2020-07-22
  • Author: Rico Valdez, Splunk
  • ID: cd6297cd-2bdd-4aa1-84aa-5d2f84228fac

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1036 Masquerading Defense Evasion
Kill Chain Phase
  • Exploitation
NIST
  • DE.CM
CIS20
  • CIS 8
CVE
1
2
3
4
5
(`sysmon` OR tag=process) EventCode=11 process_id!=4 file_path=*System\ Volume\ Information* 
| stats count min(_time) as firstTime max(_time) as lastTime by dest, Image, file_path 
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)` 
| `suspicious_writes_to_system_volume_information_filter`

Macros

The SPL above uses the following Macros:

:information_source: suspicious_writes_to_system_volume_information_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • _time

How To Implement

You need to be ingesting logs with both the process name and command-line from your endpoints. If you are using Sysmon, you must have at least version 6.0.4 of the Sysmon TA.

Known False Positives

It is possible that other utilities or system processes may legitimately write to this folder. Investigate and modify the search to include exceptions as appropriate.

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
25.0 50 50 tbd

:information_source: 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: 2