Executive Summary
Masquerading (T1036) is a MITRE ATT&CK technique associated with Stealth. Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools.
Why Attackers Use It
Attackers use Masquerading because it provides a reliable way to advance their objective within the Stealth tactic, often with a favorable balance of impact versus detectability on Containers, ESXi, Linux, macOS, Windows environments. Defenders should assess this behavior in the context of the affected platform and adjacent activity rather than treating it as a standalone indicator.
MITRE Description
Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools. Masquerading occurs when the name or location of an object, legitimate or malicious, is manipulated or abused for the sake of evading defenses and observation. This may include manipulating file metadata, tricking users into misidentifying the file type, and giving legitimate task or service names.
Renaming abusable system utilities to evade security monitoring is also a form of Masquerading.(Citation: LOLBAS Main Site)
Attack Flow
- Attacker gains the prerequisite access or context described below.
- Attacker executes Masquerading to achieve its tactical objective (Stealth).
- Resulting access/data/effect is leveraged to advance the broader attack chain (see Related Techniques).
Prerequisites
- Platform(s): Containers, ESXi, Linux, macOS, Windows
- ATT&CK does not define one universal permission requirement for this technique. Establish the required access from the observed implementation and affected platform.
Common Tools
- Tool attribution is implementation-specific. Use ATT&CK procedure examples and local telemetry to identify the binaries, services, scripts, accounts, or cloud resources involved.
Commands
No universal command represents Masquerading. Capture the exact command line, arguments, parent process, account, host, and execution time from the investigated environment; do not operationalize unverified examples.
Network Traffic
- Network observability is implementation-dependent. Review DNS, proxy, firewall, flow, authentication, and packet telemetry around the activity window, then correlate remote endpoints and protocol behavior with host evidence.
Windows Events
| Event ID | Log Channel | What It Indicates |
|---|
| Environment-specific | Relevant Windows channel(s) | Correlate authentication, process, object-access, and configuration events with the observed execution context. |
Sysmon Events
| Sysmon Event ID | Name | Why It's Relevant Here |
|---|
| Environment-specific | Validate configured telemetry | Use process, network, file, registry, DNS, or image-load telemetry only when relevant and enabled. |
Detection Opportunities
No MITRE detection guidance published for this technique.
Relevant ATT&CK Data Sources: N/A
Sigma Rules
A universal Sigma rule would create unreliable results because this technique has no single guaranteed observable. Build detection logic from a documented behavior and supported data source, scope it to the affected platform, and validate it against benign administrative activity before deployment.
Splunk Queries
Start with the data sources named in the detection section. Scope searches by asset, identity, and time window; correlate the primary behavior with preceding access and subsequent actions. A portable query is intentionally not provided where the technique lacks a universal schema or observable.
Investigation Workflow
- Confirm that the observed behavior is consistent with Masquerading and rule out expected administrative or application activity.
- Establish the first-seen time, initiating identity, source system, target system, and affected resources.
- Collect relevant host, identity, network, cloud, and application telemetry for the surrounding time window.
- Correlate parent and child activity, remote connections, file or configuration changes, and related ATT&CK techniques.
- Determine scope by searching for the same observable across peer assets and identities.
- Preserve volatile evidence and record confidence, assumptions, and telemetry gaps before containment.
Containment
- Isolate affected host(s)/account(s) identified during investigation.
- Revoke or rotate any credentials/tokens potentially exposed.
- Apply the mitigations listed below where not already enforced.
- Validate no related techniques (see Related Techniques) were chained against the same asset.
Mitigation
- M1047 -- Audit: Auditing is the process of recording activity and systematically reviewing and analyzing the activity and system configurations.
- M1018 -- User Account Management: User Account Management involves implementing and enforcing policies for the lifecycle of user accounts, including creation, modification, and deactivation.
- M1017 -- User Training: User Training involves educating employees and contractors on recognizing, reporting, and preventing cyber threats that rely on human interaction, such as phishing, social engineering, and other manipulative techniques.
- M1045 -- Code Signing: Code Signing is a security process that ensures the authenticity and integrity of software by digitally signing executables, scripts, and other code artifacts.
- M1040 -- Behavior Prevention on Endpoint: Behavior Prevention on Endpoint refers to the use of technologies and strategies to detect and block potentially malicious activities by analyzing the behavior of processes, files, API calls, and other endpoint events.
- M1022 -- Restrict File and Directory Permissions: Restricting file and directory permissions involves setting access controls at the file system level to limit which users, groups, or processes can read, write, or execute files.
- M1049 -- Antivirus/Antimalware: Antivirus/Antimalware solutions utilize signatures, heuristics, and behavioral analysis to detect, block, and remediate malicious software, including viruses, trojans, ransomware, and spyware.
- M1038 -- Execution Prevention: Prevent the execution of unauthorized or malicious code on systems by implementing application control, script blocking, and other execution prevention mechanisms.
Related Techniques
- T1036.001
- T1036.002
- T1036.003
- T1036.004
- T1036.005
- T1036.006
- T1036.007
- T1036.008
- T1036.009
- T1036.010
- T1036.011
- T1036.012
- T1059.003
- T1071.001
- T1082
- T1083
- T1102.003
- T1105
- T1140
- T1195.001
- T1204.002
- T1219.002
- T1546
- T1566.001
- T1665