Has encrypted their C2 communications.1
Encrypted Channel T1573
- Tactic
- Command and Control
- Platforms
- ESXi, Linux, macOS, Network Devices, Windows
- Version
- 1.2
- Created
- 16 March 2020
- Last modified
- 24 October 2025
Adversaries may employ an encryption algorithm to conceal command and control traffic rather than relying on any inherent protections provided by a communication protocol. Despite the use of a secure algorithm, these implementations may be vulnerable to reverse engineering if secret keys are encoded and/or generated within malware samples/configuration files.
Encrypted Channel MITRE reference T1573
4 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 encrypted traffic with the C2 to prevent network detection.1
Has used an encrypted http proxy in C2 communications.1
Has used multiple layers of encryption within malware to protect C2 communication.1
All 4 groups for this technique
2 campaigns have been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
Command and control activity includes transmission of an RSA public key in communication from the server, but this is followed by subsequent negotiation stages that represent a form of handshake similar to TLS negotiation.1
In the Triton Safety Instrumented System Attack, TEMP.Veles used cryptcat binaries to encrypt their traffic.1
All 2 campaigns for this technique
11 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 a custom encryption algorithm for content sent to command and control infrastructure.1
Can receive encrypted commands from C2.1
Can use an encrypted channel for C2 communications.1
Has used TLS encryption to initialize a custom protocol for C2 communications.1
Can support encrypted communications between the client and server.123
Can use an encrypted beacon to check in with C2.1
All 11 software entries for this technique · 6 newest in this preview
Offense vs defense T1573
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.
Encrypted Channel detection strategy DET0273
MITRE names one behaviour worth catching for this technique and breaks it into 5 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection Strategy for Encrypted Channel across OS Platforms
AN0759 · Windows
Processes that normally do not initiate network connections establishing outbound encrypted TLS/SSL sessions, especially with asymmetric traffic volumes (client sending more than receiving) or non-standard certificate chains. Defender observations correlate process creation with unexpected network encryption libraries being loaded.
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 |
|---|---|---|
| Module LoadDC0016 | WinEventLog:Sysmon | EventCode=7 |
| Network Connection CreationDC0082 | WinEventLog:Sysmon | EventCode=3, 22 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| AllowedEncryptedProcesses | Whitelist processes expected to use TLS (e.g., browsers, mail clients). |
| EntropyThreshold | Payload randomness threshold to distinguish C2 encryption from legitimate traffic. |
| TimeWindow | Correlation window between process creation, module load, and encrypted connection. |
AN0760 · Linux
Processes like curl, wget, python, socat, or custom binaries initiating TLS/SSL sessions to non-standard destinations. Defender sees abnormal syscalls for connect(), loading of libssl libraries, and persistent outbound encrypted traffic from daemons not normally communicating externally.
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 | linux:osquery | Processes linked with libssl or crypto libraries making outbound connections |
| Application Log ContentDC0038 | linux:syslog | system daemons initiating TLS sessions outside expected services |
| Network Connection CreationDC0082 | auditd:SYSCALL | socket/connect with TLS context by unexpected process |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| WhitelistedDaemons | Legitimate system services expected to use TLS (e.g., package updates). |
| CertificateAuthorities | Trusted CAs; flag self-signed or unrecognized certs. |
AN0761 · macOS
Applications or launchd jobs initiating encrypted TLS traffic to rare external hosts. Defender observes unified logs showing ssl/TLS API calls by processes not baseline-approved, and payload entropy suggesting encrypted C2 sessions.
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 | macos:unifiedlog | Process invoking SSL routines from Security framework |
| Network Traffic ContentDC0085 | macos:unifiedlog | Encrypted session initiation by unexpected binary |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| DoHResolvers | Known legitimate DoH endpoints to reduce false positives. |
| PayloadEntropyThreshold | High-entropy traffic deviations used to detect concealed channels. |
AN0762 · ESXi
VMware management daemons or guest processes initiating encrypted connections outside expected vCenter, update servers, or internal comms. Defender identifies hostd or vpxa initiating outbound TLS flows with uncommon destinations.
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 FlowDC0078 | esxi:vpxd | TLS session established by ESXi service to unapproved endpoint |
| Network Traffic ContentDC0085 | esxi:vmkernel | Inspection of sockets showing encrypted sessions from non-baseline processes |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| AllowedMgmtHosts | Baseline approved endpoints for vCenter or update services. |
AN0763 · Network Devices
Unusual TLS tunnels through ports not normally encrypted (e.g., TLS on port 8080, 53). Defender sees NetFlow/IPFIX or packet inspection indicating high-entropy traffic volumes and asymmetric client/server exchange ratios.
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 FlowDC0078 | NSM:Flow | Session records with TLS-like byte patterns |
| Network Traffic ContentDC0085 | NSM:Connections | Abnormal certificate chains or non-standard ports carrying TLS |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| PortProfiles | Define expected TLS port usage to flag anomalies. |
| TrafficAsymmetryRatio | Sent/received byte thresholds to catch hidden C2. |
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.
SSL/TLS inspection can be used to see the contents of encrypted sessions to look for network-based indicators of malware communication protocols.
Tests from Atomic Red Team (MIT licence) · technique definition