final

Author: tarTech23

articles/defender-for-iot/organizations/how-to-control-what-traffic-is-monitored.md

@@ -53,7 +53,7 @@ If the traffic shown on the **Deployment** page isn't what you expect, you might
 
 After having analyzed the traffic your sensor is monitoring and fine tuning the deployment, you may need to further fine tune your subnet list. Use this procedure to ensure that your subnets are configured correctly.
 
-While your OT sensor automatically learns your network subnets during the initial deployment, we recommend analyzing the detected traffic and updating them as needed to optimize your map views and device inventory. 
+While your OT sensor automatically learns your network subnets during the initial deployment, we recommend analyzing the detected traffic and updating them as needed to optimize your map views and device inventory.
 
 Also use this procedure to also define subnet settings, determining how devices are displayed in the sensor's [device map](how-to-work-with-the-sensor-device-map.md) and the [Azure device inventory](device-inventory.md).
 
@@ -84,7 +84,7 @@ While the OT network sensor automatically learns the subnets in your network, we
     | **Mask**| Define the subnet's IP mask. |
     | **Name**| We recommend that you enter a meaningful name that specifies the subnet's network role. Subnet names can have up to 60 characters.|
     |**Segregated**     |   Select to show this subnet separately when displaying the device map according to Purdue level.  |
-    | **Remove subnet** | Select to remove any subnets that aren't related to your IoT/OT network scope.| 
+    | **Remove subnet** | Select to remove any subnets that aren't related to your IoT/OT network scope.|
 
     In the subnet grid, subnets marked as **ICS subnet** are recognized as OT networks. This option is read-only in this grid, but you can [manually define a subnet as ICS](#manually-define-a-subnet-as-ics) if there's an OT subnet not being recognized correctly.
 
@@ -184,7 +184,7 @@ If you're working with dynamic networks, you need to handle IP addresses changes
 1. Select **Save** to save your changes.
 
 ## Configure traffic filters (advanced)
-**Belle remove this??** <!-- should this be removed if the alerts arent available? -->
+
 To reduce alert fatigue and focus your network monitoring on high priority traffic, you may decide to filter the traffic that streams into Defender for IoT at the source. Capture filters are configured via the OT sensor CLI, and allow you to block high-bandwidth traffic at the hardware layer, optimizing both appliance performance and resource usage.
 
 For more information, see:

articles/defender-for-iot/organizations/references-work-with-defender-for-iot-cli-commands.md

@@ -6,7 +6,7 @@ ms.topic: concept-article
 ---
 
 # Defender for IoT CLI users and access
-**Belle remove ??** what to remove from this page? -->
+
 This article provides an introduction to the Microsoft Defender for IoT command line interface (CLI). The CLI is a text-based user interface that allows you to access your OT sensors and the on-premises management console for advanced configuration, troubleshooting, and support.
 
 To access the Defender for IoT CLI, you'll need access to the sensor or on-premises management console.
@@ -25,7 +25,6 @@ If you're using a legacy software version, you may have one or more of the follo
 |Legacy scenario  |Description  |
 |---------|---------|
 |**Sensor versions earlier than 23.2.0**     |   In sensor versions earlier than [23.2.0](whats-new.md#default-privileged-user-is-now-admin-instead-of-support), the default *admin* user is named *support*. The *support* user is available and supported only on versions earlier than 23.2.0.<br><br>Documentation refers to the *admin* user to match the latest version of the software.    |
-<!--|**Sensor software versions earlier than 23.1.x**     |   In sensor software versions earlier than [23.1.x](whats-new.md#july-2023), the *cyberx* and *cyberx_host* privileged users are also in use. <br><br>In newly installed versions 23.1.x and higher, the *cyberx* and *cyberx_host* users are available, but not enabled by default. <br><br>To enable these extra privileged users, such as to use the [Defender for IoT CLI](references-work-with-defender-for-iot-cli-commands.md), change their passwords. For more information, see [Recover privileged access to a sensor](manage-users-sensor.md#recover-privileged-access-to-a-sensor).      |-->
 
 Other CLI users cannot be added.
 
@@ -91,8 +90,6 @@ Run:
 system shell
 ```
 
-<!--OT sensor versions earlier than [23.2.0](whats-new.md#default-privileged-user-is-now-admin-instead-of-support) include the *support* privileged user instead of the *admin* user. If you're using an older version of the sensor software, any commands that are listed as supported for the *admin* user are also supported for the legacy *support* user.-->
-
 ## Sign out of the CLI
 
 Make sure to properly sign out of the CLI when you're done using it. You're automatically signed out after an inactive period of 300 seconds.