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: articles/defender-for-iot/organizations/how-to-create-data-mining-queries.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Data mining query data is continuously saved until a device is deleted, and is a
17
17
18
18
To create data mining reports, you must be able to access the OT network sensor you want to generate data for as an **Admin** or **Security Analyst** user.
19
19
20
-
For more information, see [On-premises users and roles for OT monitoring with Defender for IoT](roles-on-premises.md)
20
+
For more information, see [On-premises users and roles for OT monitoring with Defender for IoT](roles-on-premises.md).
21
21
22
22
## View an OT sensor predefined data mining report
23
23
@@ -54,7 +54,7 @@ Create your own custom data mining report if you have reporting needs not covere
54
54
|**Choose category**| Select the categories to include in your report. |
55
55
|**Order by**| Select to sort your data by category or by activity. |
56
56
|**Filter by**| Define a filter for your report using any of the following parameters: <br><br> - **Results within the last**: Enter a number and then select **Minutes**, **Hours**, or **Days** <br> - **IP address / MAC address / Port**: Enter one or more IP addresses, MAC addresses, and ports to filter into your report. Enter a value and then select + to add it to the list.<br> - **Device group**: Select one or mode device groups to filter into your report. |
57
-
|**Add filter type**| Select to add any of the following filter types into your report. <br><br> - Transport (GENERIC) <br> -Protocol (GENERIC) <br> - TAG (GENERIC) <br> - Maximum value (GENERIC) <br> - State (GENERIC) <br> - Minimum value (GENERIC) <br><br> Enter a value in the relevant field and then select + to add it to the list. |
57
+
|**Add filter type**| Select to add any of the following filter types into your report. <br><br> - Transport (GENERIC) <br> -Protocol (GENERIC) <br> - TAG (GENERIC) <br> - Maximum value (GENERIC) <br> - State (GENERIC) <br> - Minimum value (GENERIC) <br><br> Enter a value in the relevant field and then select + to add it to the list. |
58
58
59
59
1. Select **Save**. Your data mining report is shown in the **My reports** area. For example:
60
60
@@ -82,9 +82,7 @@ Sign into an on-premises management console to view [out-of-the-box data mining
82
82
83
83
**To view a data mining report from an on-premises management console**:
84
84
85
-
Sign into your on-premises management console and select
86
-
87
-
1.**Reports** on the left.
85
+
1. Sign into your on-premises management console and select **Reports** on the left.
88
86
89
87
1. From the **Sensors** drop-down list, select the sensor for which you want to generate the report.
90
88
@@ -98,8 +96,8 @@ The page lists the current report data. Select :::image type="icon" source="medi
98
96
99
97
- Continue creating other reports for more security data from your OT sensor. For more information, see:
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-enhance-port-and-vlan-name-resolution.md
+42-20Lines changed: 42 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,48 +7,70 @@ ms.topic: how-to
7
7
8
8
# Customize port and VLAN names
9
9
10
-
You can customize port and VLAN names on your sensors to enrich device resolution.
10
+
Enrich device resolution by customizing port and VLAN names on your sensors.
11
+
12
+
## Prerequisites
13
+
14
+
To customize port and VLAN names, you must be able to access the sensor as an **Admin** user.
15
+
16
+
For more information, see [On-premises users and roles for OT monitoring with Defender for IoT](roles-on-premises.md).
11
17
12
18
## Customize a port name
13
19
14
-
Microsoft Defender for IoT automatically assigns names to most universally reserved ports, such as DHCP or HTTP. You can customize port names for other ports that Defender for IoT detects. For example, you might assign a name to a non-reserved port because that port shows unusually high activity. Names appear when you view device groups from the device map, or when you create reports that provide port information.
20
+
Customize port names for ports that Defender for IoT detects.
21
+
22
+
Port names appear when you view device groups from the device map, or when you create reports that provide port information. Microsoft Defender for IoT automatically assigns names to most universally reserved ports, such as DHCP or HTTP.
23
+
24
+
**To customize a port name:**
25
+
26
+
1. Sign in to your network sensor as an **Admin** user and select **System Settings**.
27
+
28
+
1. Under **Network monitoring**, select **Port Naming**.
29
+
30
+
1. In the **Port naming** pane, select **Add port**.
15
31
16
-
Customize a name as follows:
32
+
1. Enter the port number, select the protocol (**TCP**, **UDP**, or **BOTH**), and type in a name. For example:
17
33
18
-
1. Select **System Settings**. Under **Network monitoring**, select **Port Naming**.
19
-
2. Select **Add port**.
20
-
3. Enter the port number, select the protocol (TCP, UDP, both) and type in a name.
21
-
4. Select **Save**.
34
+
:::image type="content" source="media/how-to-enrich-asset-information/edit-port.png" alt-text="Screenshot of the port naming pane.":::
35
+
36
+
1. Select **Save**.
22
37
23
38
## Customize a VLAN name
24
39
25
-
You can enrich device inventory data with device VLAN numbers and tags.
40
+
Enrich device inventory data with device VLAN numbers and names.
41
+
42
+
VLANS are either discovered automatically by the sensor or added manually. When you add a manual VLAN, you must add a unique name. Once named, the name of the VLAN will appear in reports instead of the VLAN number.
43
+
44
+
Before you start, note that:
45
+
46
+
- Manual VLANs can be edited and deleted, but automatically discovered VLANs can’t.
26
47
27
-
- VLANs support is based on 802.1q (up to VLAN ID 4094). VLANS can be discovered automatically by the sensor or added manually.
28
-
- Automatically discovered VLANs can't be edited or deleted. You should add a name to each VLAN, if you don't add a name, the VLAN number will appear when VLAN information is reported.
29
-
- When you add a manual VLN, you must add a unique name. These VLANs can be edited and deleted.
30
-
- VLAN names can contain up to 50 ASCII characters.
48
+
- VLAN names are not synchronized between the sensor and the management console. You need to define the name on the management console as well.
49
+
50
+
- VLANs support is based on 802.1q (up to VLAN ID 4094).
31
51
32
-
## Before you start
33
-
> [!NOTE]
34
-
> VLAN names are not synchronized between the sensor and the management console. You need to define the name on the management console as well.
35
52
For Cisco switches, add the following line to the span configuration: `monitor session 1 destination interface XX/XX encapsulation dot1q`. In that command, *XX/XX* is the name and number of the port.
36
53
37
-
To configure VLAN names:
54
+
**To configure VLAN names:**
55
+
56
+
1. Sign in to your network sensor and select **System Settings**.
2. In the **System Settings**window, select **VLAN**.
60
+
1. In **VLAN naming**pane, select **Add VLAN**.
42
61
43
-
:::image type="content" source="media/how-to-enrich-asset-information/edit-vlan.png" alt-text="Use the system settings to edit your VLANs.":::
62
+
1. Add a VLAN ID and unique VLAN name. For example:
44
63
45
-
3. Add a unique name next to each VLAN ID.
64
+
:::image type="content" source="media/how-to-enrich-asset-information/edit-vlan.png" alt-text="Screenshot of the VLAN naming pane." lightbox="media/how-to-enrich-asset-information/edit-vlan.png":::
46
65
66
+
1. Select **Save**.
47
67
48
68
## Next steps
49
69
50
70
View enriched device information in various reports:
51
71
52
72
-[Investigate sensor detections in a device inventory](how-to-investigate-sensor-detections-in-a-device-inventory.md)
73
+
53
74
-[Sensor trends and statistics reports](how-to-create-trends-and-statistics-reports.md)
75
+
54
76
-[Sensor data mining queries](how-to-create-data-mining-queries.md)
0 commit comments