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-attack-vector-reports.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,4 +50,10 @@ You can use the report that is saved from the Attack vector page to review:
50
50
51
51
Working with the attack vector lets you evaluate the effect of mitigation activities in the attack sequence. You can now determine, for example, if a system upgrade disrupts the attacker's path by breaking the attack chain, or if an alternate attack path remains. This information helps you prioritize remediation and mitigation activities.
52
52
53
-
For more information, see [fill this in](not-sure-yet).
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-create-data-mining-queries.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,11 +61,9 @@ The following predefined reports are available in **Analyze** > **Data Mining**.
61
61
|**Nonactive devices**| Devices that haven't communicated for the past seven days. |
62
62
|**Active devices**| Active network devices within the last 24 hours. |
63
63
64
-
## View reports in on-premises management console
65
-
66
-
The on-premises management console lets you generate reports for each sensor that's connected to it. When you choose a sensor from the on-premises management console, all the custom reports configured on that sensor appear in the list of reports.
64
+
## Generate reports in on-premises management console
67
65
68
-
For each sensor, you can generate a default report or a custom report configured on that sensor.
66
+
The on-premises management console lets you generate reports for each sensor that's connected to it. For each sensor, you can generate a default report or a custom report configured on that sensor.
69
67
70
68
**To generate a report**:
71
69
@@ -79,7 +77,9 @@ For each sensor, you can generate a default report or a custom report configured
79
77
80
78
4. To create a PDF of the report results, select :::image type="icon" source="media/how-to-generate-reports/pdf-report-icon.png" border="false":::.
81
79
82
-
Reports are based on sensor data-mining queries that are performed, and include:
80
+
## View reports in on-premises management console
81
+
82
+
When you choose a sensor from the on-premises management console, all the custom reports configured on that sensor appear in the list of reports. Reports are based on sensor data-mining queries that are performed, and include:
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-create-trends-and-statistics-reports.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.topic: how-to
7
7
8
8
# Create trends and statistics reports
9
9
10
-
Dashboards on your sensor consoleprovide insight into network trends and statistics.
10
+
On your sensor console, create reports that provide insight into network trends and statistics, using dashboards.
11
11
12
12
## Prerequisites
13
13
@@ -21,7 +21,7 @@ You can create many different types of dashboards, based on traffic, device stat
21
21
22
22
1. On your Defender for IoT sensor console, select **Trends & Statistics** > **Create Dashboard**.
23
23
24
-
1. In the **Create Dashboard** pane that appears on the right:
24
+
1. In the **Create Dashboard** pane that appears on the right, enter the following values:
25
25
26
26
|Parameter |Description |
27
27
|---------|---------|
@@ -54,7 +54,7 @@ The following table summarizes common use cases for dashboard widgets.
54
54
|**Active TCP connections**| Displays a chart showing the number of active TCP connections in the system. |
55
55
|**Incident by type**| Displays a pie chart showing the number of incidents by type. This is the number of alerts generated by each engine over a predefined time period. |
56
56
|**Devices by vendor**| Displays a pie chart showing the number of devices by vendor. For each vendor, the size of their slice of the pie reflects the number of their devices. |
57
-
|**Number of devices per VLAN**| Displays a pie chart showing the number of discovered devices per VLAN. The size of each slice of the pie reflects the relative number of discovered device in it compared to the other slices. Each VLAN appears with the VLAN tag assigned by the sensor or the name that you've manually added. |
57
+
|**Number of devices per VLAN**| Displays a pie chart showing the number of discovered devices per VLAN. The size of each slice of the pie reflects the relative number of discovered device compared to the other slices. Each VLAN appears with the VLAN tag assigned by the sensor or the name that you've manually added. |
58
58
|**Top bandwidth by VLAN**| Displays the bandwidth consumption by VLAN. By default, the widget shows five VLANs with the highest bandwidth usage. You can filter the data by the period presented in the widget. Select the down arrow to show more results. |
0 commit comments