From 1a024dde9be1c13e3e8e38c189347ea21e617df9 Mon Sep 17 00:00:00 2001 From: David Kilfoyle Date: Fri, 23 Feb 2024 12:44:49 -0500 Subject: [PATCH 1/2] Test: Asciidoc rendering for links --- docs/en/ingest-management/index.asciidoc | 2 + .../troubleshooting/test.asciidoc | 101 ++++++++++++++++++ 2 files changed, 103 insertions(+) create mode 100644 docs/en/ingest-management/troubleshooting/test.asciidoc diff --git a/docs/en/ingest-management/index.asciidoc b/docs/en/ingest-management/index.asciidoc index 82362704b..c36c84f86 100644 --- a/docs/en/ingest-management/index.asciidoc +++ b/docs/en/ingest-management/index.asciidoc @@ -221,6 +221,8 @@ include::troubleshooting/troubleshooting.asciidoc[leveloffset=+2] include::troubleshooting/faq.asciidoc[leveloffset=+2] +include::troubleshooting/test.asciidoc[leveloffset=+2] + include::release-notes/release-notes-8.12.asciidoc[leveloffset=+1] include::elastic-agent/install-fleet-managed-agent.asciidoc[leveloffset=+2] diff --git a/docs/en/ingest-management/troubleshooting/test.asciidoc b/docs/en/ingest-management/troubleshooting/test.asciidoc new file mode 100644 index 000000000..1371c85cd --- /dev/null +++ b/docs/en/ingest-management/troubleshooting/test.asciidoc @@ -0,0 +1,101 @@ +[[prebuilt-rule-8-12-5-attempt-to-clear-kernel-ring-buffer]] += Attempt to Clear Kernel Ring Buffer + +Monitors for the deletion of the kernel ring buffer events through dmesg. Attackers may clear kernel ring buffer events to evade detection after installing a Linux kernel module (LKM). + +*Rule type*: eql + +*Rule indices*: + +* logs-endpoint.events.* +* endgame-* +* auditbeat-* +* logs-auditd_manager.auditd-* +*Severity*: low + +*Risk score*: 21 + +*Runs every*: 5m + +*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <>) + +*Maximum alerts per execution*: 100 + +*References*: None + +*Tags*: + +* Domain: Endpoint +* OS: Linux +* Use Case: Threat Detection +* Tactic: Defense Evasion +* Data Source: Elastic Defend +* Data Source: Elastic Endgame +* Data Source: Auditd Manager +*Version*: 2 + +*Rule authors*: + +* Elastic +*Rule license*: Elastic License v2 + + +== 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 https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation] + +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. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide] +- 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 https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide] +- 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 https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide] + + + +== Rule query + + +[source, js] +---------------------------------- +process where host.os.type == "linux" and event.action in ("exec", "exec_event", "executed") and +event.type == "start" and process.name == "dmesg" and process.args : "-c" +---------------------------------- + +*Framework*: MITRE ATT&CK^TM^ + +* Tactic: + +** Name: Defense Evasion +** ID: TA0005 +** Reference URL: https://attack.mitre.org/tactics/TA0005/ +* Technique: +** Name: Impair Defenses +** ID: T1562 +** Reference URL: https://attack.mitre.org/techniques/T1562/ +* Sub-technique: +** Name: Disable or Modify Tools +** ID: T1562.001 +** Reference URL: https://attack.mitre.org/techniques/T1562/001/ +* Technique: +** Name: Indicator Removal +** ID: T1070 +** Reference URL: https://attack.mitre.org/techniques/T1070/ +* Sub-technique: +** Name: Clear Linux or Mac System Logs +** ID: T1070.002 +** Reference URL: https://attack.mitre.org/techniques/T1070/002/ \ No newline at end of file From 25af38aa086cd63ec38361df65c12310f25364d7 Mon Sep 17 00:00:00 2001 From: David Kilfoyle Date: Fri, 23 Feb 2024 12:46:01 -0500 Subject: [PATCH 2/2] fix --- docs/en/ingest-management/troubleshooting/test.asciidoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/en/ingest-management/troubleshooting/test.asciidoc b/docs/en/ingest-management/troubleshooting/test.asciidoc index 1371c85cd..147a57571 100644 --- a/docs/en/ingest-management/troubleshooting/test.asciidoc +++ b/docs/en/ingest-management/troubleshooting/test.asciidoc @@ -48,10 +48,12 @@ 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 https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation] 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".