IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Event capture and Elastic Defend Elastic Endpoint self-protection features »
Elastic Docs ›Elastic Security Solution [8.16] ›Manage Elastic Defend

Allowlist Elastic Endpoint in third-party antivirus apps

edit

Allowlist Elastic Endpoint in third-party antivirus apps

edit

If you use other antivirus (AV) software along with Elastic Defend, you may need to add the other system as a trusted application in the Elastic Security app. Refer to Trusted applications for more information.

Third-party antivirus (AV) applications may identify the expected behavior of Elastic Endpoint—the installed component that performs Elastic Defend’s threat monitoring and prevention—as a potential threat. Add Elastic Endpoint’s digital signatures and file paths to your AV software’s allowlist to ensure Elastic Endpoint continues to function as intended. We recommend you allowlist both the file paths and digital signatures, if applicable.

Your AV software may refer to allowlisted processes as process exclusions, ignored processes, or trusted processes. It is important to note that file, folder, and path-based exclusions/exceptions are distinct from trusted applications and will not achieve the same result. This page explains how to ignore actions taken by processes, not how to ignore the files that spawned those processes.

Allowlist Elastic Endpoint on Windows

edit

File paths:

  • ELAM driver: c:\Windows\system32\drivers\ElasticElam.sys
  • Driver: c:\Windows\system32\drivers\elastic-endpoint-driver.sys

  • Executable: c:\Program Files\Elastic\Endpoint\elastic-endpoint.exe

    The executable runs as elastic-endpoint.exe.

Digital signatures:

  • Elasticsearch, Inc.
  • Elasticsearch B.V.

For additional information about allowlisting on Windows, refer to Trusting Elastic Defend in other software.

Allowlist Elastic Endpoint on macOS

edit

File paths:

  • System extension (recursive directory structure): /Applications/ElasticEndpoint.app/

    The system extension runs as co.elastic.systemextension.

  • Executable: /Library/Elastic/Endpoint/elastic-endpoint.app/Contents/MacOS/elastic-endpoint

    The executable runs as elastic-endpoint.

Digital signatures:

  • Authority/Developer ID Application: Elasticsearch, Inc (2BT3HPN62Z)
  • Team ID: 2BT3HPN62Z

Allowlist Elastic Endpoint on Linux

edit

File path:

  • Executable: /opt/Elastic/Endpoint/elastic-endpoint

    The executable runs as elastic-endpoint.

« Event capture and Elastic Defend Elastic Endpoint self-protection features »