hunting-for-command-and-control-beaconing

name	hunting-for-command-and-control-beaconing
description	Detect C2 beaconing patterns in network traffic using frequency analysis, jitter detection, and domain reputation to identify compromised endpoints communicating with adversary infrastructure.
domain	cybersecurity
subdomain	threat-hunting
tags	["threat-hunting","mitre-attack","c2","beaconing","network-analysis","proactive-detection"]
version	1.0
author	mahipal
license	Apache-2.0
d3fend_techniques	["File Metadata Consistency Validation","Certificate Analysis","Application Protocol Command Analysis","Content Format Conversion","File Content Analysis"]
nist_csf	["DE.CM-01","DE.AE-02","DE.AE-07","ID.RA-05"]

Hunting for Command and Control Beaconing

When to Use

• When proactively hunting for compromised systems in the network
• After threat intel indicates C2 frameworks targeting your industry
• When investigating periodic outbound connections to suspicious domains
• During incident response to identify active C2 channels
• When DNS query logs show unusual patterns to specific domains

Detection Gaps & Validation

• Jitter and long sleep break naive frequency rules: interval + 0–50% jitter (Cobalt Strike) and multi-hour sleeps drop the connection count and inflate CV — score on bytes-out consistency and use autocorrelation over a 7–14 day window, not a single-day CV < 0.2.
• Encrypted/allowlisted channels: TLS (T1573), domain fronting, and C2 over Slack/Discord/Telegram/Graph API ride trusted FQDNs — destination reputation alone misses them; pivot to JA3/JA4 (use Zeek ssl.log/Suricata, since Sysmon EID 3 lacks it) and timing.
• DNS C2 (T1071.004): TXT/CNAME tunneling needs DNS query logs (Sysmon EID 22 or resolver logs) plus entropy/volume analysis — invisible if DNS logging is off or only NXDOMAIN is retained.
• Log fidelity: sampled NetFlow or aggregated proxy logs destroy inter-arrival timing — confirm per-connection records.
• Validate: run Atomic Red Team T1071.001/T1071.004 (or a Sliver test profile) with a known interval and confirm the beacon search and DNS-entropy search fire, then map source IP to host via Sysmon EID 1/3.
• Tune FPs: Windows Update, AV, NTP, telemetry, and CDN health checks are periodic by design — allowlist by destination + process, never by interval alone.

Prerequisites

• Network proxy/firewall logs with full URL and timing data
• DNS query logs (passive DNS, DNS server logs, or Sysmon Event ID 22)
• Zeek/Bro network connection logs or NetFlow data
• SIEM with statistical analysis capabilities (Splunk, Elastic)
• Threat intelligence feeds for domain/IP reputation

Workflow

1. Identify Beaconing Characteristics: Define what constitutes beaconing (regular intervals, small payload sizes, consistent destinations, jitter patterns).
2. Collect Network Telemetry: Aggregate proxy logs, DNS queries, and connection metadata for analysis.
3. Apply Frequency Analysis: Identify connections with regular intervals using statistical methods (standard deviation, coefficient of variation).