You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-endpoint/isolation-exclusions.md
+26-24Lines changed: 26 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,9 @@ There are two modes of isolation: **full isolation** and **selective isolation**
50
50
51
51
***Selective isolation**: Selective isolation mode allows administrators to apply exclusions to ensure that critical tools and network communications can still function, while maintaining the device's isolated state.
52
52
53
-
## How to define and apply isolation exclusions
53
+
## How to use isolation exclusion
54
+
55
+
There are two steps to using isolation exclusion: defining isolation exclusion rules, and applying isolation exclusion on a device. These steps are described in the following sections. To use isolation exclusion, the feature must be enabled, as described in the prerequisites.
54
56
55
57
### Prerequisites
56
58
@@ -64,19 +66,21 @@ There are two modes of isolation: **full isolation** and **selective isolation**
64
66
>
65
67
> Note that Skype has been deprecated and is no longer included in any default exclusions.
66
68
67
-
### Step 1: Define global exclusions in settings
69
+
### Step 1: Define global exclusions in the settings
68
70
69
-
1.Navigate to **Settings** > **Endpoints** > **Isolation Exclusion Rules**.
71
+
1.In the [Microsoft Defender portal](https://security.microsoft.com), navigate to **Settings** > **Endpoints** > **Isolation Exclusion Rules**.
70
72
71
-
1. Select the relevant OS tab (Windows or macOS).
73
+
1. Select the relevant OS tab (Windows rules or Mac rules).
72
74
73
75
1. Select **+ Add exclusion rule**
74
76
75
77
:::image type="content" source="./media/isolation-exclusions/add-new-exclusion-rule.png" alt-text="Screenshot showing how to add a new isolation exclusion rule." lightbox="./media/isolation-exclusions/add-new-exclusion-rule.png":::
76
78
77
-
1. In the **Add new exclusion rule** dialog, fill in the parameters. Red asterisks denote mandatory parameters.
79
+
1. In the **Add new exclusion rule** dialog that appears., fill in the parameters. Red asterisks denote mandatory parameters.
80
+
81
+
:::image type="content" source="./media/isolation-exclusions/exclusion-rule-definition.png" alt-text="Screenshot showing the fields required for defining an isolation exclusion rule.":::
78
82
79
-
Isolation exclusion rule parameters and their valid values are described in the following table.
83
+
Fill in the isolation exclusion parameters. Red asterisks denote mandatory parameters. The parameters and their valid values are described in the following table.
80
84
81
85
| Parameter | Description and valid values |
82
86
|:-----|:-----|
@@ -88,8 +92,6 @@ There are two modes of isolation: **full isolation** and **selective isolation**
88
92
|**Direction**| The connection direction (Inbound/Outbound). Examples:<br><br>**Outbound connection**: If the device initiates a connection, for instance, an HTTPS connection to a remote backend server, define only an outbound rule. Example: The device sends a request to 1.1.1.1 (outbound). In this case, no inbound rule is needed, as the response from the server is automatically accepted as part of the connection.<br><br>**Inbound connection**: If the device is listening to incoming connections, define an **inbound rule**.|
89
93
|**Remote IP**| The IP (or IPs) with which communication is allowed while the device is isolated from the network.<br><br>Supported IP formats:<br>- IPv4/IPv6, with optional CIDR notation<br>- A comma-separated list of valid IPs<br><br>Valid input examples:<br>- Single IP address: `1.1.1.1`<br>- IPV6 address: `2001:db8:85a3::8a2e:370:7334`<br>- IP address with CIDR notation (IPv4 or IPv6): `1.1.1.1/24`<br> This example defines a range of IP addresses. In this case, it includes all IPs from 1.1.1.0 to 1.1.1.255. The /24 represents the subnet mask, which specifies that the first 24 bits of the address are fixed, and the remaining 8 bits define the address range.|
90
94
91
-
:::image type="content" source="./media/isolation-exclusions/exclusion-rule-definition.png" alt-text="Screenshot showing the fields required for defining an isolation exclusion rule." lightbox="./media/isolation-exclusions/exclusion-rule-definition.png":::
92
-
93
95
1. Save and apply changes.
94
96
95
97
**These global rules apply whenever selective isolation is enabled for a device.**
@@ -118,29 +120,29 @@ To trigger isolation with exclusions via API, set the IsolationType parameter to
118
120
* Within a single rule, conditions use AND logic (all must match).
119
121
* Undefined conditions in a rule are treated as "any" (that is, unrestricted for that parameter).
120
122
121
-
For example, if the following rules are defined:
123
+
For example, if the following rules are defined:
122
124
123
-
```
124
-
Rule 1:
125
+
```
126
+
Rule 1:
125
127
126
-
Process path = c:\example.exe
127
-
Remote IP = 1.1.1.1
128
-
Direction = Outbound
128
+
Process path = c:\example.exe
129
+
Remote IP = 1.1.1.1
130
+
Direction = Outbound
129
131
130
-
Rule 2:
132
+
Rule 2:
131
133
132
-
Process path = c:\example_2.exe
133
-
Direction = Outbound
134
+
Process path = c:\example_2.exe
135
+
Direction = Outbound
134
136
135
-
Rule 3:
137
+
Rule 3:
136
138
137
-
Remote IP = 18.18.18.18
138
-
Direction = Inbound
139
+
Remote IP = 18.18.18.18
140
+
Direction = Inbound
139
141
140
-
```
141
-
**example.exe* will only be able to initiate network connections to remote IP 1.1.1.1.
142
-
**example_2.exe* can initiate network connections to every IP address.
143
-
* The device can receive inbound connection from IP address 18.18.18.18.
142
+
```
143
+
**example.exe* will only be able to initiate network connections to remote IP 1.1.1.1.
144
+
**example_2.exe* can initiate network connections to every IP address.
145
+
* The device can receive inbound connection from IP address 18.18.18.18.
Copy file name to clipboardExpand all lines: defender-endpoint/respond-machine-alerts.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -216,7 +216,7 @@ Depending on the severity of the attack and the sensitivity of the device, you m
216
216
-`iptables`
217
217
-`ip6tables`
218
218
- Linux kernel with `CONFIG_NETFILTER`, `CONFID_IP_NF_IPTABLES`, and `CONFIG_IP_NF_MATCH_OWNER`
219
-
- Selective isolation is available for devices running Windows 10, version 1709 or later, and Windows 11.
219
+
- Selective isolation is available for devices running Windows 10, version 1709 or later, and Windows 11. For more information about selective isolation, see [Isolation exclusions](/defender-endpoint/isolation-exclusions.md).
220
220
- When isolating a device, only certain processes and destinations are allowed. Therefore, devices that are behind a full VPN tunnel won't be able to reach the Microsoft Defender for Endpoint cloud service after the device is isolated. We recommend using a split-tunneling VPN for Microsoft Defender for Endpoint and Microsoft Defender Antivirus cloud-based protection-related traffic.
221
221
- The feature supports VPN connection.
222
222
- You must have at least the `Active remediation actions` role assigned. For more information, see [Create and manage roles](user-roles.md).
0 commit comments