Potential Ping Sweep (Windows Event Log)

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

Adversaries may attempt to get a listing of other systems by IP address, hostname, or other logical identifier on a network that may be used for Lateral Movement from the current system

MITRE ATT&CK coverage

Tactic	Techniques
Discovery	`T1018` Remote System Discovery

References

https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1018/T1018.md#atomic-test-4---remote-system-discovery---ping-sweep

Telemetry coverage

Provider	Record / event type
Security-Auditing	Event ID 4688: A new process has been created.

Rule body

id: '8506.10723'
title: Potential Ping Sweep
description: 'Adversaries may attempt to get a listing of other systems by IP address,
  hostname, or other logical identifier on a network that may be used for Lateral
  Movement from the current system. - Threat Actor Association: UNC2596 - Software
  Association: Cuba, Hive - Atomics T1018 Test #4 Atomics T1018 Test #7'
logic_format: Splunk
logic: '`get_endpoint_data` `get_endpoint_data_winevent` (TERM(EventCode=4688) OR
  "<EventID>4688<" OR Type=Process) "ping.exe" | table _time, host, user, signature_id,
  process, process_*, parent_process_* | bin span=60s | stats values(*) as * by _time,
  host | eventstats dc(process) as c_proc by host, _time| where c_proc > 30 AND match(process_name,
  "(?i)ping") '
techniques:
- discovery:remote system discovery
technique_id: 
- T1018
data_category:
- Windows event logs
- Process command-line parameters
references:
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1018/T1018.md#atomic-test-4---remote-system-discovery---ping-sweep

Stages and Predicates

Stage 1: `search`

`get_endpoint_data` `get_endpoint_data_winevent` (TERM(EventCode=4688) OR "<EventID>4688<" OR Type=Process) "ping.exe"

Stage 2: `table`

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

Stage 3: `bucket`

| bin span=60s

Stage 4: `stats`

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

Stage 5: `eventstats`

| eventstats dc(process) as c_proc by host, _time

Stage 6: `where`

| where c_proc > 30 AND match(process_name, "(?i)ping")

Indicators

These rows show field, operator, and value matches.

Field	Kind	Values	Search
`EventCode`	eq	`4688` corpus 317 (splunk 283, kusto 33, elastic 1)	`field:"EventID" kind:eq value:"4688"`
`c_proc`	gt	`30`	`field:"c_proc" kind:gt value:"30"`
`process_name`	regex_match	`"(?i)ping"`	`field:"process_name" kind:regex_match`

Search terms

These SPL tokens match against raw event text.

Stage	Term
1	`"<EventID>4688<"`
1	`"ping.exe"`