Skip to content
StrikeCyberStrikeCyber
Field Manual · Attack technique

Command and Control (C2)

Reviewed 14 November 2026Attack technique 2 min read

Quick answer

Command and control (C2) is how an attacker keeps remote control of systems they have compromised: malware or an implant on the device checks in with the attacker's server for instructions and sends data back. C2 traffic is disguised as normal web traffic, and spotting it is one of the best chances to stop an intrusion early.

On this page

Getting into a network is only the start. To steal data, move laterally or deploy ransomware, an attacker needs a reliable way to keep issuing commands. That channel is command and control, and it is often the most visible part of an intrusion if you know what to look for.

01

How It Works

An implant on the compromised device connects out to infrastructure the attacker controls, receives tasks (run a command, upload a file, move to another host) and returns results. Outbound connections are used because firewalls usually allow them. To blend in, attackers use common protocols and trusted services.

ChannelHow it hides
HTTPSLooks like ordinary browsing; often fronted by content delivery networks
DNSData encoded in DNS queries, which most networks allow freely
Cloud servicesCommands passed through legitimate platforms such as cloud storage, chat or developer sites
SMB and named pipesImplants inside the network relay through one host, so only one device talks out
Remote access toolsLegitimate remote support software installed by the attacker
02

Why It Matters

Every hour of undetected C2 gives an attacker more time to find valuable data and escalate. Ransomware operators often spend days or weeks with C2 in place before encrypting. Organisations that monitor outbound traffic and endpoint behaviour can catch an intrusion at this stage, long before the damage.

03

How to Test for It

  1. Review egress controls: which devices can reach the internet directly, and through which ports and services.
  2. Check whether DNS, proxy and firewall logs are collected and searchable.
  3. Run controlled C2 from representative devices over several channels (HTTPS, DNS, cloud services) and record what was blocked or alerted.
  4. Test whether analysts investigate and contain the device, and how quickly.
04

How to Reduce the Risk

Force internet traffic through a proxy with TLS inspection where appropriate, restrict direct outbound access from servers, monitor DNS for tunnelling and newly registered domains, block unapproved remote access tools, and use EDR and network detection to spot beaconing. A red team engagement tests these controls with realistic C2 rather than assuming they work.

05

Regulatory and Framework Context

For Australian organisations, ASD's Information Security Manual includes controls on gateway and egress filtering and on network monitoring, and command and control detection features in ASD's threat detection guidance. MITRE ATT&CK catalogues C2 techniques under its Command and Control tactic.

Latest intel on this topic

Updated hourly from the daily briefing.

Common questions

What is a C2 server?

The attacker's server that compromised devices connect to for instructions. It is often hidden behind redirectors, cloud services or legitimate websites so the traffic looks normal.

What are common C2 frameworks?

Red teams and criminals use many of the same frameworks: Cobalt Strike (commercial, widely abused with cracked copies), Sliver, Havoc, Mythic and Brute Ratel. Many malware families also have their own built-in C2.

What is beaconing?

Beaconing is an implant checking in with its C2 server at intervals, often with random jitter to avoid obvious patterns. Regular small connections to an uncommon destination are a classic sign of C2.

Why do red teams use C2?

A red team uses C2 the same way an attacker would, so the engagement tests whether your network monitoring, EDR and analysts would notice and respond to a real intrusion.

Change log

  1. 14 November 2026First published.
1300 654 898