[8.0] Adds Allowlist Elastic Endpoint in third-party antivirus apps p…

…age to serverless docs (backport #5639) (#5655) * Adds Allowlist Elastic Endpoint in third-party antivirus apps page to serverless docs (#5639) * Adds Allowlist Elastic Endpoint in third-party antivirus apps page to serverless docs * Adds page description * Apply suggestions from code review Co-authored-by: Joe Peeples <[email protected]> * Removes div id * Adds note to allowlist pages --------- Co-authored-by: Joe Peeples <[email protected]> (cherry picked from commit f8e7ca6) # Conflicts: # docs/management/admin/trusted-apps.asciidoc # docs/serverless/edr-manage/trusted-apps-ov.mdx # docs/serverless/serverless-security.docnav.json * Delete docs/serverless directory and its contents * Resolves conflict * Removes unneccesary para and renames integration --------- Co-authored-by: natasha-moore-elastic <[email protected]> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: natasha-moore-elastic <[email protected]>
elastic · Aug 2, 2024 · 3aaaad8 · 3aaaad8
1 parent bdd1856
commit 3aaaad8
Show file tree

Hide file tree

Showing 2 changed files with 4 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
@@ -1,6 +1,8 @@
 [[allowlist-endpoint-3rd-party-av-apps]]
 = Allowlist Elastic Endpoint in third-party antivirus apps
 
+NOTE: If you use other antivirus (AV) software along with {endpoint-sec}, you may need to add the other system as a trusted application in the {security-app}. Refer to <<trusted-apps-ov>> for more information.
+
 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.

diff --git a/docs/management/admin/trusted-apps.asciidoc b/docs/management/admin/trusted-apps.asciidoc
@@ -2,6 +2,8 @@
 [chapter, role="xpack"]
 = Trusted applications
 
+NOTE: If you use {endpoint-sec} along with other antivirus (AV) software, you might need to configure the other system to trust {elastic-endpoint}. Refer to <<allowlist-endpoint-3rd-party-av-apps>> for more information.
+
 Users with the `superuser` role can add Windows, macOS, and Linux applications that should be trusted. By adding these trusted applications, you can use {elastic-sec} without compatibility or performance issues with other installed applications on your system. Trusted applications are applied only to hosts running {endpoint-sec}.
 
 Trusted applications are designed to help mitigate performance issues and incompatibilities with other endpoint software. However, they create blindspots for {elastic-sec}. One avenue attackers use to exploit these blindspots is by DLL (Dynamic Link Library) side-loading, where they leverage processes signed by trusted vendors -- such as antivirus software -- to execute their malicious DLLs. Such activity appears to originate from the trusted vendor's process.