From 4ec15ae24c20fb6d3ad0362d7eaf47d8c02abf9d Mon Sep 17 00:00:00 2001 From: Ruben Groenewoud <78494512+Aegrah@users.noreply.github.com> Date: Fri, 1 Nov 2024 16:09:56 +0100 Subject: [PATCH 1/2] [New Rule] Hidden Directory Creation via Unusual Parent --- ...nse_evasion_hidden_directory_creation.toml | 99 +++++++++++++++++++ 1 file changed, 99 insertions(+) create mode 100644 rules/linux/defense_evasion_hidden_directory_creation.toml diff --git a/rules/linux/defense_evasion_hidden_directory_creation.toml b/rules/linux/defense_evasion_hidden_directory_creation.toml new file mode 100644 index 00000000000..8547a0bdb25 --- /dev/null +++ b/rules/linux/defense_evasion_hidden_directory_creation.toml @@ -0,0 +1,99 @@ +[metadata] +creation_date = "2024/11/01" +integration = ["endpoint"] +maturity = "production" +updated_date = "2024/11/01" + +[rule] +author = ["Elastic"] +description = """ +This rule detects the creation of a hidden directory via an unusual parent executable. Hidden directories are +directories that are not visible to the user by default. They are often used by attackers to hide malicious files or +tools. +""" +false_positives = [ + """ + Certain tools may create hidden temporary directories upon installation or as part of their normal + behavior. These events can be filtered by the process arguments, username, or process name values. + """, +] +from = "now-9m" +index = ["logs-endpoint.events.*"] +language = "eql" +license = "Elastic License v2" +name = "Hidden Directory Creation via Unusual Parent" +risk_score = 21 +rule_id = "b15a15f2-becf-475d-aa69-45c9e0ff1c49" +setup = """## 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 selecting "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 = "low" +tags = [ + "Domain: Endpoint", + "OS: Linux", + "Use Case: Threat Detection", + "Tactic: Defense Evasion", + "Data Source: Elastic Defend", +] +timestamp_override = "event.ingested" +type = "eql" +query = ''' +process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and +process.name == "mkdir" and process.parent.executable like ( + "/dev/shm/*", "/tmp/*", "/var/tmp/*", "/var/run/*", "/root/*", "/boot/*", "/var/www/html/*", "/opt/.*" +) and process.args like (".*", "/*/.*") and process.args_count <= 3 and not ( + process.parent.executable like ("/tmp/newroot/*", "/run/containerd/*") or + process.command_line like ("mkdir -p .", "mkdir ./*") or + process.parent.executable like ( + "/tmp/pear/temp/*", "/var/tmp/buildah*", "/tmp/python-build.*", "/tmp/cliphist-wofi-img" + ) +) +''' + +[[rule.threat]] +framework = "MITRE ATT&CK" + +[[rule.threat.technique]] +id = "T1564" +name = "Hide Artifacts" +reference = "https://attack.mitre.org/techniques/T1564/" + +[[rule.threat.technique.subtechnique]] +id = "T1564.001" +name = "Hidden Files and Directories" +reference = "https://attack.mitre.org/techniques/T1564/001/" + +[rule.threat.tactic] +id = "TA0005" +name = "Defense Evasion" +reference = "https://attack.mitre.org/tactics/TA0005/" + +[[rule.threat]] +framework = "MITRE ATT&CK" + +[rule.threat.tactic] +id = "TA0003" +name = "Persistence" +reference = "https://attack.mitre.org/tactics/TA0003/" From 2d1a1f11a5670dc21dde5342ea66e18869929882 Mon Sep 17 00:00:00 2001 From: Ruben Groenewoud <78494512+Aegrah@users.noreply.github.com> Date: Fri, 8 Nov 2024 17:10:25 +0100 Subject: [PATCH 2/2] Update rules/linux/defense_evasion_hidden_directory_creation.toml Co-authored-by: shashank-elastic <91139415+shashank-elastic@users.noreply.github.com> --- rules/linux/defense_evasion_hidden_directory_creation.toml | 1 + 1 file changed, 1 insertion(+) diff --git a/rules/linux/defense_evasion_hidden_directory_creation.toml b/rules/linux/defense_evasion_hidden_directory_creation.toml index 8547a0bdb25..079b1f1292e 100644 --- a/rules/linux/defense_evasion_hidden_directory_creation.toml +++ b/rules/linux/defense_evasion_hidden_directory_creation.toml @@ -56,6 +56,7 @@ tags = [ "Use Case: Threat Detection", "Tactic: Defense Evasion", "Data Source: Elastic Defend", + "Tactic: Persistence", ] timestamp_override = "event.ingested" type = "eql"