Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cyberstrikeus/T1132_data-encoding
Adversaries may encode data to make the content of command and control traffic more difficult to detect.
Passed 21 of 23 test cases with the skill, and 12 of 23 without it.
and 6 more in the full report
9 fixed12 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
How many distinct known MITRE ATT&CK mitigations are formally recognized in the assessment checklist for technique T1132?
| Checked | Without skill | With skill |
|---|---|---|
| States that there is 1 known mitigation. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
Platforms: Linux, macOS, Windows, ESXi
Identify Attack Surface: Determine if the target environment is susceptible to Data Encoding by examining the target platforms (Linux, macOS, Windows).
Assess Existing Defenses: Review whether mitigations for T1132 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.
Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.
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. Signatures are often for unique indicators within protocols and may be based on the specific obfuscation technique used by a particular adversary or tool, and will likely be different across various malware families and versions. Adversaries will likely change tool C2 signatures over time or construct protocols in such a way as to avoid detection by common defensive tools.
test cases passed, vs 12 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.