Skip to content

Commit f12611a

Browse files
authored
Merge pull request #187383 from shhazam-ms/Control-what-traffic-is-monitored---sensor-redesign
Control traffic monitoring: sensor redesign
2 parents 2eb8be5 + 9b2317b commit f12611a

File tree

1 file changed

+35
-68
lines changed

1 file changed

+35
-68
lines changed

articles/defender-for-iot/organizations/how-to-control-what-traffic-is-monitored.md

Lines changed: 35 additions & 68 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Control what traffic is monitored
33
description: Sensors automatically perform deep packet detection for IT and OT traffic and resolve information about network devices, such as device attributes and network behavior. Several tools are available to control the type of traffic that each sensor detects.
4-
ms.date: 11/09/2021
4+
ms.date: 02/03/2022
55
ms.topic: how-to
66
---
77

@@ -19,19 +19,19 @@ After the learning period is complete and the Learning mode is disabled, the sen
1919

2020
When Smart IT Learning is enabled, the sensor tracks network traffic that generates nondeterministic IT behavior based on specific alert scenarios.
2121

22-
The sensor monitors this traffic for seven days. If it detects the same nondeterministic IT traffic within the seven days, it continues to monitor the traffic for another seven days. When the traffic is not detected for a full seven days, Smart IT Learning is disabled for that scenario. New traffic detected for that scenario will only then generate alerts and notifications.
22+
The sensor monitors this traffic for seven days. If it detects the same nondeterministic IT traffic within the seven days, it continues to monitor the traffic for another seven days. When the traffic isn't detected for a full seven days, Smart IT Learning is disabled for that scenario. New traffic detected for that scenario will only then generate alerts and notifications.
2323

2424
Working with Smart IT Learning helps you reduce the number of unnecessary alerts and notifications caused by noisy IT scenarios.
2525

2626
If your sensor is controlled by the on-premises management console, you can't disable the learning modes. In cases like this, the learning mode can only be disabled from the management console.
2727

2828
The learning capabilities (Learning and Smart IT Learning) are enabled by default.
2929

30-
To enable or disable learning:
30+
**To enable or disable learning:**
3131

32-
- Select **System Settings** and toggle the **Learning** and **Smart IT Learning** options.
32+
1. Select **System settings** > **Network monitoring** > **Detection Engines and Network Modelling**.
33+
1. Enable or disable the **Learning** and **Smart IT Learning** options.
3334

34-
:::image type="content" source="media/concept-learning-modes/toggle-options-for-learning-and-smart-it-learning.png" alt-text="System settings toggle screen.":::
3535

3636
## Configure subnets
3737

@@ -53,19 +53,17 @@ In some cases, such as environments that use public ranges as internal ranges, y
5353

5454
- No alerts will be sent about unauthorized internet activity, which reduces notifications and alerts received on external addresses.
5555

56-
To configure subnets:
56+
**To configure subnets:**
5757

5858
1. On the side menu, select **System Settings**.
5959

60-
2. In the **System Setting** window, select **Subnets**.
60+
1. Select **Basic**, and then select **Subnets**.
6161

62-
:::image type="content" source="media/how-to-control-what-traffic-is-monitored/edit-subnets-configuration-screen.png" alt-text="Screenshot that shows the subnet configuration screen.":::
62+
3. To add subnets automatically when new devices are discovered, keep the **Auto Subnets Learning** checkbox selected.
6363

64-
3. To add subnets automatically when new devices are discovered, keep **Auto Subnets Learning** selected.
64+
4. To resolve all subnets as internal subnets, select **Resolve all internet traffic as internal/private**. Public IPs will be treated as private local addresses. No alerts will be sent about unauthorized internet activity.
6565

66-
4. To resolve all subnets as internal subnets, select **Don't Detect Internet Activity**.
67-
68-
5. Select **Add network** and define the following parameters for each subnet:
66+
5. Select **Add subnet** and define the following parameters for each subnet:
6967

7068
- The subnet IP address.
7169
- The subnet mask address.
@@ -75,17 +73,15 @@ To configure subnets:
7573

7674
7. To present the subnet separately when you're arranging the map according to the Purdue level, select **Segregated**.
7775

78-
8. To delete a subnet, select :::image type="icon" source="media/how-to-control-what-traffic-is-monitored/delete-icon.png" border="false":::.
79-
8076
9. To delete all subnets, select **Clear All**.
8177

8278
10. To export configured subnets, select **Export**. The subnet table is downloaded to your workstation.
8379

8480
11. Select **Save**.
8581

86-
### Importing information
82+
### Importing information
8783

88-
To import subnet information, select **Import** and select a CSV file to import. The subnet information is updated with the information that you imported. If you important an empty field, you'll lose your data.
84+
To import subnet information, select **Import** and select a CSV file to import. The subnet information is updated with the information that you imported. If you import an empty field, you'll lose your data.
8985

9086
## Detection engines
9187

@@ -96,23 +92,21 @@ Self-learning analytics engines eliminate the need for updating signatures or de
9692
9793
When an engine detects a deviation, an alert is triggered. You can view and manage alerts from the alert screen or from a partner system.
9894

99-
:::image type="content" source="media/how-to-control-what-traffic-is-monitored/deviation-alert-screen.png" alt-text="Screenshot that shows detection of deviation.":::
100-
10195
The name of the engine that triggered the alert appears under the alert title.
10296

10397
### Protocol violation engine
10498

10599
A protocol violation occurs when the packet structure or field values don't comply with the protocol specification.
106100

107101
Example scenario:
108-
*"Illegal MODBUS Operation (Function Code Zero)"* alert. This alert indicates that a primary device sent a request with function code 0 to a secondary device. This action is not allowed according to the protocol specification, and the secondary device might not handle the input correctly.
102+
*"Illegal MODBUS Operation (Function Code Zero)"* alert. This alert indicates that a primary device sent a request with function code 0 to a secondary device. This action isn't allowed according to the protocol specification, and the secondary device might not handle the input correctly.
109103

110104
### Policy violation engine
111105

112106
A policy violation occurs with a deviation from baseline behavior defined in learned or configured settings.
113107

114108
Example scenario:
115-
*"Unauthorized HTTP User Agent"* alert. This alert indicates that an application that was not learned or approved by policy is used as an HTTP client on a device. This might be a new web browser or application on that device.
109+
*"Unauthorized HTTP User Agent"* alert. This alert indicates that an application that wasn't learned or approved by policy is used as an HTTP client on a device. This might be a new web browser or application on that device.
116110

117111
### Malware engine
118112

@@ -133,15 +127,12 @@ Example scenario:
133127
The Operational engine detects operational incidents or malfunctioning entities.
134128

135129
Example scenario:
136-
*"Device is Suspected to be Disconnected (Unresponsive)"* alert. This alert is raised when a device is not responding to any kind of request for a predefined period. This alert might indicate a device shutdown, disconnection, or malfunction.
130+
*"Device is Suspected to be Disconnected (Unresponsive)"* alert. This alert is raised when a device isn't responding to any kind of request for a predefined period. This alert might indicate a device shutdown, disconnection, or malfunction.
137131

138132
### Enable and disable engines
139133

140134
When you disable a policy engine, information that the engine generates won't be available to the sensor. For example, if you disable the Anomaly engine, you won't receive alerts on network anomalies. If you created a forwarding rule, anomalies that the engine learns won't be sent. To enable or disable a policy engine, select **Enabled** or **Disabled** for the specific engine.
141135

142-
The overall score is displayed in the lower-right corner of the **System Settings** screen. The score indicates the percentage of available protection enabled through the threat protection engines. Each engine is 20 percent of available protection.
143-
144-
:::image type="content" source="media/how-to-control-what-traffic-is-monitored/protection-score-screen.png" alt-text="Screenshot that shows a score.":::
145136

146137
## Configure DHCP address ranges
147138

@@ -161,11 +152,9 @@ The sensor console presents the most current IP address associated with the devi
161152

162153
- The **Device Properties** window indicates if the device was defined as a DHCP device.
163154

164-
To set a DHCP address range:
165-
166-
1. On the side menu, select **DHCP Ranges** from the **System Settings** window.
155+
**To set a DHCP address range:**
167156

168-
:::image type="content" source="media/how-to-control-what-traffic-is-monitored/dhcp-address-range-screen.png" alt-text="Screenshot that shows the selection of DHCP Ranges.":::
157+
1. On the side menu, select **System Settings** > **Network monitoring** > **DHCP Ranges**.
169158

170159
2. Define a new range by setting **From** and **To** values.
171160

@@ -190,30 +179,30 @@ The host name appears in the device inventory, and device map, and in reports.
190179

191180
You can schedule reverse lookup resolution schedules for specific hourly intervals, such as every 12 hours. Or you can schedule a specific time.
192181

193-
To define DNS servers:
182+
**To define DNS servers:**
194183

195-
1. Select **System Settings** and then select **DNS Settings**.
184+
1. Select **System settings**> **Network monitoring**, then select **Reverse DNS Lookup**.
196185

197186
2. Select **Add DNS Server**.
198187

199-
:::image type="content" source="media/how-to-enrich-asset-information/dns-reverse-lookup-configuration-screen.png" alt-text="Screenshot that shows the selection of Add DNS Server.":::
200-
201-
3. In the **Schedule reverse DNS lookup** field, choose either:
188+
3. In the **Schedule Reverse lookup** field, choose either:
202189

203190
- Intervals (per hour).
204191

205192
- A specific time. Use European formatting. For example, use **14:30** and not **2:30 PM**.
206193

207-
4. In the **DNS Server Address** field, enter the DNS IP address.
194+
4. In the **DNS server address** field, enter the DNS IP address.
208195

209-
5. In the **DNS Server Port** field, enter the DNS port.
196+
5. In the **DNS server port** field, enter the DNS port.
210197

211-
6. Resolve the network IP addresses to device FQDNs. In the **Number of Labels** field, add the number of domain labels to display. Up to 30 characters are displayed from left to right.
198+
6. Resolve the network IP addresses to device FQDNs. In the **Number of labels** field, add the number of domain labels to display. Up to 30 characters are displayed from left to right.
212199

213200
7. In the **Subnets** field, enter the subnets that you want the DNS server to query.
214201

215202
8. Select the **Enable** toggle if you want to initiate the reverse lookup.
216203

204+
1. Select **Save**.
205+
217206
### Test the DNS configuration
218207

219208
By using a test device, verify that the settings you defined work properly:
@@ -224,8 +213,6 @@ By using a test device, verify that the settings you defined work properly:
224213

225214
3. Enter an address in **Lookup Address** for the **DNS reverse lookup test for server** dialog box.
226215

227-
:::image type="content" source="media/how-to-enrich-asset-information/dns-reverse-lookup-test-screen.png" alt-text="Screenshot that shows the Lookup Address area.":::
228-
229216
4. Select **Test**.
230217

231218
## Configure Windows Endpoint Monitoring
@@ -247,49 +234,29 @@ You can perform scheduled scans or manual scans. When a scan is finished, you ca
247234

248235
Configure a firewall rule that opens outgoing traffic from the sensor to the scanned subnet by using UDP port 135 and all TCP ports above 1024.
249236

250-
To configure an automatic scan:
251-
252-
1. On the side menu, select **System Settings**.
237+
**To configure an automatic scan:**
253238

254-
2. Select **Windows Endpoint Monitoring** :::image type="icon" source="media/how-to-control-what-traffic-is-monitored/windows-endpoint-monitoring-icon-v2.png" border="false":::.
239+
1. Select **System settings**> **Network monitoring**, then select **Windows Endpoint Monitoring (WMI)**.
255240

256-
:::image type="content" source="media/how-to-control-what-traffic-is-monitored/windows-endpoint-monitoring-screen-v2.png" alt-text="Screenshot that shows the selection of Windows Endpoint Monitoring.":::
241+
1. In the **Edit scan ranges configuration** section, enter the ranges you want to scan and add your username and password.
257242

258-
3. On the **Scan Schedule** pane, configure options as follows:
243+
3. Define how you want to run the scan:
259244

260245
- **By fixed intervals (in hours)**: Set the scan schedule according to intervals in hours.
261246

262247
- **By specific times**: Set the scan schedule according to specific times and select **Save Scan**.
263248

264-
:::image type="content" source="media/how-to-control-what-traffic-is-monitored/schedule-a-scan-screen-v2.png" alt-text="Screenshot that shows the Save Scan button.":::
265-
266-
4. To define the scan range, select **Set scan ranges**.
267-
268-
5. Set the IP address range and add your user and password.
269-
270-
:::image type="content" source="media/how-to-control-what-traffic-is-monitored/edit-scan-range-screen.png" alt-text="Screenshot that shows adding a user and password.":::
271-
272-
6. To exclude an IP range from a scan, select **Disable** next to the range.
273-
274-
7. To remove a range, select :::image type="icon" source="media/how-to-control-what-traffic-is-monitored/remove-scan-icon.png" border="false"::: next to the range.
275-
276-
8. Select **Save**. The **Edit Scan Ranges Configuration** dialog box closes, and the number of ranges appears in the **Scan Ranges** pane.
277-
278-
To perform a manual scan:
279-
280-
1. On the side menu, select **System Settings**.
281-
282-
2. Select **Windows Endpoint Monitoring** :::image type="icon" source="media/how-to-control-what-traffic-is-monitored/windows-endpoint-monitoring-icon-v2.png" border="false":::.
249+
8. Select **Save**. The dialog box closes.
283250

284-
:::image type="content" source="media/how-to-control-what-traffic-is-monitored/windows-endpoint-monitoring-screen-v2.png" alt-text="Screenshot that shows the Windows Endpoint Monitoring setup screen.":::
251+
**To perform a manual scan:**
285252

286-
3. In the **Actions** pane, select **Start scan**. A status bar appears on the **Actions** pane and shows the progress of the scanning process.
253+
1. Define the scan ranges.
287254

288-
:::image type="content" source="media/how-to-control-what-traffic-is-monitored/started-scan-screen-v2.png" alt-text="Screenshot that shows the Start scan button.":::
255+
3. Select **Save** and **Apply changes** and then select **Manually scan**.
289256

290-
To view scan results:
257+
**To view scan results:**
291258

292-
1. When the scan is finished, on the **Actions** pane, select **View Scan Results**. The CSV file with the scan results is downloaded to your computer.
259+
1. When the scan is finished, select **View Scan Results**. A .csv file with the scan results is downloaded to your computer.
293260

294261
## See also
295262

0 commit comments

Comments
 (0)