Files
splunk-security_content/detections/samsam_test_file_write.yml
2020-05-06 17:42:38 +02:00

32 lines
1.3 KiB
YAML

name: Samsam Test File Write
id: 69c12d59-d951-431e-ab77-ec426b8d65e6
version: 1
date: '2018-12-14'
description: The search looks for a file named "test.txt" written to the windows system
directory tree, which is consistent with Samsam propagation.
how_to_implement: You must be ingesting data that records the file-system activity
from your hosts to populate the Endpoint file-system data-model node. If you are
using Sysmon, you will need a Splunk Universal Forwarder on each endpoint from which
you want to collect data.
type: ESCU
references: []
author: Rico Valdez, Splunk
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time)
as lastTime values(Filesystem.user) as user values(Filesystem.dest) as dest values(Filesystem.file_name)
as file_name from datamodel=Endpoint.Filesystem where Filesystem.file_path=*\\windows\\system32\\test.txt
by Filesystem.file_path | `drop_dm_object_name(Filesystem)` | `security_content_ctime(lastTime)`
| `security_content_ctime(firstTime)` | `samsam_test_file_write_filter`'
known_false_positives: No false positives have been identified.
tags:
analytics_story:
- SamSam Ransomware
kill_chain_phases:
- Delivery
cis20:
- CIS 8
nist:
- PR.PT
- DE.CM
security_domain: endpoint
asset_type: Endpoint