Detection rules › Splunk

Logon Script Registry Key added (Sysmon)

Group by
_time, host
Source
github.com/anvilogic-forge/armory

Adversaries may use Windows logon scripts automatically executed at logon initialization to establish persistence.

MITRE ATT&CK coverage

References

Event coverage

Rule body yaml

id: '5998.18216'
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_sysmon` (("EventCode=12" OR "<EventID>12<"
  OR "EventCode=13" OR "<EventID>13<") OR ("EventCode=1" OR "<EventID>1<" OR (TERM(reg)
  OR "reg.exe"))) "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:
- Windows Sysmon
references:
- https://blog.morphisec.com/cobalt-gang-2.0

Stages and Predicates

Stage 1: search

`get_endpoint_data` `get_endpoint_data_sysmon` (("EventCode=12" OR "<EventID>12<" OR "EventCode=13" OR "<EventID>13<") OR ("EventCode=1" OR "<EventID>1<" OR (TERM(reg) OR "reg.exe"))) "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

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.

StageTerm
1"EventCode=12"
1"<EventID>12<"
1"EventCode=13"
1"<EventID>13<"
1"EventCode=1"
1"<EventID>1<"
1TERM
1reg
1"reg.exe"
1"UserInitMprLogonScript"