T1132 Data Encoding
EnterpriseAdversaries may encode data to make the content of command and control traffic more difficult to detect. Command and control (C2) information can be encoded using a standard data encoding system. Use of data encoding may adhere to existing protocol specifications and includes use of ASCII, Unicode, Base64, MIME, or other binary-to-text and character encoding systems. Some data encoding systems may also result in data compression, such as gzip.
platforms
Platforms this applies to.
tactics
ATT&CK tactics this technique serves.
sub-techniques (2)
More specific entries beneath this one.
mitigations
ATT&CK mitigations that reduce this.
detected by (5)
Data components that detect this.
countered by (D3FEND)
D3FEND countermeasures that counter this.
Detect
NIST CSF 2.0 — areas of relevance (Protect / Detect)
NIST CSF 2.0 areas this most relates to (evidence-ranked).
- DE.CMContinuous Monitoringstrong · backed by 5 of 7 mapped controls
- PR.DSData Securitystrong · backed by 4 of 7 mapped controls
- DE.AEAdverse Event Analysismoderate · backed by 2 of 7 mapped controls
Derived from MITRE CTID (Apache-2.0) and the NIST 800-53 ↔ CSF crosswalk (public domain). Indicative relevance along the Protect/Detect axis — not a compliance assessment or coverage claim.
mitigating controls (7)
Security controls that mitigate this.
groups (1)
Threat groups associated with this.
software (7)
Malware and tools associated with this.
source
Where this definition is published.