Beaconing
Periodic outbound check-ins from malware to its command and control server, often detectable by regular timing and consistent size.
Implants rarely hold a connection open; they beacon: wake up, contact the C2 server for tasks, sleep, repeat. The result is a series of connections from one host to one destination with regular intervals and similar byte counts, sometimes over months.
Detection looks for that regularity in flow, proxy or DNS logs: low variance in inter-arrival time, a long-lived pattern to a rare destination, and few distinct destinations per host. Tools such as RITA score this statistically.
Attackers add jitter (random sleep variation) and route through popular cloud services to blend in, while legitimate software (update checkers, telemetry, NTP) beacons too. Baseline and allow-list the known noisy ones before alerting.
Learn it properly
Also used in
- Attacker movement: kill chain and ATT&CKAnalyst · Analyst essentialsFree
- TCP/IP, DNS and HTTP for analystsAnalyst · Networking & logs for analystsFree
- Packet capture basicsAnalyst · Networking & logs for analystsFree
- Malware triage for analystsAnalyst · Investigation & threat huntingPro
- Dynamic and behavioural analysisAnalyst · Malware analysis for respondersPro