Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.7] New page about allowlisting Elastic Endpoint in 3rd-party AV software (backport #4439) #4510

Merged
merged 1 commit into from
Dec 21, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
54 changes: 54 additions & 0 deletions docs/management/admin/allowlist-endpoint-3rd-party-av.asciidoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
[[allowlist-endpoint-3rd-party-av-apps]]
= Allowlist Elastic Endpoint in third-party antivirus apps

Third-party antivirus (AV) applications may identify the expected behavior of {elastic-endpoint} 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.

NOTE: 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-endpoint-on-windows]]
[discrete]
== Allowlist {elastic-endpoint} on Windows

File paths:

* ELAM driver: `c:\Windows\system32\drivers\elastic-endpoint-driver.sys`
* Driver: `c:\Windows\system32\drivers\ElasticElam.sys`
* Executable: `c:\Program Files\Elastic\Endpoint\elastic-endpoint.exe`
+
NOTE: The executable runs as `elastic-endpoint.exe`.

Digital signatures:

* `Elasticsearch, Inc.`
* `Elasticsearch B.V.`

For additional information about allowlisting on Windows, refer to https://github.com/elastic/endpoint/blob/main/PerformanceIssues-Windows.md#trusting-elastic-defend-in-other-software[Trusting Elastic Defend in other software].

[[allowlist-endpoint-on-macos]]
[discrete]
== Allowlist {elastic-endpoint} on macOS

File paths:

* System extension (recursive directory structure): `/Applications/ElasticEndpoint.app/`
+
NOTE: The system extension runs as `co.elastic.systemextension`.

* Executable: `/Library/Elastic/Endpoint/elastic-endpoint.app/Contents/MacOS/elastic-endpoint`
+
NOTE: The executable runs as `elastic-endpoint`.

Digital signatures:

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

[[allowlist-endpoint-on-linux]]
[discrete]
== Allowlist {elastic-endpoint} on Linux

File path:

* Executable: `/opt/Elastic/Endpoint/elastic-endpoint`
+
NOTE: The executable runs as `elastic-endpoint`.
1 change: 1 addition & 0 deletions docs/management/manage-intro.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -14,3 +14,4 @@ include::{security-docs-root}/docs/management/admin/event-filters.asciidoc[level
include::{security-docs-root}/docs/management/admin/host-isolation-exceptions.asciidoc[leveloffset=+1]
include::{security-docs-root}/docs/management/admin/blocklist.asciidoc[leveloffset=+1]
include::{security-docs-root}/docs/management/admin/endpoint-artifacts.asciidoc[leveloffset=+1]
include::{security-docs-root}/docs/management/admin/allowlist-endpoint-3rd-party-av.asciidoc[leveloffset=+1]