Data Encoding T1132

Adversaries 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.

Events covered

5 catalog events are tagged with this technique by at least one rule.

Authoring guide

Patterns shared across the 11 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (10 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
CommandLine5match 3, contains 2(?i)-encode, ::decompress, frombase64string, gzipstream, h4si
EventID5eq 51, 4688, 4103, 4104
Type3eq 3
process_name2match 2(?i)certutil
Image1contains 1, ends_with 1\dnscat2, \iodine.exe
ScriptBlockText1contains 1frombase64string, h4si, memorystream
event.type1in 1change, creation
event_type1in 1childproc, netconn, proc
file.Ext.header_bytes1starts_with 11F8B, 1F9D, 1FA0
process.code_signature.trusted1ne 1true

Top indicator values (53 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.

FieldKindValueRules (here)Corpus reach
CommandLinematch
(?i)-encode
33
EventIDeq
1
2232
EventIDeq
4688
2312
EventIDeq
4103
1105
EventIDeq
4104
1268
process_namematch
(?i)certutil
24
CommandLinecontains
::decompress
1
CommandLinecontains
frombase64string
113
CommandLinecontains
gzipstream
1
CommandLinecontains
h4si
1
CommandLinecontains
memorystream
1
Imagecontains
\dnscat2
1
Imageends_with
\iodine.exe
1
ScriptBlockTextcontains
frombase64string
14
ScriptBlockTextcontains
h4si
1
ScriptBlockTextcontains
memorystream
1
event.typein
change
110
event.typein
creation
19
event_typein
childproc
127
event_typein
netconn
127
event_typein
proc
127
file.Ext.header_bytesstarts_with
1F8B
1
file.Ext.header_bytesstarts_with
1F9D
1
file.Ext.header_bytesstarts_with
1FA0
1
file.Ext.header_bytesstarts_with
28B52FFD
1
file.Ext.header_bytesstarts_with
2A2A4143452A2A
1
file.Ext.header_bytesstarts_with
2D686C302D
1
file.Ext.header_bytesstarts_with
2D686C352D
1
file.Ext.header_bytesstarts_with
303730373037
1
file.Ext.header_bytesstarts_with
377ABCAF271C
1

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Sigma 4 rules

Elastic 1 rule

Splunk 6 rules