838e926058
* [New] Nsenter to PID 1 Namespace via Auditd 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. * Create privilege_escalation_nsenter_execution_inside_container.toml * Update privilege_escalation_auditd_nsenter_target_host_pid.toml * Update privilege_escalation_auditd_nsenter_target_host_pid.toml * Update privilege_escalation_auditd_nsenter_target_host_pid.toml * Update privilege_escalation_auditd_nsenter_target_host_pid.toml * Update rules/linux/privilege_escalation_auditd_nsenter_target_host_pid.toml Co-authored-by: Mika Ayenson, PhD <Mikaayenson@users.noreply.github.com> * Update privilege_escalation_nsenter_execution_inside_container.toml * Update privilege_escalation_auditd_nsenter_target_host_pid.toml --------- Co-authored-by: Mika Ayenson, PhD <Mikaayenson@users.noreply.github.com>