Disable Windows Event and Security Logs Using Built-in Toolsedit

Identifies attempts to disable EventLog via the logman Windows utility, PowerShell, or auditpol. This is often done by attackers in an attempt to evade detection on a system.

Rule type: eql

Rule indices:

  • winlogbeat-*
  • logs-endpoint.events.*
  • logs-windows.*

Severity: low

Risk score: 21

Runs every: 5 minutes

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100



  • Elastic
  • Host
  • Windows
  • Threat Detection
  • Defense Evasion

Version: 2 (version history)

Added (Elastic Stack release): 7.14.0

Last modified (Elastic Stack release): 7.16.0

Rule authors: Elastic, Ivan Ninichuck, Austin Songer

Rule license: Elastic License v2

Rule queryedit

process where event.type in ("start", "process_started") and
((process.name:"logman.exe" or process.pe.original_file_name ==
"Logman.exe") and process.args : "EventLog-*" and process.args :
("stop", "delete")) or ((process.name : ("pwsh.exe",
"powershell.exe", "powershell_ise.exe") or
process.pe.original_file_name in ("pwsh.exe", "powershell.exe",
"powershell_ise.exe")) and process.args : "Set-Service" and
process.args: "EventLog" and process.args : "Disabled") or
((process.name:"auditpol.exe" or process.pe.original_file_name ==
"AUDITPOL.EXE") and process.args : "/success:disable")

Threat mappingedit


Rule version historyedit

Version 2 (7.16.0 release)
  • Formatting only