hunting-for-beaconing-with-frequency-analysis

Featured

Identify command-and-control beaconing patterns in network traffic by applying statistical frequency analysis, jitter calculation, and coefficient of variation scoring to detect periodic callbacks from compromised endpoints.

AI & Automation 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Hunting for Beaconing with Frequency Analysis ## When to Use - When proactively searching for compromised endpoints calling back to C2 infrastructure - After threat intelligence reports indicate active C2 frameworks targeting your sector - When network logs show periodic outbound connections to unfamiliar destinations - During purple team exercises validating C2 detection capabilities - When investigating a potential breach and need to identify active C2 channels ## Prerequisites - Network proxy/firewall logs with timestamps and destination data (minimum 24 hours) - Zeek conn.log, dns.log, and ssl.log or equivalent NetFlow/IPFIX data - SIEM platform with statistical analysis capability (Splunk, Elastic, Microsoft Sentinel) - RITA (Real Intelligence Threat Analytics) or AC-Hunter for automated beacon analysis - Threat intelligence feeds for domain/IP reputation enrichment ## Workflow 1. **Define Beacon Parameters**: Establish detection thresholds -- coefficient of variation (CV) below 0.20 indicates strong periodicity, minimum 50 connections over 24 hours, average interval between 30 seconds and 24 hours. 2. **Collect Network Telemetry**: Aggregate proxy logs, DNS queries, firewall connection logs, and Zeek metadata into the analysis platform. 3. **Calculate Connection Intervals**: For each source-destination pair, compute the time delta between consecutive connections and derive mean interval, standard deviation, and CV. 4. **Apply Jitter Analysis**: Sophisticated C2 ...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

hunting-for-command-and-control-beaconing

Detect C2 beaconing patterns in network traffic using frequency analysis, jitter detection, and domain reputation to identify compromised endpoints communicating with adversary infrastructure.

36,355 Updated 2 months ago
mukul975
AI & Automation Listed

detect-c2-beaconing

Detection and hunt methodology for command-and-control beaconing, where an implant calls home on a regular interval over HTTP(S), DNS, or a tunnel service, hidden inside normal egress (MITRE ATT&CK T1071 Application Layer Protocol, T1071.004 DNS, T1573 Encrypted Channel, T1571 Non-Standard Port, T1572 Protocol Tunneling, T1090 Proxy; tactic TA0011 Command and Control). Works from Zeek conn.log/ssl.log/dns.log, Suricata EVE JSON, firewall and web-proxy logs, NetFlow/IPFIX, and endpoint Sysmon Event ID 3/22. It gives the defender's view of beacon periodicity and jitter, JA3/JA3S and JA4 TLS fingerprinting, and tunnel-service detection, plus hunt steps and hardening. Use when hunting for regular callbacks, triaging a long-lived outbound connection, analyzing JA3/JA4 hashes, investigating suspected Cobalt Strike, Sliver, or Mythic C2, chasing DNS or HTTPS tunneling, or baselining egress for periodic traffic.

0 Updated 5 days ago
umbrasec-labs
AI & Automation Listed

detecting-beaconing-patterns-with-zeek

Performs statistical analysis of Zeek conn.log connection intervals to detect C2 beaconing patterns. Uses the ZAT library to load Zeek logs into Pandas DataFrames, calculates inter-arrival time standard deviation, and flags periodic connections with low jitter. Use when hunting for command-and-control callbacks in network data.

100 Updated 2 weeks ago
adriannoes