[8.1] New page about allowlisting Elastic Endpoint in 3rd-party AV so…

…ftware (backport #4439) (#4516) * New page about allowlisting Elastic Endpoint in 3rd-party AV software (#4439) * Adds new page about allowlisting Elastic Endpoint * Update docs/management/admin/allowlist-endpoint-3rd-party-av.asciidoc Co-authored-by: Daniel Ferullo <[email protected]> * Update docs/management/admin/allowlist-endpoint-3rd-party-av.asciidoc Co-authored-by: Daniel Ferullo <[email protected]> * incorporates feedback * incorporates Gabriel Landau's feedback --------- Co-authored-by: Daniel Ferullo <[email protected]> (cherry picked from commit 424e4be) # Conflicts: # docs/management/manage-intro.asciidoc * fix merge conflict --------- Co-authored-by: Benjamin Ironside Goldstein <[email protected]> Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
elastic · Dec 31, 2023 · f533e51 · f533e51
1 parent 0e74edf
commit f533e51
Show file tree

Hide file tree

Showing 2 changed files with 55 additions and 0 deletions.
diff --git a/docs/management/admin/allowlist-endpoint-3rd-party-av.asciidoc b/docs/management/admin/allowlist-endpoint-3rd-party-av.asciidoc
@@ -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`.
diff --git a/docs/management/manage-intro.asciidoc b/docs/management/manage-intro.asciidoc
@@ -9,3 +9,4 @@ include::{security-docs-root}/docs/management/admin/host-isolation-ov.asciidoc[l
 include::{security-docs-root}/docs/management/admin/trusted-apps.asciidoc[leveloffset=+1]
 include::{security-docs-root}/docs/management/admin/event-filters.asciidoc[leveloffset=+1]
 include::{security-docs-root}/docs/management/admin/host-isolation-exceptions.asciidoc[leveloffset=+1]
+include::{security-docs-root}/docs/management/admin/allowlist-endpoint-3rd-party-av.asciidoc[leveloffset=+1]