ATT&CK coverage › Technique
Masquerading: Match Legitimate Resource Name or Location T1036.005
Adversaries may match or approximate the name or location of legitimate files, Registry keys, or other resources when naming/placing them. This is done for the sake of evading defenses and observation.
Events covered
5 catalog events are tagged with this technique by at least one rule.
| Provider | Event ID | Title |
|---|---|---|
| Sysmon | 1 | Process creation |
| Sysmon | 7 | Image loaded |
| Sysmon | 11 | FileCreate |
| Security-Auditing | 4688 | A new process has been created. |
| Defender-DeviceProcessEvents | 9001000 | Process activity (any) |
Authoring guide
Patterns shared across the 14 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (14 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (385 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.
Common exclusions (6 distinct)
Field/operator/value combinations that rules under this technique routinely exclude (top-level not() clauses). These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 12 rules
- Files With System DLL Name In Unsuspected Locations
- Files With System Process Name In Unsuspected Locations
- Potential Binary Impersonating Sysinternals Tools
- Potential MsiExec Masquerading
- Scheduled Task Creation Masquerading as System Processes
- Suspicious Files in Default GPO Folder
- Suspicious Process Masquerading As SvcHost.EXE
- Suspicious Scheduled Task Creation via Masqueraded XML File
- Uncommon Svchost Command Line Parameter
- Uncommon Svchost Parent Process
- Unsigned .node File Loaded
- Windows Processes Suspicious Parent Directory