Attempt to Disable Syslog Service

Adversaries may attempt to disable the syslog service in an attempt to an attempt to disrupt event logging and evade detection by security controls.

Rule type: query

Rule indices:

auditbeat-*
logs-endpoint.events.*

Severity: medium

Risk score: 47

Runs every: 5 minutes

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

Maximum alerts per execution: 100

Tags:

Elastic
Host
Linux
Threat Detection
Defense Evasion

Version: 7 (version history)

Added (Elastic Stack release): 7.8.0

Last modified (Elastic Stack release): 7.12.0

Rule authors: Elastic

Rule license: Elastic License v2

Rule query

edit

event.category:process and event.type:(start or process_started) and
((process.name:service and process.args:stop) or
(process.name:chkconfig and process.args:off) or
(process.name:systemctl and process.args:(disable or stop or kill)))
and process.args:(syslog or rsyslog or "syslog-ng")

Threat mapping

edit

Framework: MITRE ATT&CK^TM

Tactic:
- Name: Defense Evasion
- ID: TA0005
- Reference URL: https://attack.mitre.org/tactics/TA0005/
Technique:
- Name: Impair Defenses
- ID: T1562
- Reference URL: https://attack.mitre.org/techniques/T1562/

Rule version history

edit

Version 7 (7.12.0 release)

Formatting only

Version 6 (7.11.2 release)

Formatting only

Version 5 (7.11.0 release)

Formatting only

Version 4 (7.10.0 release)

Formatting only

Version 3 (7.9.1 release)

Formatting only

Version 2 (7.9.0 release)

Updated query, changed from:

event.action:(executed or process_started) and ((process.name:service
and process.args:stop) or (process.name:chkconfig and
process.args:off) or (process.name:systemctl and process.args:(disable
or stop or kill))) and process.args:(syslog or rsyslog or "syslog-ng")

« Attempt to Disable IPTables or Firewall Attempt to Enable the Root Account »