-
Notifications
You must be signed in to change notification settings - Fork 191
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
bc1e8af
commit f9eff8f
Showing
851 changed files
with
23,792 additions
and
3,751 deletions.
There are no files selected for viewing
112 changes: 112 additions & 0 deletions
112
...ckages/8-9-15/prebuilt-rule-8-9-15-attempt-to-clear-kernel-ring-buffer.asciidoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,112 @@ | ||
[[prebuilt-rule-8-9-15-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 <<rule-schedule, `Additional look-back time`>>) | ||
|
||
*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/ |
115 changes: 115 additions & 0 deletions
115
...es/8-9-15/prebuilt-rule-8-9-15-attempt-to-disable-iptables-or-firewall.asciidoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,115 @@ | ||
[[prebuilt-rule-8-9-15-attempt-to-disable-iptables-or-firewall]] | ||
=== Attempt to Disable IPTables or Firewall | ||
|
||
Adversaries may attempt to disable the iptables or firewall service in an attempt to affect how a host is allowed to receive or send network traffic. | ||
|
||
*Rule type*: eql | ||
|
||
*Rule indices*: | ||
|
||
* logs-endpoint.events.* | ||
* endgame-* | ||
|
||
*Severity*: low | ||
|
||
*Risk score*: 21 | ||
|
||
*Runs every*: 5m | ||
|
||
*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>) | ||
|
||
*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 | ||
|
||
*Version*: 6 | ||
|
||
*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.type == "start" and event.action in ("exec", "exec_event") and | ||
( | ||
/* disable FW */ | ||
( | ||
(process.name == "ufw" and process.args == "disable") or | ||
(process.name == "iptables" and process.args == "-F" and process.args_count == 2) | ||
) or | ||
/* stop FW service */ | ||
( | ||
((process.name == "service" and process.args == "stop") or | ||
(process.name == "chkconfig" and process.args == "off") or | ||
(process.name == "systemctl" and process.args in ("disable", "stop", "kill"))) and | ||
process.args in ("firewalld", "ip6tables", "iptables") | ||
) | ||
) | ||
---------------------------------- | ||
|
||
*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/ |
120 changes: 120 additions & 0 deletions
120
...-9-15/prebuilt-rule-8-9-15-base16-or-base32-encoding-decoding-activity.asciidoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,120 @@ | ||
[[prebuilt-rule-8-9-15-base16-or-base32-encoding-decoding-activity]] | ||
=== Base16 or Base32 Encoding/Decoding Activity | ||
|
||
Adversaries may encode/decode data in an attempt to evade detection by host- or network-based security controls. | ||
|
||
*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 <<rule-schedule, `Additional look-back time`>>) | ||
|
||
*Maximum alerts per execution*: 100 | ||
|
||
*References*: None | ||
|
||
*Tags*: | ||
|
||
* Domain: Endpoint | ||
* OS: Linux | ||
* Use Case: Threat Detection | ||
* Tactic: Defense Evasion | ||
* Data Source: Elastic Endgame | ||
* Data Source: Elastic Defend | ||
* Data Source: Auditd Manager | ||
|
||
*Version*: 108 | ||
|
||
*Rule authors*: | ||
|
||
* Elastic | ||
|
||
*Rule license*: Elastic License v2 | ||
|
||
|
||
==== Setup | ||
|
||
|
||
|
||
This rule requires data coming in from one of the following integrations: | ||
- Elastic Defend | ||
- Auditbeat | ||
|
||
|
||
*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]. | ||
|
||
|
||
*Auditbeat Setup* | ||
|
||
Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations. | ||
|
||
|
||
*The following steps should be executed in order to add the Auditbeat on a Linux System:* | ||
|
||
- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages. | ||
- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide]. | ||
- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide]. | ||
- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide]. | ||
- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide]. | ||
|
||
|
||
|
||
==== Rule query | ||
|
||
|
||
[source, js] | ||
---------------------------------- | ||
process where host.os.type == "linux" and event.type in ("start", "process_started") and | ||
process.name in ("base16", "base32", "base32plain", "base32hex") and not process.args in ("--help", "--version") | ||
---------------------------------- | ||
|
||
*Framework*: MITRE ATT&CK^TM^ | ||
|
||
* Tactic: | ||
** Name: Defense Evasion | ||
** ID: TA0005 | ||
** Reference URL: https://attack.mitre.org/tactics/TA0005/ | ||
* Technique: | ||
** Name: Obfuscated Files or Information | ||
** ID: T1027 | ||
** Reference URL: https://attack.mitre.org/techniques/T1027/ | ||
* Technique: | ||
** Name: Deobfuscate/Decode Files or Information | ||
** ID: T1140 | ||
** Reference URL: https://attack.mitre.org/techniques/T1140/ |
Oops, something went wrong.