Chkconfig Service Add

edit

Detects the use of the chkconfig binary to manually add a service for management by chkconfig. Threat actors may utilize this technique to maintain persistence on a system. When a new service is added, chkconfig ensures that the service has either a start or a kill entry in every runlevel and when the system is rebooted the service file added will run providing long-term persistence.

Rule type: eql

Rule indices:

  • logs-*

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

References:

Tags:

  • Elastic
  • Host
  • Linux
  • Threat Detection
  • Persistence
  • Lightning Framework

Version: 100 (version history)

Added (Elastic Stack release): 8.4.0

Last modified (Elastic Stack release): 8.5.0

Rule authors: Elastic

Rule license: Elastic License v2

Rule query

edit
process where event.type == "start" and (process.executable :
"/usr/sbin/chkconfig" and process.args : "--add") or (process.args
: "*chkconfig" and process.args : "--add")

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 100 (8.5.0 release)
  • Updated query, changed from:

    process where event.type == "start" and (process.executable :
    "/usr/sbin/chkconfig" and process.args : "--add") or (process.args
    : "*chkconfig" and process.args : "--add")