Lab Demonstrates How Network Monitoring Can Reveal C2 Beacons
· 1:01:24 · Watch on YouTube ↗
Summary
A red-team lab demonstrates how firewall sessions, network-flow alerts and proxy logs can reveal beacon traffic and staged payloads, while discussing visibility gaps and evasion tradeoffs.
Key points
- The presenter uses a virtual pfSense network and test beacons to examine network visibility rather than endpoint protection.
- pfTop showed persistent connections to the test C2 host, including a session that remained established despite a 10-second beacon sleep interval.
- Ntopng exposed multiple hosts communicating with the same destination and flagged a self-signed TLS certificate.
- The presenter correlated firewall sessions, Zeke logs and Ntopng alerts to identify the lab beacons.
- A Squid-connected host blocked a staged HTTPS payload on port 444, while a host not using the proxy established a session.
- The presenter discusses how redirectors, customized certificates and alternative staging methods could change the signals available to defenders.
Article Details
- Topics
- [00:09] Virtual lab topology and pfSense firewall
- [04:42] Network monitoring packages and proxy visibility
- [10:13] Beacon traffic and persistent firewall sessions
- [18:02] Ntopng flow analysis and C2 redirector tradeoffs
- [31:19] TLS certificate alerts and beacon session duration
- [38:19] Correlating Zeke logs with network alerts
- [44:02] Squid proxy configuration and request logging
- [51:08] Staged payload detection and proxy port filtering
- [58:16] Staging choices and environment-specific testing
