|T1562.001||Disable or Modify Tools|
|T1562.002||Disable Windows Event Logging|
|T1562.003||Impair Command History Logging|
|T1562.004||Disable or Modify System Firewall|
|T1562.007||Disable or Modify Cloud Firewall|
|T1562.008||Disable or Modify Cloud Logs|
|T1562.009||Safe Mode Boot|
|T1562.011||Spoof Security Alerting|
|T1562.012||Disable or Modify Linux Audit System|
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.
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
audit.conf files to ignore malicious activity.
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
|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.
|ID||Data Source||Data Component||Detects|
Command-line invocation of the
Monitor for missing log files from machines with known active periods.
Monitor changes made to the
|DS0009||Process||OS API Execution||
Monitor for abnormal execution of syslog and other functions associated with system logging.
Using another process or third-party tools, monitor for potentially malicious modifications or access to the