Potential Shadow File Read via Command Line Utilities

  1[metadata]
  2creation_date = "2022/09/01"
  3integration = ["endpoint"]
  4maturity = "production"
  5updated_date = "2024/10/17"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10Identifies access to the /etc/shadow file via the commandline using standard system utilities. After elevating
 11privileges to root, threat actors may attempt to read or dump this file in order to gain valid credentials. They may
 12utilize these to move laterally undetected and access additional resources.
 13"""
 14from = "now-9m"
 15index = ["logs-endpoint.events.*", "endgame-*"]
 16language = "kuery"
 17license = "Elastic License v2"
 18name = "Potential Shadow File Read via Command Line Utilities"
 19references = ["https://www.cyberciti.biz/faq/unix-linux-password-cracking-john-the-ripper/"]
 20risk_score = 47
 21rule_id = "9a3a3689-8ed1-4cdb-83fb-9506db54c61f"
 22setup = """## Setup
 23
 24This rule requires data coming in from Elastic Defend.
 25
 26### Elastic Defend Integration Setup
 27Elastic 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.
 28
 29#### Prerequisite Requirements:
 30- Fleet is required for Elastic Defend.
 31- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
 32
 33#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
 34- Go to the Kibana home page and click "Add integrations".
 35- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
 36- Click "Add Elastic Defend".
 37- Configure the integration name and optionally add a description.
 38- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
 39- 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).
 40- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
 41- 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.
 42For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
 43- Click "Save and Continue".
 44- 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.
 45For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
 46"""
 47severity = "medium"
 48tags = [
 49    "Domain: Endpoint",
 50    "OS: Linux",
 51    "Use Case: Threat Detection",
 52    "Tactic: Privilege Escalation",
 53    "Tactic: Credential Access",
 54    "Data Source: Elastic Endgame",
 55    "Data Source: Elastic Defend",
 56]
 57timestamp_override = "event.ingested"
 58type = "new_terms"
 59query = '''
 60host.os.type : "linux" and event.category : "process" and event.action : ("exec" or "exec_event") and
 61(process.args : "/etc/shadow" or (process.working_directory: "/etc" and process.args: "shadow")) and not (
 62  (process.executable : ("/bin/chown" or "/usr/bin/chown") and process.args : "root:shadow") or
 63  (process.executable : ("/bin/chmod" or "/usr/bin/chmod") and process.args : "640") or
 64  process.executable:(/vz/* or /var/lib/docker/* or /run/containerd/* or /tmp/.criu* or /tmp/newroot/*) or
 65  process.parent.name:(gen_passwd_sets or scc_* or wazuh-modulesd)
 66)
 67'''
 68
 69[[rule.threat]]
 70framework = "MITRE ATT&CK"
 71
 72[[rule.threat.technique]]
 73id = "T1068"
 74name = "Exploitation for Privilege Escalation"
 75reference = "https://attack.mitre.org/techniques/T1068/"
 76
 77[rule.threat.tactic]
 78id = "TA0004"
 79name = "Privilege Escalation"
 80reference = "https://attack.mitre.org/tactics/TA0004/"
 81[[rule.threat]]
 82framework = "MITRE ATT&CK"
 83
 84[[rule.threat.technique]]
 85id = "T1003"
 86name = "OS Credential Dumping"
 87reference = "https://attack.mitre.org/techniques/T1003/"
 88
 89[[rule.threat.technique.subtechnique]]
 90id = "T1003.008"
 91name = "/etc/passwd and /etc/shadow"
 92reference = "https://attack.mitre.org/techniques/T1003/008/"
 93
 94[rule.threat.tactic]
 95id = "TA0006"
 96name = "Credential Access"
 97reference = "https://attack.mitre.org/tactics/TA0006/"
 98
 99[rule.new_terms]
100field = "new_terms_fields"
101value = ["process.executable"]
102
103[[rule.new_terms.history_window_start]]
104field = "history_window_start"
105value = "now-10d"