Disable or Modify Tools: Disable or Modify Linux Audit System Log
- ID
- T1685.004
- Tactics
- TA0112 Defense Impairment
- Sub-technique of
- T1685 Disable or Modify Tools
- Platforms
- Linux
- Data sources
- Command Execution, Process Modification, File Modification, Service Metadata
- Source
- attack.mitre.org
- MITRE last modified
- 12 May 2026
Adversaries may disable or modify the Linux Audit system to hide malicious activity and avoid detection. Linux admins use the Linux Audit system to track security-relevant information on a system. The Linux Audit system operates at the kernel-level and maintains event logs on application and system activity such as process, network, file, and login events based on pre-configured rules.
Often referred to as auditd, this is the name of the daemon used to write events to disk and is governed by the parameters set in the audit.conf configuration file. Two primary ways to configure the log generation rules are through the command line auditctl utility and the file /etc/audit/audit.rules, containing a sequence of auditctl commands loaded at boot time.[1][2]
With root privileges, adversaries may be able to ensure their activity is not logged through disabling the Audit system service, editing the configuration/rule files, or by hooking the Audit system library functions. Using the command line, adversaries can disable the Audit system service through killing processes associated with auditd daemon or use systemctl to stop the Audit service. Adversaries can also hook Audit system functions to disable logging or modify the rules contained in the /etc/audit/audit.rules or audit.conf files to ignore malicious activity.[3]
Detection
- DET0062 Detection Strategy for Disable or Modify Linux Audit System Log
Data components: Command Execution, Process Modification, File Modification, Service Metadata
Mitigations (2)
- M1018 User Account Management
An adversary must already have root level access on the local system to make full use of this technique; be sure to restrict users and accounts to the least privileges they require.
- M1047 Audit
Routinely check account role permissions to ensure only expected users and roles have permission to modify logging settings.
To ensure Audit rules can not be modified at runtime, add the
auditctl -e 2as the last command in the audit.rules files. Once started, any attempt to change the configuration in this mode will be audited and denied. The configuration can only be changed by rebooting the machine.
