Skip to content

Commit c9d1f1b

Browse files
eric-forte-elasticprotectionsmachine
eric-forte-elastic
and
protectionsmachine
authored
[Security Rules] Update security rules package to v8.13.5-beta.1 (elastic#9758)
* [Security Rules] Update security rules package to v8.13.5-beta.1 * Add changelog entry for 8.13.5-beta.1 --------- Co-authored-by: protectionsmachine <72879786+protectionsmachine@users.noreply.github.com>
1 parent a79f813 commit c9d1f1b

File tree

6 files changed

+433
-1
lines changed

6 files changed

+433
-1
lines changed

‎packages/security_detection_engine/changelog.yml‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
# newer versions go on top
22
# NOTE: please use pre-release versions (e.g. -beta.0) until a package is ready for production
3+
- version: 8.13.5-beta.1
4+
changes:
5+
- description: Release security rules update
6+
type: enhancement
7+
link: https://github.com/elastic/integrations/pull/9758
38
- version: 8.13.4
49
changes:
510
- description: Release security rules update

‎packages/security_detection_engine/kibana/security_rule/25d917c4-aa3c-4111-974c-286c0312ff95_4.json‎

Lines changed: 122 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
{
2+
"attributes": {
3+
"author": [
4+
"Elastic"
5+
],
6+
"description": "This rule monitors for network connections from a kworker process. kworker, or kernel worker, processes are part of the kernel's workqueue mechanism. They are responsible for executing work that has been scheduled to be done in kernel space, which might include tasks like handling interrupts, background activities, and other kernel-related tasks. Attackers may attempt to evade detection by masquerading as a kernel worker process.",
7+
"from": "now-9m",
8+
"history_window_start": "now-14d",
9+
"index": [
10+
"logs-endpoint.events.*"
11+
],
12+
"language": "kuery",
13+
"license": "Elastic License v2",
14+
"name": "Network Activity Detected via Kworker",
15+
"new_terms_fields": [
16+
"process.name",
17+
"destination.ip",
18+
"destination.port"
19+
],
20+
"query": "host.os.type:linux and event.category:network and event.action:(connection_attempted or connection_accepted) and \nprocess.name:kworker* and not destination.ip:(\n 10.0.0.0/8 or\n 127.0.0.0/8 or\n 169.254.0.0/16 or\n 172.16.0.0/12 or\n 192.168.0.0/16 or\n 224.0.0.0/4 or\n \"::1\" or\n \"FE80::/10\" or\n \"FF00::/8\"\n) and not destination.port:2049\n",
21+
"related_integrations": [
22+
{
23+
"package": "endpoint",
24+
"version": "^8.2.0"
25+
}
26+
],
27+
"required_fields": [
28+
{
29+
"ecs": true,
30+
"name": "destination.ip",
31+
"type": "ip"
32+
},
33+
{
34+
"ecs": true,
35+
"name": "destination.port",
36+
"type": "long"
37+
},
38+
{
39+
"ecs": true,
40+
"name": "event.action",
41+
"type": "keyword"
42+
},
43+
{
44+
"ecs": true,
45+
"name": "event.category",
46+
"type": "keyword"
47+
},
48+
{
49+
"ecs": true,
50+
"name": "host.os.type",
51+
"type": "keyword"
52+
},
53+
{
54+
"ecs": true,
55+
"name": "process.name",
56+
"type": "keyword"
57+
}
58+
],
59+
"risk_score": 21,
60+
"rule_id": "25d917c4-aa3c-4111-974c-286c0312ff95",
61+
"setup": "## Setup\n\nThis rule requires data coming in from Elastic Defend.\n\n### Elastic Defend Integration Setup\nElastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows\nthe Elastic Agent to monitor events on your host and send data to the Elastic Security app.\n\n#### Prerequisite Requirements:\n- Fleet is required for Elastic Defend.\n- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).\n\n#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:\n- Go to the Kibana home page and click \"Add integrations\".\n- In the query bar, search for \"Elastic Defend\" and select the integration to see more details about it.\n- Click \"Add Elastic Defend\".\n- Configure the integration name and optionally add a description.\n- Select the type of environment you want to protect, either \"Traditional Endpoints\" or \"Cloud Workloads\".\n- 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).\n- We suggest to select \"Complete EDR (Endpoint Detection and Response)\" as a configuration setting, that provides \"All events; all preventions\"\n- 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.\nFor more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).\n- Click \"Save and Continue\".\n- 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.\nFor more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).\n",
62+
"severity": "low",
63+
"tags": [
64+
"Domain: Endpoint",
65+
"OS: Linux",
66+
"Use Case: Threat Detection",
67+
"Tactic: Command and Control",
68+
"Data Source: Elastic Defend"
69+
],
70+
"threat": [
71+
{
72+
"framework": "MITRE ATT&CK",
73+
"tactic": {
74+
"id": "TA0011",
75+
"name": "Command and Control",
76+
"reference": "https://attack.mitre.org/tactics/TA0011/"
77+
},
78+
"technique": []
79+
},
80+
{
81+
"framework": "MITRE ATT&CK",
82+
"tactic": {
83+
"id": "TA0005",
84+
"name": "Defense Evasion",
85+
"reference": "https://attack.mitre.org/tactics/TA0005/"
86+
},
87+
"technique": [
88+
{
89+
"id": "T1036",
90+
"name": "Masquerading",
91+
"reference": "https://attack.mitre.org/techniques/T1036/"
92+
},
93+
{
94+
"id": "T1014",
95+
"name": "Rootkit",
96+
"reference": "https://attack.mitre.org/techniques/T1014/"
97+
}
98+
]
99+
},
100+
{
101+
"framework": "MITRE ATT&CK",
102+
"tactic": {
103+
"id": "TA0010",
104+
"name": "Exfiltration",
105+
"reference": "https://attack.mitre.org/tactics/TA0010/"
106+
},
107+
"technique": [
108+
{
109+
"id": "T1041",
110+
"name": "Exfiltration Over C2 Channel",
111+
"reference": "https://attack.mitre.org/techniques/T1041/"
112+
}
113+
]
114+
}
115+
],
116+
"timestamp_override": "event.ingested",
117+
"type": "new_terms",
118+
"version": 4
119+
},
120+
"id": "25d917c4-aa3c-4111-974c-286c0312ff95_4",
121+
"type": "security-rule"
122+
}

‎packages/security_detection_engine/kibana/security_rule/28f6f34b-8e16-487a-b5fd-9d22eb903db8_1.json‎

Lines changed: 113 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,113 @@
1+
{
2+
"attributes": {
3+
"author": [
4+
"Elastic"
5+
],
6+
"description": "This rule monitors the creation/alteration of a shell configuration by a previously unknown process executable using the new terms rule type. Unix systems use shell configuration files to set environment variables, create aliases, and customize the user's environment. Adversaries may modify or add a shell configuration file to execute malicious code and gain persistence in the system. This behavior is consistent with the Kaiji malware family.",
7+
"false_positives": [
8+
"Legitimate user shell modification activity."
9+
],
10+
"from": "now-9m",
11+
"history_window_start": "now-10d",
12+
"index": [
13+
"logs-endpoint.events.*",
14+
"endgame-*"
15+
],
16+
"language": "kuery",
17+
"license": "Elastic License v2",
18+
"name": "Shell Configuration Modification",
19+
"new_terms_fields": [
20+
"host.id",
21+
"user.id",
22+
"process.executable"
23+
],
24+
"query": "event.category:file and host.os.type:linux and\nevent.action:(creation or file_create_event or rename or file_rename_event) and file.path:(\n \"/etc/profile\" or \"/etc/profile.local\" or \"/etc/bashrc\" or \"/etc/bash.bashrc\" or \"/etc/bash.bashrc.local\" or\n \"/etc/zshenv\" or \"/etc/zprofile\" or \"/etc/zlogin\" or \"/etc/zlogout\" or \"/root/.profile\" or \"/root/.bash_logout\" or\n \"/root/.bashrc\" or \"/root/.bash_login\" or /etc/profile.d/* or /home/*/.profile or /home/*/.bash_logout or\n /home/*/.bashrc or /home/*/.bash_login\n) and not (\n (process.executable: (\n \"/bin/dpkg\" or \"/usr/bin/dpkg\" or \"/bin/useradd\" or \"/usr/sbin/useradd\" or \"/bin/adduser\" or \"/usr/sbin/adduser\" or\n \"/bin/dockerd\" or \"/usr/bin/dockerd\" or \"/bin/microdnf\" or \"/usr/bin/microdnf\" or \"/bin/rpm\" or \"/usr/bin/rpm\" or\n \"/bin/snapd\" or \"/usr/bin/snapd\" or \"/bin/yum\" or \"/usr/bin/yum\" or \"/bin/dnf\" or \"/usr/bin/dnf\" or \"/bin/podman\" or\n \"/usr/bin/podman\" or \"/bin/dnf-automatic\" or \"/usr/bin/dnf-automatic\" or \"/bin/pacman\" or \"/usr/bin/pacman\"\n )\n) or\n (file.extension:(\"swp\" or \"swpx\")) or\n (process.executable:(\"/bin/sed\" or \"/usr/bin/sed\") and file.name:sed*) or\n (process.executable:(\"/bin/perl\" or \"/usr/bin/perl\") and file.name:e2scrub_all.tmp*)\n)\n",
25+
"references": [
26+
"https://intezer.com/blog/research/kaiji-new-chinese-linux-malware-turning-to-golang/"
27+
],
28+
"related_integrations": [
29+
{
30+
"package": "endpoint",
31+
"version": "^8.2.0"
32+
}
33+
],
34+
"required_fields": [
35+
{
36+
"ecs": true,
37+
"name": "event.action",
38+
"type": "keyword"
39+
},
40+
{
41+
"ecs": true,
42+
"name": "event.category",
43+
"type": "keyword"
44+
},
45+
{
46+
"ecs": true,
47+
"name": "file.extension",
48+
"type": "keyword"
49+
},
50+
{
51+
"ecs": true,
52+
"name": "file.name",
53+
"type": "keyword"
54+
},
55+
{
56+
"ecs": true,
57+
"name": "file.path",
58+
"type": "keyword"
59+
},
60+
{
61+
"ecs": true,
62+
"name": "host.os.type",
63+
"type": "keyword"
64+
},
65+
{
66+
"ecs": true,
67+
"name": "process.executable",
68+
"type": "keyword"
69+
}
70+
],
71+
"risk_score": 47,
72+
"rule_id": "28f6f34b-8e16-487a-b5fd-9d22eb903db8",
73+
"setup": "## Setup\n\nThis rule requires data coming in from Elastic Defend.\n\n### Elastic Defend Integration Setup\nElastic 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.\n\n#### Prerequisite Requirements:\n- Fleet is required for Elastic Defend.\n- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).\n\n#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:\n- Go to the Kibana home page and click \"Add integrations\".\n- In the query bar, search for \"Elastic Defend\" and select the integration to see more details about it.\n- Click \"Add Elastic Defend\".\n- Configure the integration name and optionally add a description.\n- Select the type of environment you want to protect, either \"Traditional Endpoints\" or \"Cloud Workloads\".\n- 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).\n- We suggest selecting \"Complete EDR (Endpoint Detection and Response)\" as a configuration setting, that provides \"All events; all preventions\"\n- 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.\nFor more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).\n- Click \"Save and Continue\".\n- 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.\nFor more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).\n",
74+
"severity": "medium",
75+
"tags": [
76+
"Domain: Endpoint",
77+
"OS: Linux",
78+
"Use Case: Threat Detection",
79+
"Tactic: Persistence",
80+
"Data Source: Elastic Endgame",
81+
"Data Source: Elastic Defend"
82+
],
83+
"threat": [
84+
{
85+
"framework": "MITRE ATT&CK",
86+
"tactic": {
87+
"id": "TA0003",
88+
"name": "Persistence",
89+
"reference": "https://attack.mitre.org/tactics/TA0003/"
90+
},
91+
"technique": [
92+
{
93+
"id": "T1546",
94+
"name": "Event Triggered Execution",
95+
"reference": "https://attack.mitre.org/techniques/T1546/",
96+
"subtechnique": [
97+
{
98+
"id": "T1546.004",
99+
"name": "Unix Shell Configuration Modification",
100+
"reference": "https://attack.mitre.org/techniques/T1546/004/"
101+
}
102+
]
103+
}
104+
]
105+
}
106+
],
107+
"timestamp_override": "event.ingested",
108+
"type": "new_terms",
109+
"version": 1
110+
},
111+
"id": "28f6f34b-8e16-487a-b5fd-9d22eb903db8_1",
112+
"type": "security-rule"
113+
}

0 commit comments

Comments
 (0)