Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
23 commits
Select commit Hold shift + click to select a range
a9aaed4
[New] Container Runtime CLI Execution with Suspicious Arguments
Samirbous Apr 29, 2026
a0d202b
Update execution_container_runtime_cli_suspicious_arguments.toml
Samirbous Apr 29, 2026
e3a1db7
Update execution_container_runtime_cli_suspicious_arguments.toml
Samirbous Apr 29, 2026
b3d42d3
Update execution_container_runtime_cli_suspicious_arguments.toml
Samirbous Apr 29, 2026
1876c1a
Update execution_container_runtime_cli_suspicious_arguments.toml
Samirbous May 1, 2026
5869840
Update execution_container_runtime_cli_suspicious_arguments.toml
Samirbous May 1, 2026
c649455
Create execution_container_runtime_cli_suspicious_args.toml
Samirbous May 1, 2026
c21239e
Merge branch 'main' into ctr_r
Samirbous May 1, 2026
2d91d4a
Apply suggestion from @terrancedejesus
Samirbous May 1, 2026
490a6ae
Update execution_container_runtime_cli_suspicious_args.toml
Samirbous May 1, 2026
695c9b8
Merge branch 'main' into ctr_r
Samirbous May 1, 2026
366a935
Update execution_container_runtime_cli_suspicious_arguments.toml
Samirbous May 5, 2026
35a2e37
Update execution_container_runtime_cli_suspicious_args.toml
Samirbous May 5, 2026
2c42a5b
Update execution_container_runtime_cli_suspicious_args.toml
Samirbous May 5, 2026
b9bce68
Update execution_container_runtime_cli_suspicious_arguments.toml
Samirbous May 5, 2026
489f96b
Update execution_container_runtime_cli_suspicious_arguments.toml
Samirbous May 5, 2026
cdb8ab7
Update execution_container_runtime_cli_suspicious_args.toml
Samirbous May 5, 2026
e2405fe
Update execution_container_runtime_cli_suspicious_arguments.toml
Samirbous May 5, 2026
db7cb86
Merge branch 'main' into ctr_r
Samirbous May 5, 2026
6648fe4
Update rules/integrations/cloud_defend/execution_container_runtime_cl…
Samirbous May 5, 2026
8af336e
Merge branch 'main' into ctr_r
Samirbous May 5, 2026
e36c335
Merge branch 'main' into ctr_r
Samirbous May 5, 2026
8797425
Merge branch 'main' into ctr_r
Samirbous May 5, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,114 @@
[metadata]
creation_date = "2026/05/01"
integration = ["cloud_defend"]
Comment thread
Samirbous marked this conversation as resolved.
maturity = "production"
min_stack_comments = "Defend for Containers integration was re-introduced in 9.3.0"
min_stack_version = "9.3.0"
updated_date = "2026/05/01"

[rule]
author = ["Elastic"]
description = """
Detects execution of container runtime CLI tools (ctr, crictl, nerdctl) with arguments indicating container creation,
command execution inside existing containers, image manipulation, or host filesystem mounting. These tools interact
directly with the container runtime socket, bypassing the Kubernetes API server, RBAC authorization, admission webhooks,
pod security standards, and Kubernetes audit logging entirely. Attackers with host-level access may use these tools to
create privileged ghost containers, exec into other pods to steal service account tokens and secrets, pull
attacker-controlled images, and destroy evidence, all while remaining invisible to Kubernetes-level monitoring.
"""
false_positives = [
"""
Platform automation, node bootstrap, and legitimate break-glass admin sessions may use these CLIs with overlapping
arguments. Tune by parent process, user, or host role (worker vs bastion).
""",
]
from = "now-6m"
index = ["logs-cloud_defend.process*"]
language = "eql"
license = "Elastic License v2"
name = "Suspicious Container Runtime CLI Execution"
note = """## Triage and analysis

### Investigating Suspicious Container Runtime CLI Execution

Review the full argv list and working directory. Confirm whether the session is interactive, whether the image or bundle
referenced is trusted, and whether bind mounts or privileged flags target host paths such as `/`, `/etc`, or Docker
sockets.

### Possible investigation steps

- Reconstruct the container ID or snapshot key passed to `tasks`, `snapshots`, or `content` subcommands.
- Correlate with file, network, and Kubernetes audit activity for pulls from unusual registries or subsequent pod
changes.
- Check whether the parent should legitimately be kubelet, containerd, or systemd on that host class.

### Response and remediation

- If unauthorized, isolate the node, revoke credentials available to the session, and hunt for new privileged
workloads or image imports.
"""
references = [
"https://attack.mitre.org/techniques/T1609/",
"https://book.hacktricks.xyz/linux-hardening/privilege-escalation/containerd-ctr-privilege-escalation",
]
risk_score = 47
rule_id = "0398c0a2-1237-478e-84c4-84510f1925e6"
severity = "medium"
tags = [
"Data Source: Elastic Defend for Containers",
"Domain: Container",
"OS: Linux",
"Use Case: Threat Detection",
"Tactic: Execution",
"Resources: Investigation Guide",
]
timestamp_override = "event.ingested"
type = "eql"
query = '''
process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
(
(
process.name in ("ctr", "crictl", "nerdctl") and
(
(process.args == "tasks" and process.args == "exec") or
(process.args == "run" and process.args in ("--privileged", "--rm", "--mount", "--net-host", "--pid-host")) or
(process.args == "snapshots" and process.args == "mount")
)
) or
(
(process.executable like ("/dev/shm/*", "/tmp/*", "/var/tmp/*") or process.name : ".*") and
process.args like ("*containerd.sock*", "*k8s.io*")
)
) and
not process.parent.executable in (
"/usr/bin/kubelet", "/usr/local/bin/kubelet",
"/usr/bin/containerd", "/usr/sbin/containerd",
"/lib/systemd/systemd", "/usr/lib/systemd/systemd", "/sbin/init"
)
'''

[[rule.threat]]
framework = "MITRE ATT&CK"

[[rule.threat.technique]]
id = "T1609"
name = "Container Administration Command"
reference = "https://attack.mitre.org/techniques/T1609/"

[rule.threat.tactic]
id = "TA0002"
name = "Execution"
reference = "https://attack.mitre.org/tactics/TA0002/"

[[rule.threat]]
framework = "MITRE ATT&CK"

[[rule.threat.technique]]
id = "T1611"
name = "Escape to Host"
reference = "https://attack.mitre.org/techniques/T1611/"

[rule.threat.tactic]
id = "TA0004"
name = "Privilege Escalation"
reference = "https://attack.mitre.org/tactics/TA0004/"
122 changes: 122 additions & 0 deletions rules/linux/execution_container_runtime_cli_suspicious_arguments.toml
Original file line number Diff line number Diff line change
@@ -0,0 +1,122 @@
[metadata]
creation_date = "2026/04/29"
integration = ["endpoint", "auditd_manager"]
maturity = "production"
updated_date = "2026/04/29"

[rule]
author = ["Elastic"]
description = """
Detects execution of container runtime CLI tools (ctr, crictl, nerdctl) with arguments indicating container creation,
command execution inside existing containers, image manipulation, or host filesystem mounting. These tools interact
directly with the container runtime socket, bypassing the Kubernetes API server, RBAC authorization, admission webhooks,
pod security standards, and Kubernetes audit logging entirely. Attackers with host-level access may use these tools to
create privileged ghost containers, exec into other pods to steal service account tokens and secrets, pull
attacker-controlled images, and destroy evidence, all while remaining invisible to Kubernetes-level monitoring.
"""
false_positives = [
"""
Platform automation, node bootstrap, and legitimate break-glass admin sessions may use these CLIs with overlapping
arguments. Tune by parent process, user, or host role (worker vs bastion).
""",
]
from = "now-9m"
index = ["auditbeat-*", "logs-auditd_manager.auditd-*", "logs-endpoint.events.process*"]
language = "eql"
license = "Elastic License v2"
name = "Container Runtime CLI Execution with Suspicious Arguments"
note = """## Triage and analysis

### Investigating Container Runtime CLI Execution with Suspicious Arguments

Review the full argv list and working directory. Confirm whether the session is interactive, whether the image or bundle
referenced is trusted, and whether bind mounts or privileged flags target host paths such as `/`, `/etc`, or Docker
sockets.

### Possible investigation steps

- Reconstruct the container ID or snapshot key passed to `tasks`, `snapshots`, or `content` subcommands.
- Correlate with file, network, and Kubernetes audit activity for pulls from unusual registries or subsequent pod
changes.
- Check whether the parent should legitimately be kubelet, containerd, or systemd on that host class.

### Response and remediation

- If unauthorized, isolate the node, revoke credentials available to the session, and hunt for new privileged
workloads or image imports.
"""
references = [
"https://attack.mitre.org/techniques/T1609/",
"https://book.hacktricks.xyz/linux-hardening/privilege-escalation/containerd-ctr-privilege-escalation",
]
risk_score = 47
rule_id = "86b3a245-03de-49a5-ab57-ae44d8f064da"
setup = """## Setup

Requires process execution telemetry with arguments from **Elastic Defend** (`logs-endpoint.events.process*`) and/or
**Auditd Manager** / Auditbeat (`logs-auditd_manager.auditd-*`, `auditbeat-*`).

Ensure exec-related auditing captures full argv for `ctr`, `crictl`, and `nerdctl`. See
https://docs.elastic.co/integrations/auditd_manager
"""
severity = "medium"
tags = [
"Data Source: Auditd Manager",
"Data Source: Elastic Defend",
"Domain: Container",
"Domain: Endpoint",
"OS: Linux",
"Use Case: Threat Detection",
"Tactic: Execution",
"Resources: Investigation Guide",
]
timestamp_override = "event.ingested"
type = "eql"
query = '''
process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "executed") and
(
(
process.name in ("ctr", "crictl", "nerdctl") and
(
(process.args == "tasks" and process.args == "exec") or
(process.args == "run" and process.args in ("--privileged", "--rm", "--mount", "--net-host", "--pid-host")) or
(process.args == "snapshots" and process.args == "mount")
)
) or
(
(process.executable like ("/dev/shm/*", "/tmp/*", "/var/tmp/*") or process.name : ".*") and
process.args like ("*containerd.sock*", "k8s.io")
)
) and
not process.parent.executable in (
"/usr/bin/kubelet", "/usr/local/bin/kubelet",
"/usr/bin/containerd", "/usr/sbin/containerd",
"/lib/systemd/systemd", "/usr/lib/systemd/systemd", "/sbin/init"
)
'''

[[rule.threat]]
framework = "MITRE ATT&CK"

[[rule.threat.technique]]
id = "T1609"
name = "Container Administration Command"
reference = "https://attack.mitre.org/techniques/T1609/"

[rule.threat.tactic]
id = "TA0002"
name = "Execution"
reference = "https://attack.mitre.org/tactics/TA0002/"

[[rule.threat]]
framework = "MITRE ATT&CK"

[[rule.threat.technique]]
id = "T1611"
name = "Escape to Host"
reference = "https://attack.mitre.org/techniques/T1611/"

[rule.threat.tactic]
id = "TA0004"
name = "Privilege Escalation"
reference = "https://attack.mitre.org/tactics/TA0004/"
Loading