Unusual D-Bus Daemon Child Process

  1[metadata]
  2creation_date = "2025/01/21"
  3integration = ["endpoint", "sentinel_one_cloud_funnel"]
  4maturity = "production"
  5updated_date = "2025/03/20"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10This rule detects when an unusual child process is spawned from the `dbus-daemon` parent process. The `dbus-daemon`
 11process is a message bus system that provides a way for applications to talk to each other. Attackers may abuse this
 12process to execute malicious code or escalate privileges.
 13"""
 14from = "now-9m"
 15index = ["logs-endpoint.events.process*", "endgame-*", "logs-sentinel_one_cloud_funnel.*"]
 16language = "eql"
 17license = "Elastic License v2"
 18name = "Unusual D-Bus Daemon Child Process"
 19note = """## Triage and analysis
 20
 21> **Disclaimer**:
 22> This investigation guide was created using generative AI technology and has been reviewed to improve its accuracy and relevance. While every effort has been made to ensure its quality, we recommend validating the content and adapting it to suit your specific environment and operational needs.
 23
 24### Investigating Unusual D-Bus Daemon Child Process
 25
 26The D-Bus daemon is a crucial component in Linux environments, facilitating inter-process communication by allowing applications to exchange information. Adversaries may exploit this by spawning unauthorized child processes to execute malicious code or gain elevated privileges. The detection rule identifies anomalies by monitoring child processes of the D-Bus daemon, excluding known benign processes and paths, thus highlighting potential threats.
 27
 28### Possible investigation steps
 29
 30- Review the process details to identify the unusual child process spawned from the dbus-daemon, focusing on the process name and executable path to determine if it is known or potentially malicious.
 31- Examine the command-line arguments (process.args) of the unusual child process to understand its intended function and assess if it aligns with typical usage patterns.
 32- Investigate the parent process arguments (process.parent.args) to confirm whether the dbus-daemon was running in a session context or another mode that might explain the unusual child process.
 33- Check the process start time and correlate it with other system events or logs to identify any related activities or anomalies occurring around the same time.
 34- Look into the user context under which the unusual child process was executed to determine if it was initiated by a legitimate user or potentially compromised account.
 35- Search for any network connections or file modifications associated with the unusual child process to identify potential data exfiltration or lateral movement activities.
 36
 37### False positive analysis
 38
 39- Known benign processes such as gnome-keyring-daemon and abrt-dbus may trigger the rule. Users can exclude these processes by adding them to the exception list in the detection rule.
 40- Processes executed from common library paths like /usr/lib/ or /usr/local/lib/ are typically non-threatening. Users should review these paths and consider excluding them if they are consistently generating false positives.
 41- The dbus-daemon with the --session argument is generally safe. Users can ensure this argument is included in the exception criteria to prevent unnecessary alerts.
 42- Specific applications like software-properties-dbus and serviceHelper.py are known to be benign. Users should verify these applications' legitimacy in their environment and exclude them if they are frequently flagged.
 43- Regularly review and update the exception list to include any new benign processes or paths that are identified over time, ensuring the rule remains effective without generating excessive false positives.
 44
 45### Response and remediation
 46
 47- Immediately isolate the affected system from the network to prevent potential lateral movement by the adversary.
 48- Terminate any suspicious child processes spawned by the dbus-daemon that are not recognized as legitimate or necessary for system operations.
 49- Conduct a thorough review of the affected system's logs to identify any unauthorized access or changes made by the suspicious process.
 50- Restore any altered or compromised system files from a known good backup to ensure system integrity.
 51- Update and patch the affected system and any related software to close vulnerabilities that may have been exploited.
 52- Implement stricter access controls and monitoring on the dbus-daemon to prevent unauthorized process execution in the future.
 53- Escalate the incident to the security operations team for further investigation and to determine if additional systems are affected."""
 54risk_score = 21
 55rule_id = "9705b458-689a-4ec6-afe8-b4648d090612"
 56setup = """## Setup
 57
 58This rule requires data coming in from Elastic Defend.
 59
 60### Elastic Defend Integration Setup
 61Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 62
 63#### Prerequisite Requirements:
 64- Fleet is required for Elastic Defend.
 65- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
 66
 67#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
 68- Go to the Kibana home page and click "Add integrations".
 69- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
 70- Click "Add Elastic Defend".
 71- Configure the integration name and optionally add a description.
 72- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
 73- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. [Helper guide](https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html).
 74- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
 75- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
 76For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
 77- Click "Save and Continue".
 78- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
 79For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
 80"""
 81severity = "low"
 82tags = [
 83    "Domain: Endpoint",
 84    "OS: Linux",
 85    "Use Case: Threat Detection",
 86    "Tactic: Persistence",
 87    "Tactic: Privilege Escalation",
 88    "Tactic: Execution",
 89    "Data Source: Elastic Endgame",
 90    "Data Source: Elastic Defend",
 91    "Data Source: SentinelOne",
 92    "Resources: Investigation Guide",
 93]
 94timestamp_override = "event.ingested"
 95type = "eql"
 96
 97query = '''
 98process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "start") and
 99process.parent.name == "dbus-daemon" and process.args_count > 1 and not (
100  process.parent.args == "--session" or
101  process.args in ("/usr/lib/software-properties/software-properties-dbus", "/usr/share/backintime/qt/serviceHelper.py") or
102  process.name in ("dbus-daemon-launch-helper", "gnome-keyring-daemon", "abrt-dbus", "aptd", "usb-creator-helper") or
103  process.executable like~ ("/usr/lib/*", "/usr/local/lib/*", "/usr/libexec/*", "/tmp/newroot/*")
104)
105'''
106
107
108[[rule.threat]]
109framework = "MITRE ATT&CK"
110[[rule.threat.technique]]
111id = "T1543"
112name = "Create or Modify System Process"
113reference = "https://attack.mitre.org/techniques/T1543/"
114
115
116[rule.threat.tactic]
117id = "TA0003"
118name = "Persistence"
119reference = "https://attack.mitre.org/tactics/TA0003/"
120[[rule.threat]]
121framework = "MITRE ATT&CK"
122[[rule.threat.technique]]
123id = "T1543"
124name = "Create or Modify System Process"
125reference = "https://attack.mitre.org/techniques/T1543/"
126
127
128[rule.threat.tactic]
129id = "TA0004"
130name = "Privilege Escalation"
131reference = "https://attack.mitre.org/tactics/TA0004/"
132[[rule.threat]]
133framework = "MITRE ATT&CK"
134[[rule.threat.technique]]
135id = "T1059"
136name = "Command and Scripting Interpreter"
137reference = "https://attack.mitre.org/techniques/T1059/"
138[[rule.threat.technique.subtechnique]]
139id = "T1059.004"
140name = "Unix Shell"
141reference = "https://attack.mitre.org/techniques/T1059/004/"
142
143
144
145[rule.threat.tactic]
146id = "TA0002"
147name = "Execution"
148reference = "https://attack.mitre.org/tactics/TA0002/"