Cross-source coverage

T1685.001 / ATT&CK

Disable or Modify Tools: Disable or Modify Windows Event Log

41 rules across 2 sources.

Showing atomic-IOC rules · back to the default

From MITRE ATT&CK 19.2

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.

The EventLog service maintains event logs from various system components and applications. By default, the service automatically starts when a system powers on. An audit policy, maintained by the Local Security Policy (secpol.msc), defines which system events the EventLog service logs. Security audit policy settings can be changed by running secpol.msc, then navigating to Security Settings\Local Policies\Audit Policy for basic audit policy settings or Security Settings\Advanced Audit Policy Configuration for advanced audit policy settings. auditpol.exe may also be used to set audit policies.

Adversaries may target system-wide logging or just that of a particular application. For example, the Windows EventLog service may be disabled using the Set-Service -Name EventLog -Status Stopped or sc config eventlog start=disabled commands (followed by manually stopping the service using Stop-Service -Name EventLog). Additionally, the service may be disabled by modifying the "Start" value in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog then restarting the system for the change to take effect.

There are several ways to disable the EventLog service via registry key modification. Without Administrator privileges, adversaries may modify the "Start" value in the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Security, then reboot the system to disable the Security EventLog. With Administrator privilege, adversaries may modify the same values in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Application to disable the entire EventLog.

Additionally, adversaries may use auditpol and its sub-commands in a command prompt to disable auditing or clear the audit policy. To enable or disable a specified setting or audit category, adversaries may use the /success or /failure parameters. For example, auditpol /set /category:"Account Logon" /success:disable /failure:disable turns off auditing for the Account Logon category. To clear the audit policy, adversaries may run the following lines: auditpol /clear /y or auditpol /remove /allusers.

Platforms
Windows
Telemetry
WinEventLog:SystemWinEventLog:SecurityWinEventLog:Sysmon

How MITRE says to detect it DET0187

Detect Disabled Windows Event Log

Windows Analytic 0535

Detection of attempts to disable or tamper with Windows Event Logging. This includes stopping or disabling the EventLog service, modifying registry keys related to EventLog and Autologger, using `auditpol` or `wevtutil` to disable categories or clear audit policies, and detecting suspicious gaps or resets in event logs. Defenders observe registry changes, service state changes, process execution of disabling commands, and anomalies in event record sequences.

  • WinEventLog:System EventCode=7035
  • WinEventLog:Security EventCode=1102
  • WinEventLog:Sysmon EventCode=13, 14
  • WinEventLog:Sysmon EventCode=1

SigmaHQ/sigma

28 rules
Detection Severity Format
Audit Policy Tampering Via Auditpol High Sigma
Audit Policy Tampering Via NT Resource Kit Auditpol High Sigma
Change Winevt Channel Access Permission Via Registry High Sigma
Disable Security Events Logging Adding Reg Key MiniNt High Sigma
Disable Windows Event Logging Via Registry High Sigma
Disable Windows IIS HTTP Logging High Sigma
Forest Blizzard APT - File Creation Activity High Sigma
HackTool - SharpEvtMute DLL Load High Sigma
HackTool - SharpEvtMute Execution High Sigma
HackTool - SysmonEnte Execution High Sigma

+ 18 more from SigmaHQ/sigma → showing the 10 highest-severity

splunk/security_content

13 rules
Detection Severity Format
Cisco ASA - Logging Message Suppression Undefined SPL
Windows Audit Policy Auditing Option Disabled via Auditpol Undefined SPL
Windows Audit Policy Cleared via Auditpol Undefined SPL
Windows Audit Policy Disabled via Auditpol Undefined SPL
Windows Audit Policy Disabled via Legacy Auditpol Undefined SPL
Windows Audit Policy Excluded Category via Auditpol Undefined SPL
Windows Audit Policy Restored via Auditpol Undefined SPL
Windows Audit Policy Security Descriptor Tampering via Auditpol Undefined SPL
Windows Disable Windows Event Logging Disable HTTP Logging Undefined SPL
Windows Global Object Access Audit List Cleared Via Auditpol Undefined SPL

+ 3 more from splunk/security_content → showing the 10 highest-severity

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.