shashank-elastic
101 lines
4.5 KiB
TOML
101 lines
4.5 KiB
TOML
[metadata]
|
|
creation_date = "2022/09/01"
|
|
integration = ["endpoint"]
|
|
maturity = "production"
|
|
min_stack_comments = "The single field New Term rule type used in this rule was added in Elastic 8.4"
|
|
min_stack_version = "8.4.0"
|
|
updated_date = "2023/10/16"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
Identifies access to the /etc/shadow file via the commandline using standard system utilities. After elevating
|
|
privileges to root, threat actors may attempt to read or dump this file in order to gain valid credentials. They may
|
|
utilize these to move laterally undetected and access additional resources.
|
|
"""
|
|
from = "now-9m"
|
|
index = ["logs-endpoint.events.*", "endgame-*"]
|
|
language = "kuery"
|
|
license = "Elastic License v2"
|
|
name = "Potential Shadow File Read via Command Line Utilities"
|
|
references = ["https://www.cyberciti.biz/faq/unix-linux-password-cracking-john-the-ripper/"]
|
|
risk_score = 47
|
|
rule_id = "9a3a3689-8ed1-4cdb-83fb-9506db54c61f"
|
|
setup = """
|
|
|
|
This rule requires data coming in from Elastic Defend.
|
|
|
|
### Elastic Defend Integration Setup
|
|
Elastic 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.
|
|
|
|
#### Prerequisite Requirements:
|
|
- Fleet is required for Elastic Defend.
|
|
- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
|
|
|
|
#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
|
|
- Go to the Kibana home page and click Add integrations.
|
|
- In the query bar, search for Elastic Defend and select the integration to see more details about it.
|
|
- Click Add Elastic Defend.
|
|
- Configure the integration name and optionally add a description.
|
|
- Select the type of environment you want to protect, either Traditional Endpoints or Cloud Workloads.
|
|
- 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).
|
|
- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
|
|
- 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.
|
|
For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
|
|
- Click Save and Continue.
|
|
- 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.
|
|
For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
|
|
|
|
"""
|
|
severity = "medium"
|
|
tags = ["Domain: Endpoint", "OS: Linux", "Use Case: Threat Detection", "Tactic: Privilege Escalation", "Tactic: Credential Access", "Data Source: Elastic Endgame", "Data Source: Elastic Defend"]
|
|
timestamp_override = "event.ingested"
|
|
type = "new_terms"
|
|
|
|
query = '''
|
|
host.os.type : "linux" and event.category : "process" and event.action : ("exec" or "exec_event") and
|
|
(process.args : "/etc/shadow" or (process.working_directory: "/etc" and process.args: "shadow")) and not
|
|
(process.executable : ("/bin/chown" or "/usr/bin/chown") and process.args : "root:shadow") and not
|
|
(process.executable : ("/bin/chmod" or "/usr/bin/chmod") and process.args : "640")
|
|
'''
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
|
|
[[rule.threat.technique]]
|
|
id = "T1068"
|
|
name = "Exploitation for Privilege Escalation"
|
|
reference = "https://attack.mitre.org/techniques/T1068/"
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0004"
|
|
name = "Privilege Escalation"
|
|
reference = "https://attack.mitre.org/tactics/TA0004/"
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
|
|
[[rule.threat.technique]]
|
|
id = "T1003"
|
|
name = "OS Credential Dumping"
|
|
reference = "https://attack.mitre.org/techniques/T1003/"
|
|
|
|
[[rule.threat.technique.subtechnique]]
|
|
id = "T1003.008"
|
|
name = "/etc/passwd and /etc/shadow"
|
|
reference = "https://attack.mitre.org/techniques/T1003/008/"
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0006"
|
|
name = "Credential Access"
|
|
reference = "https://attack.mitre.org/tactics/TA0006/"
|
|
|
|
[rule.new_terms]
|
|
field = "new_terms_fields"
|
|
value = ["process.command_line"]
|
|
|
|
[[rule.new_terms.history_window_start]]
|
|
field = "history_window_start"
|
|
value = "now-7d"
|