Analyzing Command And Control Communication
Overview
Cybersecurity skill for analyzing command and control communication. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"analyzing command and control communication"
"Analyzes malware command-and-control (C2) communication protocols to understand "
Reverse engineering a malware sample has revealed network communication that needs protocol analysis
Building network-level detection signatures for a specific C2 framework (Cobalt Strike, Metasploit, Sliver)
Mapping C2 infrastructure including primary servers, fallback domains, and dead drops
Analyzing encrypted or encoded C2 traffic to understand the command set and data format
Attributing malware to a threat actor based on C2 infrastructure patterns and tooling
Do not use for general network anomaly detection; this is specifically for understanding known or suspected C2 protocols from malware analysis.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- PCAP capture of malware network traffic (from sandbox, network tap, or full packet capture)
- Wireshark/tshark for packet-level analysis
- Reverse engineering tools (Ghidra, dnSpy) for understanding C2 code in the malware binary
- Python 3.8+ with
scapy, dpkt, and requests for protocol analysis and replay
- Threat intelligence databases for C2 infrastructure correlation (VirusTotal, Shodan, Censys)
- JA3/JA3S fingerprint databases for TLS-based C2 identification
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Scope the Analysis — Define what command and control communication artifacts or data sources to examine and the investigation timeline.
- Preserve Evidence — Create forensic copies of relevant data. Maintain chain of custody documentation.
- Extract Key Indicators — Parse and extract relevant command and control communication data points from collected artifacts.
- Correlate Findings — Cross-reference extracted data with other sources (threat intel, logs, timelines).
- Build Timeline — Construct a chronological sequence of events related to command and control communication.
- Document Analysis — Write findings report with evidence, conclusions, and recommendations.
Tools
- Forensic Toolkit — Evidence collection and analysis
- Timeline Tools — Chronological event reconstruction
- Log Analysis Platform — Centralized log parsing and search
Process
- Scope — Define research questions, identify data sources, set time boundaries
- Gather — Collect data from primary sources, APIs, and public records
- Synthesize — Analyze findings, identify patterns, produce actionable report
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: analyzing-command-and-control-communication3description: Use when analyzing malware command-and-control (C2) communication protocols4 to understand beacon patterns, command structures, data encoding, and infrastructure.5 Covers HTTP, HTTPS, DNS, and custom protocol C2 analysis for detection development6 and threat intelligence. Activates for requests involving C2 analysis, beacon detection,7 C2 protocol reverse engineering, or command-and-control infrastructure mapping.8domain: cybersecurity9tags:10- malware11- C212- command-and-control13- beacon14- protocol-analysis15subdomain: malware-analysis16version: 1.0.017author: oyi7718license: Apache-2.019nist_csf:20- DE.AE-0221- RS.AN-0322- ID.RA-0123- DE.CM-0124category: cybersecurity25metadata:26 source: https://skillmd.com/skills/oyi77/analyzing-command-and-control-communication27---2829# Analyzing Command And Control Communication3031## Overview3233Cybersecurity skill for analyzing command and control communication. Follows industry best practices and security standards.3435## When to Use36**Trigger phrases:**37- "analyzing command and control communication"38- "Analyzes malware command-and-control (C2) communication protocols to understand "394041- Reverse engineering a malware sample has revealed network communication that needs protocol analysis42- Building network-level detection signatures for a specific C2 framework (Cobalt Strike, Metasploit, Sliver)43- Mapping C2 infrastructure including primary servers, fallback domains, and dead drops44- Analyzing encrypted or encoded C2 traffic to understand the command set and data format45- Attributing malware to a threat actor based on C2 infrastructure patterns and tooling4647**Do not use** for general network anomaly detection; this is specifically for understanding known or suspected C2 protocols from malware analysis.484950## When NOT to Use5152- When you lack proper authorization for testing53- For production systems without change management54- When the task requires legal or compliance expertise beyond technical scope555657## Prerequisites5859- PCAP capture of malware network traffic (from sandbox, network tap, or full packet capture)60- Wireshark/tshark for packet-level analysis61- Reverse engineering tools (Ghidra, dnSpy) for understanding C2 code in the malware binary62- Python 3.8+ with `scapy`, `dpkt`, and `requests` for protocol analysis and replay63- Threat intelligence databases for C2 infrastructure correlation (VirusTotal, Shodan, Censys)64- JA3/JA3S fingerprint databases for TLS-based C2 identification6566## Workflow6768```python69# Example: IOC detection70import re7172IOC_PATTERNS = {73 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",74 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",75 "hash_md5": r"\b[a-f0-9]{32}\b",76 "hash_sha256": r"\b[a-f0-9]{64}\b",77}7879def extract_iocs(text: str) -> dict:80 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}81```82831. **Scope the Analysis** — Define what command and control communication artifacts or data sources to examine and the investigation timeline.842. **Preserve Evidence** — Create forensic copies of relevant data. Maintain chain of custody documentation.853. **Extract Key Indicators** — Parse and extract relevant command and control communication data points from collected artifacts.864. **Correlate Findings** — Cross-reference extracted data with other sources (threat intel, logs, timelines).875. **Build Timeline** — Construct a chronological sequence of events related to command and control communication.886. **Document Analysis** — Write findings report with evidence, conclusions, and recommendations.8990## Tools9192- **Forensic Toolkit** — Evidence collection and analysis93- **Timeline Tools** — Chronological event reconstruction94- **Log Analysis Platform** — Centralized log parsing and search959697## Process98991. **Scope** — Define research questions, identify data sources, set time boundaries1001. **Gather** — Collect data from primary sources, APIs, and public records1011. **Synthesize** — Analyze findings, identify patterns, produce actionable report102103## Verification104105- [ ] All command and control communication procedures executed completely and documented106- [ ] Findings validated against multiple data sources107- [ ] False positives identified and filtered108- [ ] Results documented with evidence and timestamps109- [ ] Recommendations provided with risk-based prioritization110111## Anti-Rationalization Table112113| Rationalization | Reality |114|---|---|115| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |116| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |117| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |