Study guide

13.3 Elastic Defend Administration & Endpoint Policy Controls

Elastic Certified SIEM Analyst Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Study Strategy

1.1 Elastic Certified SIEM Analyst Exam Facts, Objectives & Study Plan

2 Chapter 2: Elastic Stack Architecture & SIEM Foundations

2.1 Elastic Stack Architecture for Security Operations 2.2 Telemetry Ingestion Architecture & Data Pipelines 2.3 Security Data Storage, Data Streams & ILM

3 Chapter 3: Elastic Common Schema (ECS) & Ingestion Normalization

3.1 ECS Structure, Core Principles & Essential Field Sets 3.2 Ingest Pipelines, Processors & Normalization Workflows 3.3 Fleet Server & Elastic Agent Integration Management

4 Chapter 4: Discover, Data Views & Security Query Languages

4.1 Kibana Discover, Security Data Views & Runtime Fields 4.2 Kibana Query Language (KQL) & Lucene for SecOps 4.3 ES|QL for Multi-Stage Security Analysis

5 Chapter 5: Security Visualizations & Threat Analytics

5.1 Metric, Aggregation & Histogram Visualizations for SOC 5.2 Data Tables, Heatmaps & Specialized Security Charts 5.3 Elastic Maps & Geospatial Telemetry Analysis

6 Chapter 6: Kibana Lens for Security Workflows

6.1 Lens Architecture & Multi-Layer Telemetry Visualizations 6.2 Lens Formulas, Ratios & Anomaly Baseline Metrics 6.3 Operationalizing Lens in SOC Triage & Drilldowns

7 Chapter 7: Security Dashboards & SOC Operations

7.1 Security Dashboard Architecture & SOC Layout Design 7.2 Interactive Controls, Time Sync & Cross-Filtering 7.3 Dashboard Exporting, Reporting & Spaces Sharing

8 Chapter 8: The Elastic Security App: Capabilities, Explore & Dashboards

8.1 Security App Capabilities & the Explore Pages (Hosts, Network, Users) 8.2 Monitoring with the Security App Dashboards

9 Chapter 9: Elastic Security Detection Engine & Core Rules

9.1 Detection Engine Architecture & Prebuilt Rule Management 9.2 Custom Query & Threshold Detection Rules 9.3 Event Correlation Rules with Event Query Language (EQL)

10 Chapter 10: Advanced Detection Rules, ML & Rule Tuning

10.1 Threat Intelligence & Indicator Match Rules 10.2 New Terms, ES|QL & Machine Learning Detection Rules 10.3 Detection Rule Tuning, Exceptions & Alert Suppression

11 Chapter 11: Alert Triage, Timelines & Investigation Workflows

11.1 Alert Triage Workflow & the Alert Details Flyout 11.2 Elastic Security Timeline & Timeline Templates 11.3 Visual Event Analyzer & Session View Forensics

12 Chapter 12: Case Management, Integrations & AI Assistant

12.1 Elastic Security Case Management & Triage Workflows 12.2 Case Connectors & External Incident Escalation 12.3 Elastic AI Assistant for Security & Attack Discovery

13 Chapter 13: Security Administration, RBAC & Kibana Spaces

13.1 Kibana Spaces for SOC Multitenancy & Segmentation 13.2 Role-Based Access Control, Feature Privileges & Index Security 13.3 Elastic Defend Administration & Endpoint Policy Controls

14 Chapter 14: End-to-End Threat Hunting & Incident Investigation Capstone

14.1 Hypothesis-Driven Threat Hunting & Baselining in Elastic 14.2 Investigating Lateral Movement & Credential Access Campaigns 14.3 Data Exfiltration, C2 Detection & Incident Reconstruction

13.3 Elastic Defend Administration & Endpoint Policy Controls

Key Takeaways Explain This Topic AI

Elastic Defend runs inside Elastic Agent and is configured through Fleet integration policies, with malware, ransomware (Windows), memory threat and malicious behavior protections set to Detect or Prevent.

Trusted applications stop Elastic Endpoint from monitoring a process at all, an intentional blind spot meant for conflicting security software.

Endpoint alert exceptions suppress alerts and preventions for a verified false positive while Defend keeps monitoring everything else.

Event filters keep matching events out of Elasticsearch to save storage, but Elastic Endpoint still analyzes those events for threats.

Host isolation (Platinum or higher) blocks a host from talking to other hosts while it still sends data to Elasticsearch and Kibana, and host isolation exceptions allow specific IPs.

Last updated: September 2026

Endpoint security represents both the frontline defense and the highest-volume telemetry source in modern enterprise security architectures. The Elastic Defend integration (formerly Endpoint Security) combines kernel-level behavioral monitoring, signatureless machine learning, anti-ransomware defenses, and real-time containment into the unified Elastic Agent. Administering Elastic Defend requires balancing aggressive threat prevention against operational stability: tuning out benign high-volume events, whitelisting proprietary enterprise software, generating diagnostic bundles during operational anomalies, and executing emergency host isolation during active breaches.

1. Elastic Defend Architecture & Fleet Policy Orchestration

Unlike legacy endpoint architectures that rely on separate standalone agents for EDR, log forwarding, and osquery, Elastic Defend operates as an integrated extension of the Unified Elastic Agent :

Fleet Control Plane: Defend configurations are managed entirely through Fleet Agent Policies in Kibana. When an administrator modifies a Defend integration policy (e.g., toggling Ransomware protection from Detect to Prevent), Fleet Server delivers the updated policy to enrolled agents over their outbound HTTPS check-in connection (port 8220 by default).

User-Space & Kernel Architecture: Elastic Defend consists of an endpoint daemon running in user-space coupled with platform-specific kernel drivers:

Windows: A kernel driver that receives process, file, network and registry events.

macOS: Apple's Endpoint Security framework through a system extension (which needs Full Disk Access).

Linux: Kernel instrumentation such as eBPF (with a tracefs fallback on older kernels) and fanotify for file scanning.

2. Protection Engines and Operating Modes

Elastic Defend's policy has four primary protections (plus attack surface reduction settings such as credential hardening on Windows). Each can be independently set to Detect or Prevent (or turned off). Ransomware protection applies to Windows, and the presets other than Data Collection turn on all preventions by default: +-------------------------------------------------------------------------+

  • | Elastic Defend Integration |
  • +--------------------+--------------------+-------------------------------+|
  • | Protection Engine | Operating Mode | Primary SecOps Detection Scope |
  • +--------------------+--------------------+-------------------------------+|
  • | Malware Protection | Detect / Prevent | Malicious binaries, DLLs via signatures and ML |
  • | Ransomware Protect | Detect / Prevent | Mass encryption, canary tampering, VSS purge |
  • | Memory Threat Prot | Detect / Prevent | Shellcode, reflective DLLs, process hollowing |
  • | Malicious Behavior | Detect / Prevent | LOLBAS abuse, suspicious process trees, LSASS |
  • +--------------------+--------------------+-------------------------------+|
  • Operating Modes: Detect vs. Prevent

Detect Mode: When an engine detects a threat, it generates a security alert, records full event metadata (process ancestry, hashes, command lines), and transmits the telemetry to Elasticsearch. However, the offending process is permitted to continue execution. Detect mode is critical during initial baselining or when rolling out policies to mission-critical servers, allowing engineers to verify that line-of-business applications are not disrupted.

Prevent Mode: When a threat is detected, Defend blocks it, for example by stopping the offending process or preventing the malicious file from running, and publishes an alert documenting the prevention action.

Detailed Engine Capabilities

Malware Protection: Scans executables, dynamic libraries, and scripts upon creation, modification, or execution. Uses a local signature engine combined with on-device machine learning models to detect known and novel malware variants.

Ransomware Protection: Monitors file system activity for behavioral patterns characteristic of ransomware, including rapid file encryption velocities, modification of high-entropy files, tampering with canary files placed in sensitive directories, and execution of volume shadow copy deletion commands ( vssadmin.exe delete shadows /all /quiet ).

Memory Threat Protection: Defends against advanced in-memory exploitation techniques that bypass disk-based scanners. Detects shellcode injection, process hollowing, reflective DLL loading, thread execution hijacking, and asynchronous procedure call (APC) injection.

Malicious Behavior Protection: Analyzes live process behaviors targeting living-off-the-land binaries (LOLBAS). Detects suspicious child process relationships (e.g., word.exe spawning powershell.exe with base64 encoded parameters) and attempts to dump credentials from the Local Security Authority Subsystem Service ( lsass.exe ).

3. Diagnostic Bundles & Endpoint Troubleshooting

When an Elastic Agent exhibits communication issues, high resource consumption, or driver conflicts with third-party software, engineers must collect forensic diagnostic data without manual SSH or RDP sessions.

Generating Diagnostic Bundles via Fleet

In Kibana, open Fleet → Agents .

Locate the affected host, click the Actions menu ( ... ), and select Request diagnostics .zip .

Fleet Server dispatches an instruction to the endpoint. The agent collects:

Active configuration JSON files ( elastic-agent.yml , policy snapshots).

Agent daemon logs ( elastic-agent.log ) and Defend service logs ( endpoint-security.log ).

Driver operational states, kernel extension statuses, and crash dump files.

System resource utilization metrics (CPU, memory, handle counts) and network socket tables.

The endpoint compresses the diagnostic payload into a zip or tar archive and streams it back through Fleet Server. The administrator can download the bundle directly from the Kibana interface for analysis.

4. Policy Tuning: Endpoint Artifacts and Exceptions

Elastic's Optimize Elastic Defend guidance separates four tools. Choosing the wrong one either leaves noise or creates a blind spot.

Trusted Applications

Purpose: Resolve conflicts and performance problems with other software, usually other antivirus or endpoint security products.

Effect: Elastic Endpoint stops monitoring the process for threats and generates no events for it, except process events used internally for visualizations. This is an intentional blind spot : attackers can abuse trusted processes, for example through DLL side-loading. Use trusted applications sparingly.

Matching: One field type per entry: hash (MD5, SHA-1 or SHA-256), full path (wildcards allowed with matches ), or, on Windows, the signer name. Entries apply globally or, with Platinum or higher, to specific Elastic Defend policies.

Endpoint Alert Exceptions

Purpose: Stop false-positive alerts and preventions for a specific, verified behavior.

Effect: Elastic Endpoint does not generate the alert or stop the process when the exception matches. It keeps monitoring everything else, and checks exceptions early, which can also save CPU. Add one from an Endpoint alert with Take action → Add Endpoint exception .

Event Filters

Purpose: Reduce storage by keeping noisy, benign event documents out of Elasticsearch.

Effect: Matching events are not written to Elasticsearch , but Elastic Endpoint still monitors them for threats . Event filters do not lower CPU use on the endpoint.

Blocklist

Purpose: Extend protection by preventing known-bad applications (by hash, path or signer) from running.

Effect: Not intended for blocking benign software for non-security reasons.

( Host isolation exceptions are a fifth artifact type. They list IP addresses that isolated hosts may still reach.)

5. Host Isolation Mechanics & Emergency Network Containment

During an active incident, such as an adversary running a reverse shell or lateral movement tools, responders must contain the host without losing visibility. +-------------------------------------------------------------------------+

  • | Host Isolation Engaged |
  • +-------------------------------------------------------------------------+
  • | Attacker C2 traffic -----> [ BLOCKED ] |
  • | Lateral SMB / RDP to peers -----> [ BLOCKED ] |
  • | Internal subnet scans -----> [ BLOCKED ] |
  • | |
  • | Data to Elasticsearch/Kibana <====> [ ALLOWED - telemetry continues ] |
  • | Host isolation exception IPs <====> [ ALLOWED - e.g. VPN or DNS host ] |
  • +-------------------------------------------------------------------------+
  • Mechanism of Host Isolation

When an analyst chooses Isolate host from the alert details flyout, the Endpoints page, or the response console ( isolate , Enterprise):

Requirements: Host isolation needs a Platinum or Enterprise subscription and the Host Isolation privilege. It is supported on Windows, macOS and supported Linux distributions running Elastic Defend.

Network Blocking: The endpoint is blocked from communicating with other hosts on the network, which cuts C2 channels and stops lateral spread.

Preserved Visibility: Isolated hosts can still send data to Elasticsearch and Kibana , so responders keep receiving telemetry and can continue response actions.

Exceptions: Host isolation exceptions list specific IP addresses that isolated hosts may still reach, for example a VPN concentrator or a DNS server.

Release: When remediation is finished, responders choose Release host . Every isolate and release action is recorded in the host's response actions history, and an Isolated status appears next to the agent status.

6. Comprehensive Tuning Artifact Comparison

Tool What It Changes Protection Events in Elasticsearch Typical Use

Trusted application Elastic Endpoint stops monitoring the process None for that process (intentional blind spot) Only internal process events Another antivirus or EDR product that conflicts with Defend

Endpoint alert exception Suppresses alerts and preventions for a matching behavior Still active for everything else Unchanged A verified false positive, such as an in-house app blocked by malicious behavior protection

Event filter Keeps matching events out of Elasticsearch Unchanged : events are still analyzed Not stored High-volume benign activity, such as backup software file reads

Blocklist Prevents specified applications from running Extended Unchanged Known malware not yet caught by other protections

Host isolation exception Allows specific IPs while a host is isolated Not applicable Unchanged Keeping a VPN or DNS server reachable during isolation

Loading diagram... Elastic Defend Endpoint Protection & Host Isolation Lifecycle