Skip to content

Command and Control

github-actions[bot] edited this page Nov 19, 2026 · 2 revisions

C2 channel techniques and covert communication methods for red team infrastructure, organized by protocol/channel. Most items link to a specific pentestlab.blog write-up. C2-005, C2-010, C2-011, and C2-020 have no dedicated article, so they link to the general pentestlab.blog Command & Control category (โ˜… general reference).

Purpose: A survey of covert communication channels an implant can use to phone home once execution is achieved, organized by carrier protocol/service rather than by C2 framework. Where Tradecraft/c2-frameworks.md covers which tool to run (Cobalt Strike, Sliver, Havoc), this checklist covers which channel the traffic rides on - DNS, HTTPS, WebDAV, cloud storage APIs, social media, even images and JavaScript as a transport.

Function: Each item represents a different way to blend outbound C2 traffic into normal network noise: DNS and ICMP exploit protocols that are rarely fully inspected; Gmail/DropBox/GitHub/Twitter exploit the fact that traffic to major SaaS platforms is almost never blocked at a corporate firewall; WebSocket, images, and JavaScript exploit the fact that web traffic inspection tools often don't parse payloads embedded in those formats.

Goal: Determine which covert channels a target's network defenses (firewall egress rules, DNS filtering, TLS inspection, DLP) actually catch versus which ones pass through undetected - this is a detection-evasion assessment as much as an offensive one. For blue teams, this same list doubles as a coverage map: for each channel, "do we have a detection for this" is a fair question to ask.

When & how to use this: Use during red team engagements after initial access, when establishing a resilient C2 channel is the next objective - test the most "boring"/high-blend-in channels first (HTTPS, DNS) before escalating to more unusual ones (Instagram, images) that are more likely to be a research curiosity than a production-viable channel. For blue/purple teams, use this as a checklist of channels to validate detection coverage against, ideally paired with the Sigma/detection content in Tradecraft/c2-frameworks.md.

๐Ÿ“– Full Deep-dives (Cobalt Strike, etc; Architecture, Detection, etc): Tradecraft/c2-frameworks.md



๐Ÿ“– Use These Checklists Responsibly: Authorization is MANDATORY

Attack techniques are powerful - use them ethically and legally.

Repository: ULTIMATE CYBERSECURITY MASTER GUIDE

Maintained by: Pacific Northwest Computers


โš ๏ธ Authorized testing only: confirm authority and scope before active testing. โš ๏ธ

โš ๏ธ Legal consequences depend on the conduct and applicable law; see 18 U.S.C. ยง1030 and DOJ CFAA charging policy. โš ๏ธ

โš ๏ธ For systems you do not own or administer, confirm authorization in advance and document scope in writing where policy, law, or contract requires it. โš ๏ธ

โญ Star this repo if you find it useful! โญ

## Related Files - [README.md](https://github.com/Pnwcomputers/ULTIMATE-CYBERSECURITY-MASTER-GUIDE/wiki/Checklists) - Checklists section index

๐Ÿ“„ Source: Checklists/command-and-control.md | โœ๏ธ Suggest an edit | โฌ…๏ธ Back to Checklists

Clone this wiki locally