mirror of
https://github.com/elastic/detection-rules
synced 2026-06-08 14:00:08 +00:00
Samirbous
17c3be2689
* [New] Container Runtime CLI Execution with Suspicious Arguments
Detects ctr, crictl, or nerdctl on Linux when invoked with arguments associated with container lifecycle abuse, image staging, task or snapshot access, privileged or host-namespace flags, bind mounts, or CRI namespace targeting—patterns common during post-compromise container administration and breakout attempts.
* Update execution_container_runtime_cli_suspicious_arguments.toml
* Update execution_container_runtime_cli_suspicious_arguments.toml
* Update execution_container_runtime_cli_suspicious_arguments.toml
* Update execution_container_runtime_cli_suspicious_arguments.toml
* Update execution_container_runtime_cli_suspicious_arguments.toml
* Create execution_container_runtime_cli_suspicious_args.toml
* Apply suggestion from @terrancedejesus
Co-authored-by: Terrance DeJesus <99630311+terrancedejesus@users.noreply.github.com>
* Update execution_container_runtime_cli_suspicious_args.toml
* Update execution_container_runtime_cli_suspicious_arguments.toml
* Update execution_container_runtime_cli_suspicious_args.toml
* Update execution_container_runtime_cli_suspicious_args.toml
* Update execution_container_runtime_cli_suspicious_arguments.toml
* Update execution_container_runtime_cli_suspicious_arguments.toml
* Update execution_container_runtime_cli_suspicious_args.toml
* Update execution_container_runtime_cli_suspicious_arguments.toml
* Update rules/integrations/cloud_defend/execution_container_runtime_cli_suspicious_args.toml
Co-authored-by: Ruben Groenewoud <78494512+Aegrah@users.noreply.github.com>
---------
Co-authored-by: Terrance DeJesus <99630311+terrancedejesus@users.noreply.github.com>
Co-authored-by: Ruben Groenewoud <78494512+Aegrah@users.noreply.github.com>
(cherry picked from commit d3eb02d85e)
rules/
Rules within this folder are organized by solution or platform. The structure is flattened out, because nested file hierarchies are hard to navigate and find what you're looking for. Each directory contains several .toml files, and the primary ATT&CK tactic is included in the file name when it's relevant (i.e. windows/execution_via_compiled_html_file.toml)
| folder | description |
|---|---|
. |
Root directory where rules are stored |
apm/ |
Rules that use Application Performance Monitoring (APM) data sources |
cross-platform/ |
Rules that apply to multiple platforms, such as Windows and Linux |
integrations/ |
Rules organized by Fleet integration |
linux/ |
Rules for Linux or other Unix based operating systems |
macos/ |
Rules for macOS |
ml/ |
Rules that use machine learning jobs (ML) |
network/ |
Rules that use network data sources |
promotions/ |
Rules that promote external alerts into detection engine alerts |
windows/ |
Rules for the Microsoft Windows Operating System |
Integration specific rules are stored in the integrations/ directory:
| folder | integration |
|---|---|
aws/ |
Amazon Web Services (AWS) |
azure/ |
Microsoft Azure |
cyberarkpas/ |
Cyber Ark Privileged Access Security |
endpoint/ |
Elastic Endpoint Security |
gcp/ |
Google Cloud Platform (GCP) |
google_workspace/ |
Google Workspace (formerly GSuite) |
o365/ |
Microsoft Office |
okta/ |
Okta |