Techniques › T1574.014 › AN1433
AN1433 Analytic 1433
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Detection focuses on unauthorized manipulation of .NET AppDomainManager behavior. Defenders may observe suspicious creation of new AppDomains within trusted processes, anomalous loading of assemblies via non-standard configuration files, or registry/environment variable changes redirecting AppDomainManager to malicious assemblies. Correlated events include config file tampering, new process creation of .NET host processes (e.g., w3wp.exe, powershell.exe) with modified runtime parameters, and module loads of unusual or unsigned .NET DLLs.</p>
- Detects
- T1574.014 AppDomainManager
- Part of
- DET0517 Detection Strategy for Hijack Execution Flow through the AppDomainManager on Windows.
Log sources and channels
Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.
| Log source | Channel | Data component |
|---|---|---|
| WinEventLog:Security | EventCode=4688 | DC0032 Process Creation |
| WinEventLog:Sysmon | EventCode=11 | DC0039 File Creation |
| WinEventLog:Sysmon | EventCode=7 | DC0016 Module Load |
Mutable elements
Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.
| Field | Description |
|---|---|
TargetProcesses | List of monitored .NET host processes (e.g., powershell.exe, w3wp.exe, svchost.exe). |
AssemblyWhitelist | Known benign .NET assemblies expected to load via AppDomainManager. |
ConfigFilePaths | Directory paths where configuration tampering should be monitored (application directories, system32, program files). |
TimeWindow | Correlation period between file modification of config/environment settings and subsequent anomalous module load. |