You are viewing docs on Elastic's new documentation system, currently in technical preview. For all other Elastic docs, visit elastic.co/guide.

Configure an integration policy for Elastic Defend

Configure settings on an Elastic Defend integration policy.

After the Elastic Agent is installed with the Elastic Defend integration, several protections features — including preventions against malware, ransomware, memory threats, and malicious behavior — are automatically enabled on protected hosts (most features require the Endpoint Protection Essentials or Endpoint Protection Complete project feature). If needed, you can update the integration policy to configure protection settings, event collection, antivirus settings, trusted applications, event filters, host isolation exceptions, and blocked applications to meet your organization's security needs.

You can also create multiple Elastic Defend integration policies to maintain unique configuration profiles. To create an additional Elastic Defend integration policy, go to Project settingsIntegrations, then follow the steps for adding the Elastic Defend integration.

Requirements

You must have the appropriate user role to configure an integration policy.

To configure an integration policy:

  1. Go to AssetsEndpointsPolicies to view the Policies page.

  2. Select the integration policy you want to configure. The integration policy configuration page appears.

  3. On the Policy settings tab, review and configure the following settings as appropriate:

  4. Click the Trusted applications, Event filters, Host isolation exceptions, and Blocklist tabs to review the endpoint policy artifacts assigned to this integration policy (for more information, refer to trusted applications, event filters, host isolation exceptions, and blocklist). On these tabs, you can:

    • Expand and view an artifact — Click the arrow next to its name.
    • View an artifact's details — Click the actions menu (), then select View full details.
    • Unassign an artifact — Click the actions menu (), then select Remove from policy. This does not delete the artifact; this just unassigns it from the current policy.
    • Assign an existing artifact — Click Assign x to policy, then select an item from the flyout. This view lists any existing artifacts that aren't already assigned to the current policy.

    Note

    You can't create a new endpoint policy artifact while configuring an integration policy. To create a new artifact, go to its main page in the Elastic Security app (for example, to create a new trusted application, go to AssetsEndpointsTrusted applications).

  5. Click the Protection updates tab to configure how Elastic Defend receives updates from Elastic with the latest threat detections, malware models, and other protection artifacts. Refer to Configure updates for protection artifacts for more information.

Malware protection

Elastic Defend malware prevention detects and stops malicious attacks by using a machine learning model that looks for static attributes to determine if a file is malicious or benign.

By default, malware protection is enabled on Windows, macOS, and Linux hosts. To disable malware protection, switch the Malware protections enabled toggle off.

Requirements

Malware protection requires the Endpoint Protection Essentials project feature.

Malware protection levels are:

  • Detect: Detects malware on the host and generates an alert. The agent will not block malware. You must pay attention to and analyze any malware alerts that are generated.

  • Prevent (Default): Detects malware on the host, blocks it from executing, and generates an alert.

Select Notify user to send a push notification in the host operating system when activity is detected or prevented. Notifications are enabled by default for the Prevent option.

Tip

Endpoint Protection Complete customers can customize these notifications using the Elastic Security {action} {filename} syntax.

Malware protection also allows you to manage a blocklist to prevent specified applications from running on hosts, extending the list of processes that Elastic Defend considers malicious. Use the Blocklist enabled toggle to enable or disable this feature for all hosts associated with the integration policy. To configure the blocklist, refer to Blocklist.

Manage quarantined files

When Prevent is enabled for malware protection, Elastic Defend will quarantine any malicious file it finds. Specifically Elastic Defend will remove the file from its current location, encrypt it with the encryption key ELASTIC, move it to a different folder, and rename it as a GUID string, such as 318e70c2-af9b-4c3a-939d-11410b9a112c.

The quarantine folder location varies by operating system:

  • macOS: /System/Volumes/Data/.equarantine
  • Linux: .equarantine at the root of the mount point of the file being quarantined
  • Windows - Elastic Defend versions 8.5 and later: [DriveLetter:]\.quarantine, unless the files are from the C: drive. These files are moved to C:\Program Files\Elastic\Endpoint\state\.equarantine.
  • Windows - Elastic Defend versions 8.4 and earlier: [DriveLetter:]\.quarantine, for any drive

To restore a quarantined file to its original state and location, add an exception to the rule that identified the file as malicious. If the exception would've stopped the rule from identifying the file as malicious, Elastic Defend restores the file.

You can access a quarantined file by using the get-file response action command in the response console. To do this, copy the path from the alert's Quarantined file path field (file.Ext.quarantine_path), which appears under Highlighted fields in the alert details flyout. Then paste the value into the --path parameter. This action doesn't restore the file to its original location, so you will need to do this manually.

Note

Response actions and the response console UI are Endpoint Protection Complete project features.

Ransomware protection

Behavioral ransomware prevention detects and stops ransomware attacks on Windows systems by analyzing data from low-level system processes. It is effective across an array of widespread ransomware families — including those targeting the system’s master boot record.

Requirements

Ransomware protection requires the Endpoint Protection Essentials project feature.

Ransomware protection levels are:

  • Detect: Detects ransomware on the host and generates an alert. Elastic Defend will not block ransomware. You must pay attention to and analyze any ransomware alerts that are generated.

  • Prevent (Default): Detects ransomware on the host, blocks it from executing, and generates an alert.

When ransomware protection is enabled, canary files placed in targeted locations on your hosts provide an early warning system for potential ransomware activity. When a canary file is modified, Elastic Defend immediately generates a ransomware alert. If prevent ransomware is active, Elastic Defend terminates the process that modified the file.

Select Notify user to send a push notification in the host operating system when activity is detected or prevented. Notifications are enabled by default for the Prevent option.

Tip

Endpoint Protection Complete customers can customize these notifications using the Elastic Security {action} {filename} syntax.

Memory threat protection

Memory threat protection detects and stops in-memory threats, such as shellcode injection, which are used to evade traditional file-based detection techniques.

Requirements

Memory threat protection requires the Endpoint Protection Essentials project feature.

Memory threat protection levels are:

  • Detect: Detects memory threat activity on the host and generates an alert. Elastic Defend will not block the in-memory activity. You must pay attention to and analyze any alerts that are generated.

  • Prevent (Default): Detects memory threat activity on the host, forces the process or thread to stop, and generates an alert.

Select Notify user to send a push notification in the host operating system when activity is detected or prevented. Notifications are enabled by default for the Prevent option.

Tip

Endpoint Protection Complete customers can customize these notifications using the Elastic Security {action} {rule} syntax.

Malicious behavior protection

Malicious behavior protection detects and stops threats by monitoring the behavior of system processes for suspicious activity. Behavioral signals are much more difficult for adversaries to evade than traditional file-based detection techniques.

Requirements

Malicious behavior protection requires the Endpoint Protection Essentials project feature.

Malicious behavior protection levels are:

  • Detect: Detects malicious behavior on the host and generates an alert. Elastic Defend will not block the malicious behavior. You must pay attention to and analyze any alerts that are generated.

  • Prevent (Default): Detects malicious behavior on the host, forces the process to stop, and generates an alert.

Select whether you want to use Reputation service for additional malware analysis. This service identifies malicious activity and false positives, and enriches alerts using data from various sources, such as VirusTotal and telemetry. For example, reputation service can detect suspicious downloads of binaries with low or malicious reputation.

Select Notify user to send a push notification in the host operating system when activity is detected or prevented. Notifications are enabled by default for the Prevent option.

Tip

Endpoint Protection Complete customers can customize these notifications using the Elastic Security {action} {rule} syntax.

Attack surface reduction

This section helps you reduce vulnerabilities that attackers can target on Windows endpoints.

Requirements

Attack surface reduction requires the Endpoint Protection Essentials project feature.

  • Credential hardening: Prevents attackers from stealing credentials stored in Windows system process memory. Turn on the toggle to remove any overly permissive access rights that aren't required for standard interaction with the Local Security Authority Subsystem Service (LSASS). This feature enforces the principle of least privilege without interfering with benign system activity that is related to LSASS.

Event collection

In the Settings section, select which categories of events to collect on each operating system. Most categories are collected by default, as seen below.

Register Elastic Security as antivirus (optional)

With Elastic Defend version 7.10 or later on Windows 7 or later, you can configure Elastic Security as your antivirus software by turning on Register as antivirus.

Note

Windows Server versions are not supported. Antivirus registration requires Windows Security Center, which is not included in Windows Server operating systems.

Advanced policy settings (optional)

Users with unique configuration and security requirements can select Show advanced settings to configure the policy to support advanced use cases. Hover over each setting to view its description.

Note

Advanced settings are not recommended for most users.

This section includes:

Save the general policy settings

After you have configured the general settings on the Policy settings tab, click Save. A confirmation message appears.

On this page