IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Event filters Blocklist »
Elastic Docs ›Elastic Security Solution [8.15] ›Manage Elastic Defend

Host isolation exceptions

edit

Host isolation exceptions

edit

You can configure host isolation exceptions for specific IP addresses that isolated hosts are still allowed to communicate with, even when blocked from the rest of your network. Isolated hosts can still send data to Elasticsearch and Kibana, so you don’t need to set up host isolation exceptions for them.

Host isolation exceptions support IPv4 addresses, with optional classless inter-domain routing (CIDR) notation.

Requirements

You must have the Host Isolation Exceptions privilege to access this feature.

  • 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 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.

  1. Go to Manage → Host isolation exceptions.
  2. Click Add Host isolation exception.

  3. Fill in these fields in the Add Host isolation exception flyout:

    1. Name your host isolation exceptions: Enter a name to identify the host isolation exception.
    2. Description: Enter a description to provide more information on the host isolation exception (optional).
    3. Enter IP Address: Enter the IP address for which you want to allow communication with an isolated host. This must be an IPv4 address, with optional CIDR notation (for example, 0.0.0.0 or 1.0.0.0/24, respectively).

  4. Select an option in the Assignment section to assign the host isolation exception to a specific integration policy:

    • Global: Assign the host isolation exception to all integration policies for Elastic Defend.

    • Per Policy: Assign the host isolation exception to one or more specific Elastic Defend integration policies. Select each policy where you want the host isolation exception to apply.

      You can also select the Per Policy option without immediately assigning a policy to the host isolation exception. For example, you could do this to create and review your host isolation exception configurations before putting them into action with a policy.

  5. Click Add Host isolation exception. The new exception is added to the Host isolation exceptions list.

View and manage host isolation exceptions

edit

The Host isolation exceptions page displays all the host isolation exceptions that have been configured for Elastic Security. To refine the list, use the search bar to search by name, description, or IP address.

List of host isolation exceptions

Edit a host isolation exception

edit

You can individually modify each host isolation exception and change the policies that a host isolation exception is assigned to.

To edit a host isolation exception:

  1. Click the actions menu (…​) for the exception you want to edit, then select Edit Exception.
  2. Modify details as needed.
  3. Click Save. The newly modified exception appears at the top of the list.

Delete a host isolation exception

edit

You can delete a host isolation exception, which removes it entirely from all Elastic Defend integration policies.

To delete a host isolation exception:

  1. Click the actions menu (…​) on the exception you want to delete, then select Delete Exception.
  2. On the dialog that opens, verify that you are removing the correct host isolation exception, then click Delete. A confirmation message is displayed.
« Event filters Blocklist »