Disable or Modify Tools: Disable or Modify Windows Event Log T1685.001

Tactic: Defense Impairment

Adversaries may disable or modify the Windows Event Log to limit data that can be leveraged for detections and audits. Windows Event Log records user and system activity such as login attempts and process creation. This data is used by security tools and analysts to generate detections.

Events covered

11 catalog events are tagged with this technique by at least one rule.

Authoring guide

Patterns shared across the 41 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names 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 (26 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.

FieldRulesHowSample values
CommandLine19contains 16, in 6, ends_with 2/set, */clear*, */remove*, clear, unload
OriginalFileName16eq 16auditpol.exe, fltmc.exe, powershell.exe, pwsh.dll, reg.exe
Image14ends_with 14, eq 3, starts_with 3, contains 2, is_null 1\powershell.exe, \pwsh.exe, \fltmc.exe, \powershell_ise.exe, \tiworker.exe
Details9eq 4, contains 3, is_not_null 2DWORD (0x00000000), (a;;0x1;;;la), (a;;0x1;;;sy), (a;;0x5;;;ba), AnonymousAuthenticationModule
process_name9eq 9auditpol.exe, appcmd.exe
TargetObject6contains 4, ends_with 4, eq 2\microsoft\windows\currentversion\winevt\channels\, \channelaccess, \control\wmi\autologger\, \defender, \defenderapilogger\
Configuration4contains 2, ends_with 1, eq 1/system.webServer/httpLogging/@dontLog, /system.webserver/modules/add, /system.webserver/modules/remove, @logTargetW3C
TargetFilename3ends_with 3, starts_with 3, contains 1.dll, .evtx, .save, \.js, \doit.bat
AuditPolicyChanges2contains 2%%8448, %%8450
CallTrace2contains 1, eq 1Ente, microsoft.build.ni.dll, system.ni.dll, unknown
GrantedAccess2eq 20x1400, 0x1f3fff
ParentImage2eq 2, contains 1, ends_with 1:\windows\temp\, \appdata\local\temp\, \endpoint-protection-installer-x64.tmp, c:\windows\system32\msiexec.exe, c:\windows\syswow64\msiexec.exe
SubcategoryGuid2eq 2{0CCE9210-69AE-11D9-BED3-505054503030}, {0CCE9211-69AE-11D9-BED3-505054503030}, {0CCE9212-69AE-11D9-BED3-505054503030}
TargetImage2contains 1, ends_with 1:\windows\sysmon.exe, :\windows\sysmon64.exe, :\windows\system32\svchost.exe
registry_path2contains 1, in 1*\Microsoft\Windows\EventLog\*, *\\Microsoft\\Windows\\CurrentVersion\\WINEVT\\Channels\\*, \\services\\eventlog\\

Top indicator values (233 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. Click a value to expand the rules under this technique that use it.

FieldKindValueRules (here)Corpus reach
OriginalFileNameeq
auditpol.exe
910
OriginalFileNameeq
fltmc.exe
22
OriginalFileNameeq
powershell.exe
2120
OriginalFileNameeq
pwsh.dll
2112
OriginalFileNameeq
reg.exe
242
process_nameeq
auditpol.exe
810
CommandLinecontains
/set
46
CommandLinecontains
clear
24
CommandLinecontains
disable
213
CommandLinecontains
unload
25
Imageends_with
\powershell.exe
3182
Imageends_with
\pwsh.exe
3168
Imageends_with
\fltmc.exe
23
Imageends_with
\msmpeng.exe
22
Imageends_with
\powershell_ise.exe
241
Imageends_with
\reg.exe
258
Imageends_with
\tiworker.exe
2
AuditPolicyChangescontains
%%8448
23
AuditPolicyChangescontains
%%8450
23
CommandLinein
*/clear*
22
CommandLinein
*/remove*
22
Detailseq
DWORD (0x00000000)
238
Imageeq
c:\windows\servicing\trustedinstaller.exe
2
Imageeq
c:\windows\system32\wevtutil.exe
2
Imagestarts_with
c:\windows\winsxs\
2
SubcategoryGuideq
{0CCE9210-69AE-11D9-BED3-505054503030}
2
SubcategoryGuideq
{0CCE9211-69AE-11D9-BED3-505054503030}
2
SubcategoryGuideq
{0CCE9212-69AE-11D9-BED3-505054503030}
2
SubcategoryGuideq
{0CCE9215-69AE-11D9-BED3-505054503030}
2
SubcategoryGuideq
{0CCE9217-69AE-11D9-BED3-505054503030}
2

Exclusions (75 distinct)

Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. 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. Click a value to expand the rules under this technique that exclude it.

FieldKindValueRules excluding
CommandLinecontains
/?
4
CommandLinecontains
sl
1
CommandLinein
*/?*
2
CommandLinein
*/exclude*
1
CommandLinein
*/resourceSACL*
1
Imageends_with
\msmpeng.exe
2
Imageends_with
\tiworker.exe
2
Imageeq
c:\windows\servicing\trustedinstaller.exe
2
Imageeq
c:\windows\system32\wevtutil.exe
2
Imagestarts_with
c:\windows\winsxs\
2
CallTracecontains
microsoft.build.ni.dll
1
CallTracecontains
system.ni.dll
1
CommandLineends_with
unload DFMFilter
1
CommandLineends_with
unload rtp_filesystem_filter
1
CommandLineends_with
unload rtp_filter
1

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.

Platform (all)
Domain (all)

Sigma 28 rules

Splunk 13 rules