Skip to content

[New] Container Runtime CLI Execution with Suspicious Arguments#6009

Merged
Samirbous merged 23 commits into
mainfrom
ctr_r
May 5, 2026
Merged

[New] Container Runtime CLI Execution with Suspicious Arguments#6009
Samirbous merged 23 commits into
mainfrom
ctr_r

Conversation

@Samirbous

Copy link
Copy Markdown
Contributor

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.

image

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.
@github-actions

Copy link
Copy Markdown
Contributor

Rule: New - Guidelines

These guidelines serve as a reminder set of considerations when proposing a new rule.

Documentation and Context

  • Detailed description of the rule.
  • List any new fields required in ECS/data sources.
  • Link related issues or PRs.
  • Include references.

Rule Metadata Checks

  • creation_date matches the date of creation PR initially merged.
  • min_stack_version should support the widest stack versions.
  • name and description should be descriptive and not include typos.
  • query should be inclusive, not overly exclusive, considering performance for diverse environments. Non ecs fields should be added to non-ecs-schema.json if not available in an integration.
  • min_stack_comments and min_stack_version should be included if the rule is only compatible starting from a specific stack version.
  • index pattern should be neither too specific nor too vague, ensuring it accurately matches the relevant data stream (e.g., use logs-endpoint.process-* for process data).
  • integration should align with the index. If the integration is newly introduced, ensure the manifest, schemas, and new_rule.yaml template are updated.
  • setup should include the necessary steps to configure the integration.
  • note should include any additional information (e.g. Triage and analysis investigation guides, timeline templates).
  • tags should be relevant to the threat and align/added to the EXPECTED_RULE_TAGS in the definitions.py file.
  • threat, techniques, and subtechniques should map to ATT&CK always if possible.

New BBR Rules

  • building_block_type should be included if the rule is a building block and the rule should be located in the rules_building_block folder.
  • bypass_bbr_timing should be included if adding custom lookback timing to the rule.

Testing and Validation

  • Provide evidence of testing and detecting the expected threat.
  • Check for existence of coverage to prevent duplication.

@tradebot-elastic

tradebot-elastic commented Apr 29, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented Apr 29, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented Apr 29, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented Apr 29, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 1, 2026

Copy link
Copy Markdown

Test succeeded

Results

@tradebot-elastic

tradebot-elastic commented May 1, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 1, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 1, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

Comment thread rules/linux/execution_container_runtime_cli_suspicious_arguments.toml Outdated
Comment thread rules/linux/execution_container_runtime_cli_suspicious_arguments.toml Outdated
@Samirbous Samirbous requested a review from imays11 May 4, 2026 20:52
@tradebot-elastic

tradebot-elastic commented May 5, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 5, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 5, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 5, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 5, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 5, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 5, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 5, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@Aegrah Aegrah left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the decreased severity and rule rewrite it LGTM!

Samirbous and others added 2 commits May 5, 2026 17:38
…i_suspicious_args.toml

Co-authored-by: Ruben Groenewoud <78494512+Aegrah@users.noreply.github.com>
@tradebot-elastic

tradebot-elastic commented May 5, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 5, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 5, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 5, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Suspicious Container Runtime CLI Execution (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Container Runtime CLI Execution with Suspicious Arguments (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@Samirbous Samirbous merged commit d3eb02d into main May 5, 2026
13 checks passed
@Samirbous Samirbous deleted the ctr_r branch May 5, 2026 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants