Detection rules › Splunk
Command and Control Detection (Windows Event Log)
Detects malicious (like Github repositories or known suspicious IPs) sources based on a list of IPs and domains
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Command & Control | T1071.001 Application Layer Protocol: Web Protocols, T1095 Non-Application Layer Protocol |
Event coverage
| Provider | Event | Title |
|---|---|---|
| Security-Auditing | Event ID 5156 | The Windows Filtering Platform has permitted a connection. |
Rule body yaml
id: '1043.1069'
title: Command and Control Detection
description: 'Detects malicious (like Github repositories or known suspicious IPs)
sources based on a list of IPs and domains. - Threat Actor Association: APT29/Nobelium/Cozy
Bear, Magic Hound (APT32, Phosphorus, Mint Sandstorm), UNC4990 - Software Association:
Alchimist, Remcos RAT'
logic_format: Splunk
logic: ' `get_endpoint_data` `get_endpoint_data_winevent` (TERM(EventCode=5156) OR
"<EventID>5156<") `fltr_bl_ip_address` | table _time, host, user dest_ip, dest_port,
direction, dvc, dvc_nt_host, event_id, host, index, process_id, process_name, process_path,
signature_id, source, sourcetype, src_ip, src_port, tag, transport, user | bin span=60s
| stats values(*) as * by _time, host `hec_collect`'
techniques:
- command-and-control:application layer protocol:web protocols
- command-and-control:non-application layer protocol
technique_id:
- T1071.001
- T1095
data_category:
- Windows event logs
references: null
Stages and Predicates
Stage 1: search
`get_endpoint_data` `get_endpoint_data_winevent` (TERM(EventCode=5156) OR "<EventID>5156<") `fltr_bl_ip_address`
Stage 2: table
| table _time, host, user dest_ip, dest_port, direction, dvc, dvc_nt_host, event_id, host, index, process_id, process_name, process_path, signature_id, source, sourcetype, src_ip, src_port, tag, transport, user
Stage 3: bucket
| bin span=60s
Stage 4: stats
| stats values(*) as * by _time, host `hec_collect`
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 |
|---|---|---|
EventCode | eq |
|
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 | "<EventID>5156<" |