Detection rules › Splunk
Logon Script Registry Key added (EDR)
Adversaries may use Windows logon scripts automatically executed at logon initialization to establish persistence.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Persistence | T1037.001 Boot or Logon Initialization Scripts: Logon Script (Windows) |
| Privilege Escalation | T1037.001 Boot or Logon Initialization Scripts: Logon Script (Windows) |
References
Event coverage
| Provider | Event | Title |
|---|---|---|
| Sysmon | Event ID 1 | Process creation |
| Security-Auditing | Event ID 4688 | A new process has been created. |
Rule body yaml
id: '5998.12250'
title: Logon Script Registry Key added
description: 'Adversaries may use Windows logon scripts automatically executed at
logon initialization to establish persistence. '
logic_format: Splunk
logic: ' `get_endpoint_data` `get_endpoint_data_edr` ((event_type IN ("childproc","netconn","proc"))
OR (TERM(ProcessRollup2) OR Type=Process) OR TERM(DeviceProcessEvents)) (TERM(reg)
OR "reg.exe") TERM(add) TERM(UserInitMprLogonScript) | table _time, host, user process,
process_*, singature_id, parent_* | bin span=1s | stats values(*) as * by _time,
host '
techniques:
- persistence:boot or logon initialization scripts:logon script (windows)
- privilege-escalation:boot or logon initialization scripts:logon script (windows)
technique_id:
- T1037.001
data_category:
- Process command-line parameters
- EDR Logs
references:
- https://blog.morphisec.com/cobalt-gang-2.0
Stages and Predicates
Stage 1: search
`get_endpoint_data` `get_endpoint_data_edr` ((event_type IN ("childproc","netconn","proc")) OR (TERM(ProcessRollup2) OR Type=Process) OR TERM(DeviceProcessEvents)) (TERM(reg) OR "reg.exe") TERM(add) TERM(UserInitMprLogonScript)
Stage 2: table
| table _time, host, user process, process_*, singature_id, parent_*
Stage 3: bucket
| bin span=1s
Stage 4: stats
| stats values(*) as * by _time, host
Indicators
Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.
| Field | Kind | Values |
|---|---|---|
event_type | in |
|
Search terms
Bare-string tokens in the SPL search body. Splunk matches each token against _raw (the untyped raw event text) anywhere it appears, not against a specific field. These don't surface in the Indicators table because they aren't predicates on a known field.
| Stage | Term |
|---|---|
| 1 | TERM |
| 1 | ProcessRollup2 |
| 1 | TERM |
| 1 | DeviceProcessEvents |
| 1 | TERM |
| 1 | reg |
| 1 | "reg.exe" |
| 1 | TERM |
| 1 | add |
| 1 | TERM |
| 1 | UserInitMprLogonScript |