Detection rules › Splunk

Potential nanodump execution (Windows Event Log)

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

Nanodump is a flexible tool that creates a minidump of the LSASS process and is commonly used by red teams with cobalt strike. This use case looks for nanodumps default access requests.

MITRE ATT&CK coverage

TacticTechniques
Credential AccessT1003 OS Credential Dumping

References

Event coverage

Rule body yaml

id: '19348.33710'
title: Potential nanodump execution
description: Nanodump is a flexible tool that creates a minidump of the LSASS process
  and is commonly used by red teams with cobalt strike. This use case looks for nanodumps
  default access requests.
logic_format: Splunk
logic: '`get_endpoint_data` `get_endpoint_data_winevent` ((TERM(EventCode=4656) OR
  "<EventID>4656<") "0x1010" ) OR ((TERM(EventCode=4663) OR "<EventID>4663<") "%%4484"
  ) "lsass.exe" | table _time, host, user process, process_*, signature_id, parent_*
  | bin span=5s | stats values(*) as * by _time, host | where match(signature_id,
  "4656") and match(signature_id, "4663") '
techniques:
- credential-access:os credential dumping
technique_id: T1003
data_category:
- Windows event logs
references:
- https://github.com/fortra/nanodump

Stages and Predicates

Stage 1: search

`get_endpoint_data` `get_endpoint_data_winevent` ((TERM(EventCode=4656) OR "<EventID>4656<") "0x1010" ) OR ((TERM(EventCode=4663) OR "<EventID>4663<") "%%4484" ) "lsass.exe"

Stage 2: table

| table _time, host, user process, process_*, signature_id, parent_*

Stage 3: bucket

| bin span=5s

Stage 4: stats

| stats values(*) as * by _time, host

Stage 5: where

| where match(signature_id, "4656") and match(signature_id, "4663")

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.

FieldKindValues
EventCodeeq
  • 4656 corpus 19 (splunk 15, kusto 4)
  • 4663 corpus 34 (splunk 29, kusto 5)
signature_idmatch
  • "4656" corpus 3 (splunk 3)
  • "4663" corpus 2 (splunk 2)

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
1TERM
1"<EventID>4656<"
1"0x1010"
1TERM
1"<EventID>4663<"
1"%%4484"
1"lsass.exe"