committing suggestions

Author: Shereen-Bhar

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

@@ -559,7 +559,7 @@ JSON object that represents recommended mitigation steps.
 |--|--|--|
 | **content** | String | Not nullable | Recommended mitigation steps for detected vulnerabilities  |
 | **scoreImprovement** | Integer | Nullable | Expected percentage of security improvement after mitigation steps are taken.  |
-| **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). |
+| **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-assessment-reporting). |
 
 > [!NOTE]
 > 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-create-risk-assessment-reports.md

@@ -9,23 +9,39 @@ ms.topic: how-to
 
 Risk assessment reports, generated by Defender for IoT OT network sensors and on-premises management consoles, provide details about security scores, vulnerabilities, and operational issues on detected devices as well as risks coming from imported firewall rules.
 
-Take action based on the recommendations provided in the risk assesment 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.
+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.
 
 Each sensor has access to reports generated for that sensor, while the on-premises management console allows you view reports from all connected sensors from the same page. The on-premises management console also supports customizations for the logo that appears in your report.
 
 ## Prerequisites
 
 - You must be an **Admin** user to import firewall rules to an OT sensor or add backup and anti-virus server addresses. <!--need to check this-->.
 
-- You must be an **Admin** or **Security Analyst** user to create or view risk assesment reports on the OT sensor or on-premises management console.
+- 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.
 
 ## Import firewall rules to a OT sensor
 
-<!--put the firewall rules procedure here-->
+Import firewall rules to your OT sensor for analysis in **Risk assessment** reports. Importing firewall rules is supported for Checkpoint, Fortinet, and Juniper firewalls.
+
+- Checkpoint
+- Fortinet
+- Juniper
+
+**To import firewall rules**:
+
+1. Sign in to your sensor as an **Admin** user and elect **System Settings** > **Import settings** > **Firewall rules**.
+1. In the **Firewall rules** pane:
+
+    - Select a firewall type from the dropdown menu
+    - Select **+ Import file** to browse to and select the file you want to import.
+
+For example:
+
+:::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":::
 
 ## Add backup and anti-virus server addresses to your sensor
 
-Backup and anti-virus servers are not defined on your sensor by default. We recommend defining these addresses on your sensor to keep your network risk assesment low.
+Backup and anti-virus servers are not defined on your sensor by default. We recommend defining these addresses on your sensor to keep your network risk assessment low.
 
 **To add backup and anti-virus server addresses**:
 
@@ -37,31 +53,31 @@ Backup and anti-virus servers are not defined on your sensor by default. We reco
 
 Use an individual OT sensor to view reports generated for that sensor only.
 
-**To generate a report**: 
+**To generate a report**:
 
-1. Sign in to the sensor console and select **Risk assesment** > **Generate report**. The report is generated and appears in the **Reports list**, along with the timestamp and report size.
+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.
 
-    Reports are automatically named `risk-assesment-report-<integer>`, where the `<integer>` is incremented automatically.
+    Reports are automatically named `risk-assessment-report-<integer>`, where the `<integer>` is incremented automatically.
 
 1. Select the report name to download it and open it in your browser.
 
-## Create and view risk assesment reports for multiple sensors
+## Create and view risk assessment reports for multiple sensors
 
-Use an on-premises management console to create and view risk assesment reports for all connected sensors, or to customize your report logo.
+Use an on-premises management console to create and view risk assessment reports for all connected sensors, or to customize your report logo.
 
 **To generate a report**:
 
-1. Sign in to your on-premises management console and select **Risk assesment**.
+1. Sign in to your on-premises management console and select **Risk assessment**.
 
 1. To customize the logo that appears on your report, select **Import logo**. Browse to and select the logo file you want to use.
 
 1. From the **Select Sensor** drop-down menu, select the sensor for which you want to generate the report, and then select **Generate Report**.
 
     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.
-    
+
 1. Select **Download** to download a report and open it in your browser.
 
-## Risk assesment report contents
+## Risk assessment report contents
 
 Risk assessment reports include the following details:
 
@@ -75,12 +91,12 @@ Risk assessment reports include the following details:
 
     - **Vulnerable Devices** are devices with a security score below 70%.
 
-- Insight into any of the following security and operational issues: <!--im not really even sure how much this list is helpful. it doesn't really tell me much.-->
+- Insight into any of the following security and operational issues:
 
     :::row:::
         :::column span="":::
         - Configuration issues
-        - Device vulnerability, prioritzed by security level
+        - Device vulnerability, prioritized by security level
         - Network security issues
         - Network operational issues
         :::column-end:::
@@ -95,8 +111,6 @@ Risk assessment reports include the following details:
 
 If you've imported firewall data to your sensor, the risk assessment reports also include data about firewall rule risk, based on the imported rules. The Risk Assessment report highlights if a rule is not secure, or if there's a mismatch between the rule and the monitored network.
 
-<!--i don't really think that this screenshot is helpful out of context. we don't show screenshots for any other part of the report.-->
-
 ## Next steps
 
 For more information, see [Attack vector reporting](how-to-create-attack-vector-reports.md).

articles/defender-for-iot/organizations/how-to-set-up-your-network.md

@@ -173,27 +173,6 @@ Open these ports to allow extra services for Defender for IoT.
 | LDAPS | TCP | In/Out | 636 | Active Directory | Allows Active Directory management of users that have access, to sign in to the system | On-premises management console and Sensor | LDAPS server |
 | Tunneling | TCP | In | 9000 </br></br> In addition to port 443 </br></br> Allows access from the sensor, or end user, to the on-premises management console </br></br> Port 22 from the sensor to the on-premises management console | Monitoring | Tunneling | Endpoint, Sensor | On-premises management console |
 
-## Import firewall rules
-
-Import firewall rules to your OT sensor for analysis in **Risk assessment** reports. Importing firewall rules is supported for Checkpoint, Fortinet, and Juniper firewalls.
-
-- Checkpoint
-- Fortinet
-- Juniper
-
-**To import firewall rules**:
-
-1. Sign in to your sensor as an **Admin** user and elect **System Settings** > **Import settings** > **Firewall rules**.
-1. In the **Firewall rules** pane:
-
-    - Select a firewall type from the dropdown menu
-    - Select **+ Import file** to browse to and select the file you want to import.
-For example:
-
-:::image type="content" source="media/how-to-set-up-your-network/import-firewall-rules.png" alt-text="Screenshot of how to import firewall rules." lightbox="media/how-to-set-up-your-network/import-firewall-rules.png":::
-
-Firewall rules are analyzed in the [Risk Assessment report](how-to-create-risk-assessment-reports.md).
-
 ## Choose a cloud connection method
 
 If you're setting up OT sensors and connecting them to the cloud, understand supported cloud connection methods, and make sure to connect your sensors as needed.