Skip to content

Commit f67cbdc

Browse files
authored
Merge pull request #219618 from Shereen-Bhar/firewall-rule-risk
Import firewall rules
2 parents 7285132 + ede8095 commit f67cbdc

File tree

4 files changed

+53
-64
lines changed

4 files changed

+53
-64
lines changed

articles/defender-for-iot/organizations/api/sensor-vulnerability-apis.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -559,7 +559,7 @@ JSON object that represents recommended mitigation steps.
559559
|--|--|--|
560560
| **content** | String | Not nullable | Recommended mitigation steps for detected vulnerabilities |
561561
| **scoreImprovement** | Integer | Nullable | Expected percentage of security improvement after mitigation steps are taken. |
562-
| **details** | Table | Nullable | A table listing mitigation recommendations, such as would be generated in the **Risk assessment** report. Each recommendation includes details about possible security impact if the action is performed and more. For more information, see [Risk mitigation](../how-to-create-risk-assessment-reports.md#risk-mitigation). |
562+
| **details** | Table | Nullable | A table listing mitigation recommendations, such as would be generated in the **Risk assessment** report. Each recommendation includes details about possible security impact if the action is performed and more. For more information, see [Risk mitigation](../how-to-create-risk-assessment-reports.md#create-risk-assessment-reports). |
563563

564564
> [!NOTE]
565565
> You might have multiple mitigation steps, with some returned in the `notifications` field, and others returned in the `mitigation` field. Items with `scoreImprovement` and `details` data is returned only in the `mitigation` field. Items without `scoreImprovement` and `details` data is returned only in the `notifications` field.

articles/defender-for-iot/organizations/how-to-activate-and-set-up-your-sensor.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -241,7 +241,7 @@ You can access console tools from the side menu. Tools help you:
241241
| Event timeline | View a timeline with information about alerts, network events, and user operations. For more information, see [Track sensor activity](how-to-track-sensor-activity.md).|
242242
| Data mining | Generate comprehensive and granular information about your network's devices at various layers. For more information, see [Sensor data mining queries](how-to-create-data-mining-queries.md).|
243243
| Trends and Statistics | View trends and statistics about an extensive range of network traffic and activity. As a small example, display charts and graphs showing top traffic by port, connectivity drops by hours, S7 traffic by control function, number of devices per VLAN, SRTP errors by day, or Modbus traffic by function. For more information, see [Sensor trends and statistics reports](how-to-create-trends-and-statistics-reports.md).
244-
| Risk Assessment | Proactively address vulnerabilities, identify risks such as missing patches or unauthorized applications. Detect changes to device configurations, controller logic, and firmware. Prioritize fixes based on risk scoring and automated threat modeling. For more information, see [Risk assessment reporting](how-to-create-risk-assessment-reports.md#risk-assessment-reporting).|
244+
| Risk Assessment | Proactively address vulnerabilities, identify risks such as missing patches or unauthorized applications. Detect changes to device configurations, controller logic, and firmware. Prioritize fixes based on risk scoring and automated threat modeling. For more information, see [Risk assessment reporting](how-to-create-risk-assessment-reports.md#create-risk-assessment-reports).|
245245
| Attack Vector | Display a graphical representation of a vulnerability chain of exploitable devices. These vulnerabilities can give an attacker access to key network devices. The Attack Vector Simulator calculates attack vectors in real time and analyzes all attack vectors for a specific target. For more information, see [Attack vector reporting](how-to-create-attack-vector-reports.md#attack-vector-reporting).|
246246

247247
### Manage
Lines changed: 51 additions & 62 deletions
Original file line numberDiff line numberDiff line change
@@ -1,104 +1,93 @@
11
---
2-
title: Create risk assessment reports
3-
description: Gain insight into network risks detected by individual sensors or an aggregate view of risks detected by all sensors.
4-
ms.date: 02/03/2022
2+
title: Create risk assessment reports on an OT sensor - Microsoft Defender for IoT
3+
description: Gain insight into network risks detected by individual Defender for IoT OT sensors or an aggregate view of risks detected by all OT sensors.
4+
ms.date: 12/01/2022
55
ms.topic: how-to
66
---
77

8-
# Risk assessment reporting
8+
# Create risk assessment reports
99

10-
## About risk assessment reports
10+
Risk assessment reports provide details about security scores, vulnerabilities, and operational issues on detected devices as well as risks coming from imported firewall rules.
1111

12-
Risk assessment reports provide:
12+
Each Defender for IoT network sensor can generate a risk assessment report, while the on-premises management console collects those reports from all connected sensors.
1313

14-
- An overall security score for the devices detected by organizational sensors.
14+
## Prerequisites
1515

16-
- A security score for each network device detected by an individual sensor.
16+
- You must be an **Admin** user to import firewall rules to an OT sensor or add backup and anti-virus server addresses.
1717

18-
- A breakdown of the number of vulnerable devices, devices that need improvement and secure devices.
18+
- 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

20-
- Insight into security and operational issues:
20+
## Generate risk assessment reports for a specific sensor
2121

22-
- Configuration issues
22+
Use an individual OT sensor to view reports generated for that sensor only.
2323

24-
- Device vulnerability prioritized by security level
24+
**To generate a report**:
2525

26-
- Network security issues
26+
1. Sign in to the sensor console and select **Risk assessment** > **Generate report**. The report is generated and appears in the **Reports list**, along with the timestamp and report size.
2727

28-
- Network operational issues
28+
Reports are automatically named `risk-assessment-report-<integer>`, where the `<integer>` is incremented automatically.
2929

30-
- Connections to ICS networks
30+
1. Select the report name to download it and open it in your browser.
3131

32-
- Internet connections
32+
## Risk assessment report contents
3333

34-
- Industrial malware indicators
34+
Risk assessment reports include the following details:
3535

36-
- Protocol issues
36+
|Details |Description |
37+
|---------|---------|
38+
| **Security scores** | An overall security score for all detected devices, and a security score for each individual device. <br><br> Security scores are based on data learned from packet inspection, behavioral modeling engines, and a SCADA-specific state machine design, and are categorized as follows: <br><br> - **Secure Devices** are devices with a security score above 90%. <br> - **Devices Needing Improvement** are devices with a security score between 70 percent and 89%. <br> - **Vulnerable Devices** are devices with a security score below 70%. |
39+
| **Security and operational issues** | Insight into any of the following security and operational issues: <br><br> - Configuration issues <br> - Device vulnerability, prioritized by security level <br> - Network security issues <br> - Network operational issues <br> - Connections to ICS networks <br> - Internet connections <br> - Industrial malware indicators <br> - Protocol issues <br> - Attack vectors |
40+
| **Firewall rule risk** | The Risk Assessment report highlights if a rule isn't secure, or if there's a mismatch between the rule and the monitored network. |
3741

38-
- Attack vectors
42+
## Enrich the risk assessment report
3943

40-
### Risk mitigation
44+
Enrich your sensor with extra data to provide fuller risk assessment reports:
4145

42-
Reports provide recommendations to help you improve your security score. For example:
43-
- Install the latest security updates.
44-
- Upgrade firmware to the latest version.
45-
- Investigate PLCs in unsecure states.
46+
- Import firewall rules to have them assessed for risks in the report
47+
- Lower your risk by defining addresses for your backup and anti-virus server
4648

47-
## About security scores
49+
### Import firewall rules to an OT sensor
4850

49-
Overall network security score is generated in each report. The score represents the percentage of 100 percent security. For example, a score of 30% would indicate that your network 30% secure.
51+
Import firewall rules to your OT sensor for analysis in **Risk assessment** reports. Importing firewall rules is supported for Checkpoint, Fortinet, and Juniper firewalls.
5052

51-
Risk Assessment scores are based on information learned from packet inspection, behavioral modeling engines, and a SCADA-specific state machine design.
53+
**To import firewall rules**:
5254

53-
**Secure Devices** are devices with a security score above 90%.
55+
1. Sign in to your sensor as an **Admin** user and elect **System Settings** > **Import settings** > **Firewall rules**.
56+
1. In the **Firewall rules** pane:
5457

55-
**Devices Needing Improvement**: Devices with a security score between 70 percent and 89%.
58+
- Select a firewall type from the dropdown menu
59+
- Select **+ Import file** to browse to and select the file you want to import.
5660

57-
**Vulnerable Devices** are devices with a security score below 70%.
61+
For example:
5862

59-
### About backup and anti-virus servers
63+
:::image type="content" source="media/how-to-create-risk-assessment-reports/import-firewall-rules.png" alt-text="Screenshot of how to import firewall rules." lightbox="media/how-to-create-risk-assessment-reports/import-firewall-rules.png":::
6064

61-
The risk assessment score may be negatively impacted if you don't define backup and anti-virus server addresses in your sensor. Adding these addresses improves your score. By default these addresses aren't defined.
62-
The Risk Assessment report cover page will indicate if backup servers and anti-virus servers are not defined.
65+
### Define backup and anti-virus servers on an OT sensor
6366

64-
**To add servers:**
67+
Backup and anti-virus servers aren't defined on your sensor by default. We recommend defining these addresses on your sensor to keep your network risk assessment low.
6568

66-
1. Select **System Settings** and then select **System Properties**.
67-
1. Select **Vulnerability Assessment** and add the addresses to **backup_servers** and **AV_addresses** fields. Use commas to separate multiple addresses. separated by commas.
68-
1. Select **Save**.
69+
**To add backup and anti-virus server addresses**:
6970

70-
## Create risk assessment reports
71+
1. Sign into your OT sensor and select **System Settings** > **System Properties** > **Vulnerability Assessment**.
72+
1. Add your backup and anti-virus server addresses to the **backup_servers** and **AV_addresses** fields, respectively. Use commas to separate multiple addresses.
73+
1. Select **Save** to save your changes.
7174

72-
Create a risk assessment report based on detections made by the sensor you are logged into. The report name is automatically generated as risk-assessment-report-1.pdf. The number is updated for each new report you create. The time and day of creation are displayed.
75+
## View risk assessment reports for multiple sensors
7376

74-
**To create a report:**
77+
Use an on-premises management console to view risk assessment reports for all connected sensors.
7578

76-
1. Sign in to the sensor console.
77-
1. Select **Risk assessment** on the side menu.
78-
1. Select **Generate report**. The report appears in the Saved Reports section.
79-
1. Select the report from the Saved Reports section to download it.
79+
**To generate a report**:
8080

81-
**To import a company logo:**
81+
1. Sign in to your on-premises management console and select **Risk assessment**.
8282

83-
1. Select **Import logo**.
84-
1. Choose a logo to add to the header of your Risk assessment reports.
83+
1. From the **Select Sensor** drop-down menu, select the sensor for which you want to generate the report, and then select **Generate Report**.
8584

86-
### Create an on-premises management console risk assessment report
85+
A new report is listed in the **Archived Reports** area, listed by the time and date it was created, and showing the security score and report size.
8786

88-
Create a risk assessment report based on detections made by sensors that are managed by your on-premises management console.
89-
90-
**To create a report:**
91-
92-
1. Select **Risk Assessment** on the side menu.
93-
2. Select a sensor from the **Select sensor** drop-down list.
94-
3. Select **Generate Report**.
95-
4. Select **Download** from the **Archived Reports** section.
96-
97-
**To import a company logo:**
98-
99-
1. Select **Import logo**.
100-
1. Choose a logo to add to the header of your Risk assessment reports.
87+
1. Select **Download** to download a report and open it in your browser.
10188

10289
## Next steps
10390

104-
For more information, see [Attack vector reporting](how-to-create-attack-vector-reports.md).
91+
Take action based on the recommendations provided in the risk assessment reports to improve your overall network security score. For example, you might install the latest security or firmware updates, or investigate any PLCs that are currently in unsecure states.
92+
93+
For more information, see [Enhance security posture with security recommendations](recommendations.md).
151 KB
Loading

0 commit comments

Comments
 (0)