New

The executive guide to generative AI

Read more

Emond Rules Creation or Modification

edit

Identifies the creation or modification of the Event Monitor Daemon (emond) rules. Adversaries may abuse this service by writing a rule to execute commands when a defined event occurs, such as system start up or user authentication.

Rule type: eql

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

References:

Tags:

  • Elastic
  • Host
  • macOS
  • Threat Detection
  • Persistence

Version: 3 (version history)

Added (Elastic Stack release): 7.12.0

Last modified (Elastic Stack release): 8.3.0

Rule authors: Elastic

Rule license: Elastic License v2

Investigation guide

edit
## Config

If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2, events will not define `event.ingested` and default fallback for EQL rules was not added until 8.2, so you will need to add a custom pipeline to populate `event.ingested` to @timestamp for this rule to work.

Rule query

edit
file where event.type != "deletion" and file.path :
("/private/etc/emond.d/rules/*.plist", "/etc/emon.d/rules/*.plist",
"/private/var/db/emondClients/*")

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 3 (8.3.0 release)
  • Updated query, changed from:

    file where event.type != "deletion" and file.path :
    ("/private/etc/emond.d/rules/*.plist", "/etc/emon.d/rules/*.plist")
Version 2 (8.2.0 release)
  • Formatting only
Was this helpful?
Feedback