Skip to content

Commit 227ed75

Browse files
committed
small fixes
1 parent c3d5f06 commit 227ed75

File tree

3 files changed

+16
-10
lines changed

3 files changed

+16
-10
lines changed

articles/defender-for-iot/organizations/how-to-create-attack-vector-reports.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,4 +50,10 @@ You can use the report that is saved from the Attack vector page to review:
5050

5151
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.
5252

53-
For more information, see [fill this in](not-sure-yet).
53+
For more information, see:
54+
55+
- [Risk assessment reporting](how-to-create-risk-assessment-reports.md)
56+
57+
- [Sensor data mining queries](how-to-create-data-mining-queries.md)
58+
59+
- [Create trends and statistics dashboards](how-to-create-trends-and-statistics-reports.md)

articles/defender-for-iot/organizations/how-to-create-data-mining-queries.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -61,11 +61,9 @@ The following predefined reports are available in **Analyze** > **Data Mining**.
6161
| **Nonactive devices** | Devices that haven't communicated for the past seven days. |
6262
| **Active devices** | Active network devices within the last 24 hours. |
6363

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
6765

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

7068
**To generate a report**:
7169

@@ -79,7 +77,9 @@ For each sensor, you can generate a default report or a custom report configured
7977

8078
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":::.
8179

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:
8383

8484
| Information | Description |
8585
|---------|---------|
@@ -98,4 +98,4 @@ For more information, see:
9898

9999
- [Attack vector reporting](how-to-create-attack-vector-reports.md)
100100

101-
- [Create trends and statistics dashboards](how-to-create-trends-and-statistics-reports.md)
101+
- [Create trends and statistics dashboards](how-to-create-trends-and-statistics-reports.md)

articles/defender-for-iot/organizations/how-to-create-trends-and-statistics-reports.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.topic: how-to
77

88
# Create trends and statistics reports
99

10-
Dashboards on your sensor console provide insight into network trends and statistics.
10+
On your sensor console, create reports that provide insight into network trends and statistics, using dashboards.
1111

1212
## Prerequisites
1313

@@ -21,7 +21,7 @@ You can create many different types of dashboards, based on traffic, device stat
2121

2222
1. On your Defender for IoT sensor console, select **Trends & Statistics** > **Create Dashboard**.
2323

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:
2525

2626
|Parameter |Description |
2727
|---------|---------|
@@ -54,7 +54,7 @@ The following table summarizes common use cases for dashboard widgets.
5454
| **Active TCP connections** | Displays a chart showing the number of active TCP connections in the system. |
5555
| **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. |
5656
| **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. |
5858
| **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. |
5959

6060
## Next steps

0 commit comments

Comments
 (0)