Elastic Details Defend for Containers Runtime Detection in Stack 9.3.0

· Original article ↗

Summary

Elastic’s Defend for Containers in Stack 9.3.0 collects container process and write-oriented file telemetry with Kubernetes context for policy-based detection. The guide covers setup, policies, event fields and Beta limitations, including gaps in network and read-only-

Key points

  • Defend for Containers is a Beta integration in Elastic Stack 9.3.0, deployed through Elastic Agent to collect container runtime telemetry.
  • It captures process activity and write-oriented file events, enriching them with container, host and Kubernetes orchestration context.
  • Policies use selectors to match activity and responses to log, alert or block it; defaults log fork/exec events and alert on executable creation or modification.
  • Pre-built detection rules for container and Kubernetes threats are available in Elastic Security on version 9.3.0 or later.
  • Process lineage, interactive-session indicators, Linux capabilities, container security context and orchestration metadata can support workload-aware detections.
  • The Beta formally supports Amazon EKS and Google GKE; Azure AKS is not officially supported and currently lacks file-event telemetry.
  • The integration does not capture network events or read-only file access; the article recommends validating policies in monitoring mode before enabling blocking.

Article Details

Defense Focus
Detect and respond to suspicious runtime behavior in Linux containers by combining process and file telemetry with container, privilege, host, and Kubernetes workload context.
Detection Methods
  • Monitor fork and exec activity, process arguments and lineage, and interactive-session indicators to identify unusual execution chains inside containers.
  • Detect executable creation or modification and other write-oriented file activity, scoped by file paths and container or Kubernetes selectors.
  • Correlate process activity with container privilege state and effective or permitted Linux capabilities to prioritize high-risk behavior.
  • Use container image, namespace, pod name, labels, and host PID namespace to scope detections and investigate runtime events.
  • Enable the pre-built container detection rules and validate their matches against observed workload behavior.
Data Sources
  • Defend for Containers process events, including fork, exec, and process lifecycle and lineage fields.
  • Defend for Containers file events, including write-intent opens, creation, modification, rename, permission changes, and deletion; read-only file access is not captured.
  • Container, host, and Kubernetes orchestration metadata, including image, security context, namespace, pod, labels, and host PID namespace.
  • Kernel tracepoint context for process creation and execution.
  • Complementary network telemetry from Network Packet Capture or Packetbeat, because Defend for Containers does not capture network events.
Rule Types
  • Defend for Containers selector-and-response policies configured in YAML, with log, alert, or block actions.
  • Elastic Security pre-built container and Kubernetes detection rules.
  • KQL and ES|QL queries for analyzing Defend for Containers events.
Platforms
  • Kubernetes clusters; formal support is stated for Amazon EKS and Google GKE, while Azure AKS is not officially supported and lacks file-event telemetry.
  • Elastic Stack 9.3.0 or later for the described integration and pre-built rules.
Defensive Actions
  • Deploy Defend for Containers through Elastic Agent and configure the required Kubernetes security context capabilities: BPF, PERFMON, and SYS_RESOURCE.
  • Enable the pre-built detection rules in Elastic Security on version 9.3.0 or later.
  • Start policies in monitoring or log-only mode, review events in Elasticsearch, and refine selectors against normal workload behavior.
  • Test blocking in a staging or test cluster, then move gradually from logging to alerting and blocking to reduce the risk of disrupting workloads.
  • Use complementary network telemetry for outbound connections, lateral movement, or exfiltration investigations.
  • Account for beta limitations: do not rely on this integration alone to detect read-only secret or token access, and consider missing file telemetry when evaluating Azure AKS deployments.

MITRE ATT&CK

Vendors

Products

Amazon Elastic Kubernetes ServiceBeta limitations: formal support for Amazon EKS and Google GKE, partial/unsupported AKS telemetry (no file events), and no built-in network event capture—complementary network data sources are recommended.Azure Kubernetes ServiceWhile the integration can be deployed on Azure AKS, this configuration is not officially supported.Defend for ContainersDefend for Containers (Elastic Stack 9.3.0) is a runtime security integration that captures container process and file telemetry, enriches events with container and orchestration context, and provides a policy-drivenElastic AgentThe integration ships pre-built detection rules, supports Elastic Agent deployment on clusters (EKS/GKE; limited AKS support), and emphasizes runtime behavior such as interactive execution, file modifications,Elastic SecurityPre-built detection rules tailored to container/Kubernetes threats are available in Elastic Security (9.3.0+), and policies should be validated in monitoring mode before enabling blocking to avoid disrupting workloads.Elastic StackDefend for Containers (Elastic Stack 9.3.0) is a runtime security integration that captures container process and file telemetry, enriches events with container and orchestration context, and provides a policy-drivenGoogle GKEBeta limitations: formal support for Amazon EKS and Google GKE, partial/unsupported AKS telemetry (no file events), and no built-in network event capture—complementary network data sources are recommended.Network Packet Capturenetwork movement, or data exfiltration must rely on complementary data sources, such as the Network Packet Capture integration or Packetbeat integrations, rather than on Defend for Containers telemetry alone.Packetbeatexfiltration must rely on complementary data sources, such as the Network Packet Capture integration or Packetbeat integrations, rather than on Defend for Containers telemetry alone.

Related Articles