MITRE ATT&CK T1132: Data Encoding
When to use this skill
Use this skill when the task involves T1132, Data Encoding, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.
Technique context
- ATT&CK domain: enterprise
- ATT&CK ID: T1132
- Technique name: Data Encoding
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1132
- Tactics: command-and-control
- Platforms: ESXi, Linux, macOS, Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
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.(Citation: Wikipedia Binary-to-text Encoding) (Citation: Wikipedia Character Encoding) Some data encoding systems may also result in data compression, such as gzip.
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
templates/detection-brief.md: detection engineering brief template.
templates/hunt-plan.md: threat hunt plan template.
templates/incident-response-note.md: incident response note template.
templates/coverage-assessment.md: ATT&CK coverage assessment template.
scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
- Network Intrusion Prevention
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- BADNEWS (malware)
- H1N1 (malware)
- LAMEHUG (malware)
- Linux Rabbit (malware)
- Mythic (tool)
- Ursnif (malware)
- Velvet Ant (intrusion-set)
- evilginx2 (tool)
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
ATT&CK contributors
1---2name: attack-ent-t1132-data-encoding3description: "Analyze MITRE ATT&CK T1132 Data Encoding in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1132, Data Encoding, or enterprise ATT&CK. Adversaries may encode data to make the content of command and control traffic more difficult to detect."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-ent-t1132-data-encoding7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T113210 attack_stix_id: attack-pattern--cc7b8c4e-9be0-47ca-b0bb-83915ec3ee2f11 attack_version: "1.3"12 attack_modified: "2025-10-24T17:49:23.915Z"13---1415# MITRE ATT&CK T1132: Data Encoding1617## When to use this skill1819Use this skill when the task involves T1132, Data Encoding, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.2021## Technique context2223- ATT&CK domain: enterprise24- ATT&CK ID: T113225- Technique name: Data Encoding26- Type: technique27- ATT&CK URL: https://attack.mitre.org/techniques/T113228- Tactics: command-and-control29- Platforms: ESXi, Linux, macOS, Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries 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.(Citation: Wikipedia Binary-to-text Encoding) (Citation: Wikipedia Character Encoding) Some data encoding systems may also result in data compression, such as gzip.3738## Agent workflow39401. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.412. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.423. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.434. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.445. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.456. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.4647## Bundled resources4849- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.50- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.51- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.52- `templates/detection-brief.md`: detection engineering brief template.53- `templates/hunt-plan.md`: threat hunt plan template.54- `templates/incident-response-note.md`: incident response note template.55- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.56- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.57- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.5859To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6061## Detection guidance6263No ATT&CK detection guidance was present in the source STIX object.6465## Useful telemetry and data sources6667- Not specified in the STIX object.6869## Mitigations to consider7071- Network Intrusion Prevention7273## Known threat context7475Use these examples only as contextual leads, not as proof that an observed event is this technique:7677- BADNEWS (malware)78- H1N1 (malware)79- LAMEHUG (malware)80- Linux Rabbit (malware)81- Mythic (tool)82- Ursnif (malware)83- Velvet Ant (intrusion-set)84- evilginx2 (tool)8586## Recommended output pattern8788When responding with this skill, structure the answer as:8990- Assessment: whether the evidence supports this ATT&CK mapping and why.91- Evidence: specific indicators, logs, behaviors, and assumptions.92- Detection: telemetry sources, analytic logic, and tuning considerations.93- Response: containment, eradication, recovery, and validation actions.94- Coverage gaps: missing logs, sensors, controls, or environmental details.95- References: include the ATT&CK URL and any user-provided evidence references.9697## ATT&CK contributors9899- Itzik Kotler, SafeBreach