MITRE D3FENDdefensive technique
D3-DA Dynamic Analysis
- Tactic
- Detect
- Synonyms
- Malware Detonation, Malware Sandbox
Definition
Executing or opening a file in a synthetic "sandbox" environment to determine if the file is a malicious program or if the file exploits another program such as a document reader.
How it works
How it works
Analyzing the interaction of a piece of code with a system while the code is being executed in a controlled environment such as a sandbox, virtual machine, or simulator. This exposes the natural behavior of the piece of code without requiring the code to be disassembled.
Considerations
• Malware often detects a fake environment, then changes its behavior accordingly. For example, it could detect that the system clock is being sped up in an effort to get it to execute commands that it would normally only execute at a later time, or that the hardware manufacturer of the machine is a virtualization provider.
• Malware can attempt to determine if it is being debugged, and change its behavior accordingly.
• For maximum fidelity, the simulated and real environments should be as similar as possible because the malware could perform differently in different environments.
• Sometimes the malware behavior is triggered only under certain conditions (on a specific system date, after a certain time, or after it is sent a specific command) and can't be detected through a short execution in a virtual environment.
Implementations
• Cuckoo Sandbox
Related
Counters · MITRE ATT&CK (57)
- T0895 Autorun Image technique
- T0894 System Binary Proxy Execution technique
- T1564.007 VBA Stomping sub-technique
- T0865 Spearphishing Attachment technique
- T0871 Execution through API technique
- T1027.004 Compile After Delivery sub-technique
- T1546.015 Component Object Model Hijacking sub-technique
- T1574.007 Path Interception by PATH Environment Variable sub-technique
- T1574.008 Path Interception by Search Order Hijacking sub-technique
- T1574.009 Path Interception by Unquoted Path sub-technique
- T1574 Hijack Execution Flow technique
- T1204.002 Malicious File sub-technique
- T1565 Data Manipulation technique
- T1565.003 Runtime Data Manipulation sub-technique
- T1566 Phishing technique
- T1566.001 Spearphishing Attachment sub-technique
- T1566.002 Spearphishing Link sub-technique
- T1564 Hide Artifacts technique
- T1114.001 Local Email Collection sub-technique
- T1036.001 Invalid Code Signature sub-technique
- T1036.003 Rename Legitimate Utilities sub-technique
- T1027.001 Binary Padding sub-technique
- T1027.002 Software Packing sub-technique
- T1548 Abuse Elevation Control Mechanism technique
- T1548.002 Bypass User Account Control sub-technique
- T1546.002 Screensaver sub-technique
- T1546.005 Trap sub-technique
- T1546.006 LC_LOAD_DYLIB Addition sub-technique
- T1546.008 Accessibility Features sub-technique
- T1546.013 PowerShell Profile sub-technique
Child of · MITRE D3FEND (1)
- D3-FA File Analysis defensive technique
References
- https://patents.google.com/patent/US20150319136A1 Malware analysis system
- https://patents.google.com/patent/US20180032727A1 Use of an application controller to monitor and control software file and application environments