Skip to content

[New] Nsenter to PID 1 Namespace via Auditd/D4C#5988

Merged
Samirbous merged 13 commits into
mainfrom
nsenter_runc
May 2, 2026
Merged

[New] Nsenter to PID 1 Namespace via Auditd/D4C#5988
Samirbous merged 13 commits into
mainfrom
nsenter_runc

Conversation

@Samirbous

@Samirbous Samirbous commented Apr 27, 2026

Copy link
Copy Markdown
Contributor

we have an existing rule (compatible with Elastic Defend - uses `process.entry_leader.entry_meta.type == "container").

Two new rules compatible with the auditd and D4C integrations.

image

we have an existing rule https://github.com/elastic/detection-rules/blob/0f521a0848420844f3af383f1dee8481d41b2e5b/rules/linux/privilege_escalation_docker_escape_via_nsenter.toml#L15 (compatible only with Elastic Defend `process.entry_leader.entry_meta.type == "container"`).

This rule is compatible with the auditd integration and scoped to Init/systemd PID namespace commonly targeted for container escape.
@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 27, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Nsenter to PID 1 Namespace via Auditd (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented Apr 27, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Nsenter Execution with Target Flag Inside Container (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Nsenter to PID 1 Namespace via Auditd (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@Samirbous Samirbous changed the title [New] Nsenter to PID 1 Namespace via Auditd [New] Nsenter to PID 1 Namespace via Auditd/D4C Apr 27, 2026
@Samirbous Samirbous requested a review from Aegrah April 27, 2026 16:04
@tradebot-elastic

tradebot-elastic commented Apr 27, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Nsenter Execution with Target Flag Inside Container (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Nsenter to PID 1 Namespace via Auditd (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented Apr 27, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Nsenter Execution with Target Flag Inside Container (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Nsenter to PID 1 Namespace via Auditd (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

Comment thread rules/linux/privilege_escalation_auditd_nsenter_target_host_pid.toml Outdated

@terrancedejesus terrancedejesus 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.

Looks good. Nsenter Execution with Target Flag Inside Container I think we can remove FPs for debugging tools after it ships.

Great stuff!

@tradebot-elastic

tradebot-elastic commented May 1, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Nsenter Execution with Target Flag Inside Container (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Nsenter to PID 1 Namespace via Auditd (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
  • ❌ Nsenter Execution with Target Flag Inside Container (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Nsenter to PID Namespace via Auditd (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

Comment thread rules/linux/privilege_escalation_auditd_nsenter_target_host_pid.toml Outdated
…d.toml

Co-authored-by: Mika Ayenson, PhD <Mikaayenson@users.noreply.github.com>
@tradebot-elastic

tradebot-elastic commented May 2, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Nsenter Execution with Target Flag Inside Container (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Nsenter to PID Namespace via Auditd (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 2, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Nsenter Execution with Target Flag Inside Container (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Nsenter to PID Namespace via Auditd (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 2, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Nsenter Execution with Target Flag Inside Container (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Nsenter to PID Namespace via Auditd (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 2, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Nsenter Execution with Target Flag Inside Container (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Nsenter to PID Namespace via Auditd (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 2, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Nsenter Execution with Target Flag Inside Container (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Nsenter to PID Namespace via Auditd (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 2, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Nsenter Execution with Target Flag Inside Container (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Nsenter to PID Namespace via Auditd (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic

tradebot-elastic commented May 2, 2026

Copy link
Copy Markdown

⛔️ Test failed

Results
  • ❌ Nsenter Execution with Target Flag Inside Container (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
  • ❌ Nsenter to PID Namespace via Auditd (kuery)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@Samirbous Samirbous merged commit 838e926 into main May 2, 2026
13 checks passed
@Samirbous Samirbous deleted the nsenter_runc branch May 2, 2026 13:56
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.

4 participants