Techniques › T1546.009 › AN1029
AN1029 Analytic 1029
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Detection of AppCert DLL abuse involves correlating registry modifications to the AppCertDLLs key with subsequent unexpected DLL load behavior during process creation events. Specifically, defenders can observe abnormal DLLs being loaded into standard Windows processes after changes to the 'AppCertDLLs' registry value. Monitoring CreateProcess-family API executions with injected DLLs and linking those DLLs back to recent registry edits is key to identifying misuse. This is often accompanied by elevated privileges and potential lateral movement or discovery behavior.</p>
- Detects
- T1546.009 AppCert DLLs
- Part of
- DET0362 Detection Strategy for AppCert DLLs Persistence via Registry Injection
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=4657 | DC0063 Windows Registry Key Modification |
| WinEventLog:Sysmon | EventCode=1 | DC0032 Process 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 |
|---|---|
TargetObject | Registry path for AppCertDLLs may vary by control set or group policy context |
ImageLoaded | Loaded DLLs may differ by malware family or environment |
ParentImage | Parent processes to monitor for DLL injection can be tuned to exclude known-good cases |
TimeWindow | Time correlation between registry modification and DLL load events may vary |