Has used reverse SSH tunnels to communicate to victim devices.1
Application Layer Protocol T1071
- Tactic
- Command and Control
- Platforms
- Linux, macOS, Windows, Network Devices, ESXi
- Version
- 2.4
- Created
- 31 May 2017
- Last modified
- 24 October 2025
- Contributor
- Duane Michael
Adversaries may communicate using OSI application layer protocols to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.
Application Layer Protocol MITRE reference T1071
5 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Has used valid accounts over RDP to connect to targeted systems.1
Has used an IRC bot for C2 communications.1
Issued wget requests from infected systems to the C2.1
All 5 groups for this technique
1 campaign has been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During FrostyGoop Incident, the adversary initiated Layer Two Tunnelling Protocol (L2TP) connections to Moscow-based IP addresses.1
All 1 campaigns for this technique
10 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Uses TCP and UDP communication for command and control traffic.12
Is capable of contacting the TOR network for delivering second-stage payloads.123
Can use an inverse negotiated SSH connection as part of its C2.1
Has the ability to use Telnet for communication.1
Can utilize the Wireguard VPN protocol for command and control.1
Connects to an IRC server for C2.1
All 10 software entries for this technique · 6 newest in this preview
Offense vs defense T1071
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Application Layer Protocol detection strategy DET0444
MITRE names one behaviour worth catching for this technique and breaks it into 4 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection of Command and Control Over Application Layer Protocols
AN1225 · Windows
Detects suspicious usage of common application-layer protocols (e.g., HTTP, HTTPS, DNS, SMB) by abnormal processes, with high outbound byte counts or irregular ports, possibly indicating command and control or data exfiltration.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Network Connection CreationDC0082 | WinEventLog:Sysmon | EventCode=3, 22 |
| Network Traffic ContentDC0085 | NSM:Flow | http, dns, smb, ssl logs |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ProtocolList | Limit detection to app-layer protocols of interest: HTTP, DNS, SSL, SMB, RDP |
| DataVolumeThreshold | Detects asymmetric communication volume (e.g., >90% outbound) |
| UnusualProcessList | Track processes not normally associated with network activity |
AN1226 · Linux
Detects suspicious curl, wget, or custom socket traffic that leverages DNS, HTTPS, or IRC-style protocols with unbalanced traffic or beacon-like intervals.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | auditd:SYSCALL | execve |
| Network Traffic ContentDC0085 | NSM:Flow | dns, ssl, conn |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| KnownPortsToMonitor | Uncommon ports for HTTPS, IRC, DNS (e.g., 8443, 5353) |
| BeaconTimingThreshold | Detect intervals of outbound traffic within fixed timeframes |
AN1227 · macOS
Detects applications using abnormal protocols or high volume traffic not previously associated with the process image, such as Automator or AppleScript invoking curl or python sockets.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Command ExecutionDC0064 | macos:unifiedlog | log stream |
| Network Traffic FlowDC0078 | macos:osquery | socket_events |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| SocketParentProcessMatch | Non-browser processes opening sockets to external IPs |
| DataFlowImbalanceRatio | High outbound/inbound ratio indicating C2 beacon |
AN1228 · Network Devices
Detects application-layer tunneling or unauthorized app protocols like DNS-over-HTTPS, embedded C2 in TLS/HTTP headers, or misused SMB traffic crossing VLANs.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Network Traffic ContentDC0085 | NSM:Flow | conn.log, http.log, dns.log, ssl.log |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| AppProtocolAbusePattern | Detects DNS tunneling, encrypted HTTP C2, or malformed headers |
| NorthSouthEgressFilter | Monitor internal hosts talking externally using internal protocols (e.g., SMB) |
Use network appliances to filter ingress or egress traffic and perform protocol-based filtering. Configure software on endpoints to filter network traffic.
Network intrusion detection and prevention systems that use network signatures to identify traffic for specific adversary malware can be used to mitigate activity at the network level.
Tests from Atomic Red Team (MIT licence) · technique definition