Skip to content

Commit

Permalink
Host isolation exceptions and VPN communication (#5579)
Browse files Browse the repository at this point in the history
* Add to admonition [ESS]

* Add to admonition [serverless]

* Add back accidentally deleted line
  • Loading branch information
joepeeples authored Jul 31, 2024
1 parent 87713a8 commit 3886a21
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 2 deletions.
7 changes: 6 additions & 1 deletion docs/management/admin/host-isolation-exceptions.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,12 @@ Host isolation exceptions support IPv4 addresses, with optional classless inter-
You must have the *Host Isolation Exceptions* <<endpoint-management-req,privilege>> to access this feature.
--

IMPORTANT: Each host isolation exception IP address should be a highly trusted and secure location since you're allowing it to communicate with hosts that have been isolated to prevent a potential threat from spreading.
[IMPORTANT]
====
* Each host isolation exception IP address should be a highly trusted and secure location since you're allowing it to communicate with hosts that have been isolated to prevent a potential threat from spreading.
* If your hosts depend on VPNs for network communication, you should also set up host isolation exceptions for those VPN servers' IP addresses.
====

Host isolation is a https://www.elastic.co/pricing[Platinum or Enterprise subscription] feature. By default, a host isolation exception is recognized globally across all hosts running {elastic-defend}. You can also assign a host isolation exception to a specific {elastic-defend} integration policy, affecting only the hosts assigned to that policy.

Expand Down
4 changes: 3 additions & 1 deletion docs/serverless/edr-manage/host-isolation-exceptions.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,9 @@ You must have the appropriate user role to use this feature.
</DocCallOut>

<DocCallOut title="Important" color="warning">
Each host isolation exception IP address should be a highly trusted and secure location since you're allowing it to communicate with hosts that have been isolated to prevent a potential threat from spreading.
* Each host isolation exception IP address should be a highly trusted and secure location since you're allowing it to communicate with hosts that have been isolated to prevent a potential threat from spreading.

* If your hosts depend on VPNs for network communication, you should also set up host isolation exceptions for those VPN servers' IP addresses.
</DocCallOut>

Host isolation requires the Endpoint Protection Complete <DocLink slug="/serverless/elasticsearch/manage-project" text="project feature"/>. By default, a host isolation exception is recognized globally across all hosts running ((elastic-defend)). You can also assign a host isolation exception to a specific ((elastic-defend)) integration policy, affecting only the hosts assigned to that policy.
Expand Down

0 comments on commit 3886a21

Please sign in to comment.