Skip to content

Latest commit

 

History

History
190 lines (154 loc) · 40 KB

File metadata and controls

190 lines (154 loc) · 40 KB

T1027: Obfuscated Files or Information

MITRE ATT&CK Tactic(s): Defense Evasion

MITRE ATT&CK Description

Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit. This is common behavior that can be used across different platforms and the network to evade defenses.

Payloads may be compressed, archived, or encrypted in order to avoid detection. These payloads may be used during Initial Access or later to mitigate detection. Sometimes a user's action may be required to open and Deobfuscate/Decode Files or Information for User Execution. The user may also be required to input a password to open a password protected compressed/encrypted file that was provided by the adversary. (Citation: Volexity PowerDuke November 2016) Adversaries may also used compressed or archived scripts, such as JavaScript.

Portions of files can also be encoded to hide the plain-text strings that would otherwise help defenders with discovery. (Citation: Linux/Cdorked.A We Live Security Analysis) Payloads may also be split into separate, seemingly benign files that only reveal malicious functionality when reassembled. (Citation: Carbon Black Obfuscation Sept 2016)

Adversaries may also obfuscate commands executed from payloads or directly via a Command and Scripting Interpreter. Environment variables, aliases, characters, and other platform/language specific semantics can be used to evade signature based detections and application control mechanisms. (Citation: FireEye Obfuscation June 2017) (Citation: FireEye Revoke-Obfuscation July 2017)(Citation: PaloAlto EncodedCommand March 2017)

Policy / Process Controls

Last accessed: May 23, 2022

Total ATT&CK-mapped resources: 2328

ATT&CK-mapped resources for this (sub)technique: 7

Resources mapped to this (sub)technique can be viewed on this page (see also the ATT&CK to D3FEND Mapper tool):

Technical Controls (Detection Rules)

Last accessed: August 09, 2022

Total ATT&CK-mapped rules: 641

ATT&CK-mapped resources for this (sub)technique: 4

Resources mapped to this (sub)technique can be located in the following files within the repository's rules folder:

Last accessed: August 09, 2022

Total ATT&CK-mapped rules: 450

ATT&CK-mapped resources for this (sub)technique: 5

Resources mapped to this (sub)technique can be located in the following files within the repository's Detections folder:

Last accessed: August 09, 2022

Total ATT&CK-mapped rules: 2578

ATT&CK-mapped resources for this (sub)technique: 81

Resources mapped to this (sub)technique can be located in the following files within the repository's rules folder:

Last accessed: August 09, 2022

Total ATT&CK-mapped rules: 1624

ATT&CK-mapped resources for this (sub)technique: 8

Resources mapped to this (sub)technique can be located in the following files within the repository's detections folder:

Offensive Security Tests

Last accessed: August 10, 2022

Total ATT&CK-mapped tests: 1341

ATT&CK-mapped resources for this (sub)technique: 8

The following unit tests mapped to this (sub)technique can be located in the file here:

  • Decode base64 Data into Script
  • Execute base64-encoded PowerShell
  • Execute base64-encoded PowerShell from Windows Registry
  • Execution from Compressed File
  • DLP Evasion via Sensitive Data in VBA Macro over email
  • DLP Evasion via Sensitive Data in VBA Macro over HTTP
  • Obfuscated Command in PowerShell
  • Obfuscated Command Line using special Unicode characters