Skip to content

Commit 2ba7809

Browse files
committed
validating procedures
1 parent 909dd9e commit 2ba7809

File tree

6 files changed

+32
-40
lines changed

6 files changed

+32
-40
lines changed

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

Lines changed: 13 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -9,15 +9,14 @@ ms.topic: how-to
99

1010
Attack vector reports show a chain of vulnerable devices in a specified attack path. Simulate an attack on a specific target in your network to discover vulnerable devices and analyze attack vectors in real time.
1111

12-
Attack vector reports can also help evaluate mitigation activities to ensure that you're taking all required steps to reduce the risk to your network. For example, use an attack vector report to understand whether a system upgrade would disrupt the attacker's path, or if an alternate attack path still remains.
12+
Attack vector reports can also help evaluate mitigation activities to ensure that you're taking all required steps to reduce the risk to your network. For example, use an attack vector report to understand whether a system upgrade would disrupt the attacker's path, or if an alternate attack path still remains.
1313

1414
## Prerequisites
1515

16-
You must be an **Admin** or **Security Analyst** user to create an attack vector report.
16+
You must be an **Admin** or **Security Analyst** [user](roles-on-premises.md) to create an attack vector report.
1717

1818
## Generate an attack vector simulation
1919

20-
2120
Generate an attack vector simulation so that you can view the resulting report.
2221

2322
**To generate an attack vector simulation:**
@@ -31,28 +30,27 @@ Generate an attack vector simulation so that you can view the resulting report.
3130
| **Maximum Vectors** | The maximum number of attack vectors you want to include in the simulation. |
3231
| **Show in Device Map** | Select to show the attack vector as a group in the **Device map**. |
3332
| **Show All Source Devices** | Select to consider all devices as a possible attack source. |
34-
| **Attack Source** | Shown only, and required, if the **Show All Source Devices** option is toggled off. Select one or more devices to consider as the attack source.|
33+
| **Attack Source** | Appears only, and required, if the **Show All Source Devices** option is toggled off. Select one or more devices to consider as the attack source.|
3534
| **Show All Target Devices** | Select to consider all devices as possible attack targets.|
36-
| **Attack Target** | Shown only, and required, if the **Show All Target Devices** option is toggled off. Select one or more devices to consider as the attack target.|
35+
| **Attack Target** | Appears only, and required, if the **Show All Target Devices** option is toggled off. Select one or more devices to consider as the attack target.|
3736
| **Exclude Devices** | Select one or more devices to exclude from the attack vector simulation.|
3837
| **Exclude Subnets** | Select one or more subnets to exclude from the attack vector simulation.|
3938

40-
1. Select **Save**.
41-
42-
## Attack vector report contents
39+
1. Select **Save**. Your simulation is added to the list, with the number of attack paths indicated in parenthesis.
40+
1. Expand your simulation to view the list of possible attack vector, and select one to view more details on the right. For example:
41+
:::image type="content" source="media/how-to-generate-reports/sample-attack-vectors.png" alt-text="Screen shot of Attack vectors report." lightbox="media/how-to-generate-reports/sample-attack-vectors.png":::
4342

44-
You can use the report that is saved from the Attack vector page to review:
43+
## View an attack vector in the Device Map
4544

46-
- network attack paths and insights
47-
- a risk score
48-
- source and target devices
49-
- a graphical representation of attack vectors
45+
The Device map provides, among [other things](how-to-work-with-the-sensor-device-map.md), a graphical representation of vulnerable devices detected in attack vector reports. To view an attack vector in the Device map:
5046

51-
:::image type="content" source="media/how-to-generate-reports/sample-attack-vectors.png" alt-text="Screen shot of Attack vectors report.":::
47+
1. In the **Attack vector** page, make sure your simulation has **Show in Device map** toggled on.
48+
1. Select **Device map** from the side menu.
49+
1. Select your simulation and then select an attack vector to visualize the devices in your map. For example:
50+
:::image type="content" source="media/how-to-generate-reports/sample-device-map.png" alt-text="Screen shot of Device map." lightbox="media/how-to-generate-reports/sample-device-map.png":::
5251

5352
## Next steps
5453

55-
5654
Continue creating other reports for more security data from your OT sensor. For more information, see:
5755

5856
- [Risk assessment reporting](how-to-create-risk-assessment-reports.md)

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

Lines changed: 13 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Create data mining queries and reports in Defender for IoT
33
description: Learn how to create granular reports about network devices.
4-
ms.date: 02/02/2022
4+
ms.date: 12/05/2022
55
ms.topic: how-to
66
---
77

@@ -13,11 +13,11 @@ Data mining information is saved and stored continuously, except for when a devi
1313

1414
## Prerequisites
1515

16-
You must be an **Admin** or **Security Analyst** user to access predefined data mining reports.
16+
You must be an **Admin** or **Security Analyst** [user](roles-on-premises.md) to access predefined data mining reports.
1717

1818
## Create a report
1919

20-
Reports are dynamically updated each time you open them, meaning that the report will show information that's accurate for the date of viewing the report, rather than the date of creating the report.
20+
Reports are dynamically updated each time you open them. The report shows information that's accurate for the date of viewing the report, rather than the date of creating the report.
2121

2222
**To generate a report**:
2323

@@ -35,11 +35,11 @@ Reports are dynamically updated each time you open them, meaning that the report
3535

3636
1. Select **Save** to save your report and display results on the **Data Mining** page.
3737

38-
## Data mining report contents
38+
## Custom data mining reports
3939

40-
You can use data mining queries for:
40+
Customize your data mining queries, using the different parameters in the **Create new report** pane, to:
4141

42-
| Information | Description |
42+
| Purpose | Description |
4343
|---------|---------|
4444
| **SOC incident response** | Generate a report in real time to help deal with immediate incident response. For example, Data Mining can generate a report for a list of devices that might require patching. |
4545
| **Forensics** | Generate a report based on historical data for investigative reports. |
@@ -49,37 +49,33 @@ You can use data mining queries for:
4949

5050
## Predefined data mining reports
5151

52-
The following predefined reports are available in **Analyze** > **Data Mining**. These queries are generated in real time.
52+
The following predefined reports are available in the **Data Mining** page. These queries are generated in real time.
5353

5454
| Report | Description |
5555
|---------|---------|
5656
| **Programming commands** | Devices that send industrial programming. |
5757
| **Remote access** | Devices that communicate through remote session protocols. |
5858
| **Internet activity** | Devices that are connected to the internet. |
5959
| **CVEs** | A list of devices detected with known vulnerabilities, along with CVSSv2 risk scores. |
60-
| **Excluded CVEs** | A list of all the CVEs that were manually excluded. Customize the CVE list manually if you want the VA reports and attack vectors to reflect your network more accurately by excluding or including particular CVEs and updating the CVSSv2 score accordingly. |
60+
| **Excluded CVEs** | A list of all the CVEs that were manually excluded. Customize the CVE list manually if you want the VA reports and attack vectors to reflect your network more accurately. Customization includes excluding or including particular CVEs and updating the CVSSv2 score accordingly. |
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

6464
## Generate reports in on-premises management console
6565

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

6868
**To generate a report**:
6969

70-
1. On the left pane, select **Reports**. The **Reports** window appears.
70+
1. Select **Reports** from the side menu.
7171

7272
2. From the **Sensors** drop-down list, select the sensor for which you want to generate the report.
7373

74-
:::image type="content" source="media/how-to-generate-reports/sensor-drop-down-list.png" alt-text="Screenshot of sensors view.":::
75-
76-
3. From the right drop-down list, select the report that you want to generate.
74+
3. From the **Select Report** drop-down list, select the report that you want to generate.
7775

7876
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":::.
7977

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.
78+
## Default reports in on-premises management console
8379

8480
Reports are based on sensor data-mining queries that are performed, and include:
8581

@@ -92,9 +88,7 @@ Reports are based on sensor data-mining queries that are performed, and include:
9288

9389
## Next steps
9490

95-
Reports can be viewed in the **Data Mining** page. You can refresh a report, edit report parameters, and export to a CSV file or PDF. You can also take a snapshot of a report.
96-
97-
For more information, see:
91+
Continue creating other reports for more security data from your OT sensor. For more information, see:
9892

9993
- [Risk assessment reporting](how-to-create-risk-assessment-reports.md)
10094

articles/defender-for-iot/organizations/how-to-create-risk-assessment-reports.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Each Defender for IoT network sensor can generate a risk assessment report, whil
1313

1414
## Prerequisites
1515

16-
- You must be an **Admin** user to import firewall rules to an OT sensor or add backup and anti-virus server addresses.
16+
- You must be an **Admin** [user](roles-on-premises.md) to import firewall rules to an OT sensor or add backup and anti-virus server addresses.
1717

1818
- You must be an **Admin** or **Security Analyst** user to create or view risk assessment reports on the OT sensor or on-premises management console.
1919

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Create trends and statistics reports in Defender for IoT
33
description: Gain insight into network activity, statistics, and trends by using Defender for IoT Trends and Statistics widgets.
4-
ms.date: 02/01/2022
4+
ms.date: 12/05/2022
55
ms.topic: how-to
66
---
77

@@ -11,7 +11,7 @@ On your sensor console, create reports that provide insight into network trends
1111

1212
## Prerequisites
1313

14-
You must be an **Administrator** or **Security Analyst** user to create dashboards.
14+
You must be an **Administrator** or **Security Analyst** [user](roles-on-premises.md) to create dashboards.
1515

1616
## Create dashboards
1717

@@ -27,13 +27,13 @@ You can create many different types of dashboards, based on traffic, device stat
2727
|---------|---------|
2828
| **Dashboard name** | Enter a meaningful name for your dashboard. |
2929
| **Dashboard widget type** (Optional) | Filter the widgets displayed by selecting a category or protocol from the menu. |
30-
| **Widget** | Scroll down as needed and select the widget you want to add. Each widget has a short description and indicates whether it focuses on operations, security, or traffic. |
30+
| **Widget** | Scroll down as needed and select the widget you want to add. Each widget has a short description and indicates what it focuses on. |
3131

3232
1. Select **Save** to start your new dashboard.
3333

3434
1. Your widget is added to the new dashboard. Use the toolbar at the top of page to continue modifying your dashboard.
3535

36-
By default, results display detections for over the last seven days. Select the **Filter** button at the top left of each widget to change this range.
36+
By default, results display detections for the current day. Select the **Filter** icon at the top left of each widget to change this range.
3737

3838
> [!NOTE]
3939
> The time shown in the widget is set according to the sensor machine's time.
@@ -59,7 +59,7 @@ The following table summarizes common use cases for dashboard widgets.
5959

6060
## Next steps
6161

62-
For more information, see:
62+
Continue creating other reports for more security data from your OT sensor. For more information, see:
6363

6464
- [Risk assessment reporting](how-to-create-risk-assessment-reports.md)
6565

28.6 KB
Loading
164 KB
Loading

0 commit comments

Comments
 (0)