Detection rules › Splunk
Windows .Key File Creation in Root Directory
Detects the creation of a .key file in the root directory of the system drive. This activity was seen with various ransomware before performing encryption of files.
Known false positives
- False positives may occur if legitimate software or administrative tools create key files in the root directory, although this is uncommon in normal operations. Filter alerts based on known approved applications.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Impact |
Telemetry coverage
| Provider | Record / event type |
|---|---|
| Sysmon | Event ID 11: FileCreate |
Rule body
name: Windows .Key File Creation in Root Directory
id: 90e71722-8c0f-43b4-937a-6222325976c2
version: 2
creation_date: '2021-09-02'
modification_date: '2026-05-13'
author: Raven Tait, Splunk
status: production
type: Anomaly
description: |-
Detects the creation of a .key file in the root directory of the system drive.
This activity was seen with various ransomware before performing encryption of files.
data_source:
- Sysmon EventID 11
search: |-
| tstats `security_content_summariesonly`
count min(_time) as firstTime
max(_time) as lastTime
from datamodel=Endpoint.Filesystem where
Filesystem.file_name="*.key"
by Filesystem.dest Filesystem.file_create_time
Filesystem.process_path Filesystem.process_guid
Filesystem.process_id Filesystem.file_path
Filesystem.action Filesystem.file_name
Filesystem.user Filesystem.vendor_product
| `drop_dm_object_name(Filesystem)`
| where match(file_path, "^[A-Za-z]:\\\\[^\\\\]+\.key$")
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| `windows__key_file_creation_in_root_directory_filter`
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: False positives may occur if legitimate software or administrative tools create key files in the root directory, although this is uncommon in normal operations. Filter alerts based on known approved applications.
references:
- https://www.cisa.gov/uscert/ncas/alerts/aa22-321a
intermediate_findings:
entities:
- field: dest
type: system
score: 20
message: .key file created in the root of the system drive at $file_path$ on $dest$.
threat_objects:
- field: file_path
type: file_path
analytic_story:
- Ransomware
asset_type: Endpoint
mitre_attack_id:
- T1486
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
category: endpoint
security_domain: endpoint
Stages and Predicates
Stage 1: tstats
| tstats `security_content_summariesonly`
count min(_time) as firstTime
max(_time) as lastTime
from datamodel=Endpoint.Filesystem where
Filesystem.file_name="*.key"
by Filesystem.dest Filesystem.file_create_time
Filesystem.process_path Filesystem.process_guid
Filesystem.process_id Filesystem.file_path
Filesystem.action Filesystem.file_name
Filesystem.user Filesystem.vendor_product
Stage 2: search
| `drop_dm_object_name(Filesystem)`
Stage 3: where
| where match(file_path, "^[A-Za-z]:\\\\[^\\\\]+\.key$")
Stage 4: search
| `security_content_ctime(firstTime)`
Stage 5: search
| `security_content_ctime(lastTime)`
Stage 6: search
| `windows__key_file_creation_in_root_directory_filter`
Indicators
These rows show field, operator, and value matches.
| Field | Kind | Values | Search |
|---|---|---|---|
Filesystem.file_name | eq |
| field:"file_name" kind:eq |
file_path | regex_match |
| field:"TargetFilename" kind:regex_match |