acrolinx

Author: batamig

articles/defender-for-iot/organizations/cli-ot-sensor.md

@@ -9,13 +9,11 @@ ms.topic: reference
 
 This article lists the CLI commands available from Defender for IoT OT network sensors.
 
-Command syntax differs depending on the user performing the command, as indicated below for each activity.
-
 ## Prerequisites
 
 Before you can run any of the following CLI commands, you'll need access to the CLI on your OT network sensor as a privileged user.
 
-Each activity listed below is accessible by a different set of privileged users, including the *cyberx*, *support*, or *cyber_x_host* users. Command syntax is listed only for the users supported for a specific activity.
+Each activity listed in this article is accessible by a different set of privileged users, including the *cyberx*, *support*, or *cyber_x_host* users. Command syntax is listed only for the users supported for a specific activity.
 
 >[!IMPORTANT]
 > We recommend that customers using the Defender for IoT CLI use the *support* user whenever possible.
@@ -26,7 +24,7 @@ For more information, see [Access the CLI](../references-work-with-defender-for-
 
 ### Check OT monitoring services health
 
-Use the following commands to verify that all Defender for IoT application components on the OT sensor are working correctly, including the web console and traffic analysis processes.
+Use the following commands to verify that the Defender for IoT application on the OT sensor are working correctly, including the web console and traffic analysis processes.
 
 Health checks are also available from the OT sensor console. For more information, see [Troubleshoot the sensor and on-premises management console](../how-to-troubleshoot-the-sensor-and-on-premises-management-console.md).
 
@@ -284,7 +282,7 @@ root@xsense:/#
 ```
 
 
-## SSL and TLS certificates
+## TLS/SSL certificates
 
 
 ### Import TLS/SSL certificates to your OT sensor
@@ -319,7 +317,7 @@ root@xsense:/# cyberx-xsense-certificate-import
 
 ### Restore the default self-signed certificate
 
-Use this command in order to restore the default self-signed certificates on the appliance (This should be used only for troubleshooting and not production environments).
+Use the following command to restore the default, self-signed certificates on your sensor appliance. We recommend that you use this activity for troubleshooting only, and not on production environments.
 
 |User  |Command  |Full command syntax   |
 |---------|---------|---------|
@@ -348,7 +346,7 @@ root@xsense:/#
 
 Use the following commands to change passwords for local users on your OT sensor.
 
-When resetting the password for the *cyberx*, *support*, or *cyberx_host* user, the password is reset for both SSH and web access.
+When you change the password for the *cyberx*, *support*, or *cyberx_host* user, the password is changed for both SSH and web access.
 
 
 |User  |Command  |Full command syntax   |
@@ -399,7 +397,7 @@ For more information, see [Define maximum number of failed sign-ins](manage-user
 ### Network settings
 #### Change networking configuration or reassign network interface roles
 
-Use the following command to re-run the OT monitoring software configuration wizard, which helps you define or re-configure the following OT sensor settings:
+Use the following command to rerun the OT monitoring software configuration wizard, which helps you define or reconfigure the following OT sensor settings:
 
 - Enable/disable SPAN monitoring interfaces
 - Configure network settings for the management interface (IP, subnet, default gateway, DNS)
@@ -410,19 +408,19 @@ Use the following command to re-run the OT monitoring software configuration wiz
 |---------|---------|---------|
 |**cyberx_host**     |   `sudo dpkg-reconfigure iot-sensor`      |   No attributes     |
 
-For example with the **cyberx_host** user:
+For example, with the **cyberx_host** user:
 
 ```bash
 root@xsense:/# sudo dpkg-reconfigure iot-sensor
 ```
 
-The configuration wizard starts automatically after you run this command. 
+The configuration wizard starts automatically after you run this command.
 For more information, see [Install OT monitoring software](../how-to-install-software.md#install-ot-monitoring-software).
 
 
 #### Validate and show network interface configuration
 
-Use the following commands to send a validate and show the current network interface configuration on the OT sensor.
+Use the following commands to validate and show the current network interface configuration on the OT sensor.
 
 |User  |Command  |Full command syntax   |
 |---------|---------|---------|
@@ -512,7 +510,7 @@ In this command:
 
 - `-h` or `--help`: Shows the command help syntax
 
-- `--interface <INTERFACE VALUE>`: Is the interface you you want to limit, such as `eth0`
+- `--interface <INTERFACE VALUE>`: Is the interface you want to limit, such as `eth0`
 
 - `--limit <LIMIT VALUE>`: The limit you want to set, such as `30kbit`. Use one of the following units:
 
@@ -651,7 +649,7 @@ Supported attributes for the *cyberx* user are defined as follows:
 
 #### Create a basic capture filter using the support user
 
-If you are creating a basic capture filter as the *support* user, no attributes are passed in the [original command](#create-a-basic-filter-for-all-components). Instead, a series of prompts are displayed to help you create the capture filter interactively.
+If you're creating a basic capture filter as the *support* user, no attributes are passed in the [original command](#create-a-basic-filter-for-all-components). Instead, a series of prompts is displayed to help you create the capture filter interactively.
 
 Reply to the prompts displayed as follows:
 
@@ -665,8 +663,8 @@ Reply to the prompts displayed as follows:
     |---------|---------|---------|
     |**Device**     |   Define a device by its IP address.      |    `1.1.1.1` includes all traffic for this device.     |
     |**Channel**    |    Define a channel by the IP addresses of its source and destination devices, separated by a comma.     |   `1.1.1.1,2.2.2.2` includes all of the traffic for this channel.      |
-    |**Subnet**     |    Define a subnet by its network address.     |   `1.1.1` incudes all traffic for this subnet.      |
-    |**Subnet channel**     |    Define a subnet channel network addresses of the source and destination subnets.     |   `1.1.1,2.2.2` incudes all of the traffic between these subnets.      |
+    |**Subnet**     |    Define a subnet by its network address.     |   `1.1.1` includes all traffic for this subnet.      |
+    |**Subnet channel**     |    Define subnet channel network addresses for the source and destination subnets.     |   `1.1.1,2.2.2` includes all of the traffic between these subnets.      |
 
     List multiple arguments in separate rows.
 
@@ -682,7 +680,7 @@ Reply to the prompts displayed as follows:
     | **Channel** | Define a channel by the IP addresses of its source and destination devices, separated by a comma. | `1.1.1.1,2.2.2.2` excludes all of the traffic between these devices. |
     | **Channel by port** | Define a channel by the IP addresses of its source and destination devices, and the traffic port. | `1.1.1.1,2.2.2.2,443` excludes all of the traffic between these devices and using the specified port.|
     | **Subnet** | Define a subnet by its network address. | `1.1.1` excludes all traffic for this subnet. |
-    | **Subnet channel** | Define a subnet channel network addresses of the source and destination subnets. | `1.1.1,2.2.2` excludes all of the traffic between these subnets. |
+    | **Subnet channel** | Define subnet channel network addresses for the source and destination subnets. | `1.1.1,2.2.2` excludes all of the traffic between these subnets. |
 
     List multiple arguments in separate rows.
 
@@ -736,9 +734,7 @@ Loaded 1 unique channels
 (000) ret      #262144
 (000) ldh      [12]
 ......
-
 ......
-
 ......
 debug: set new filter for horizon '(((not (net 192.168))) and (not (tcp port 9000)) and (not (udp port 9000))) or (vlan and ((not (net 192.168))) and (not (tcp port 9000)) and (not (udp port 9000)))'
 root@xsense:
@@ -767,11 +763,11 @@ The following extra attributes are used for the *cyberx* user to create capture
 |`-s BASE_TRAFFIC_MONITOR`, `--base-traffic-monitor BASE_TRAFFIC_MONITOR`     |     Defines a base capture filter for the `traffic-monitor` component. <br> Default value = `""`    |
 |`-c BASE_COLLECTOR`, `--base-collector BASE_COLLECTOR`     |  Defines a base capture filter for the `collector` component.  <br> Default value = `""`             |
 
-Other attribute values have the same descriptions as in the basic use case, described [above](#create-a-basic-filter-for-all-components).
+Other attribute values have the same descriptions as in the basic use case, described [earlier](#create-a-basic-filter-for-all-components).
 
 #### Create an advanced capture filter using the support user
 
-If you are creating a capture filter for each component separately as the *support* user, no attributes are passed in the [original command](#create-an-advanced-filter-for-specific-components). Instead, a series of prompts are displayed to help you create the capture filter interactively.
+If you're creating a capture filter for each component separately as the *support* user, no attributes are passed in the [original command](#create-an-advanced-filter-for-specific-components). Instead, a series of prompts is displayed to help you create the capture filter interactively.
 
 Most of the prompts are identical to [basic use case](#create-a-basic-capture-filter-using-the-support-user). Reply to the following extra prompts as follows:
 

articles/defender-for-iot/organizations/faqs-ot.md

@@ -11,7 +11,8 @@ This article provides a list of frequently asked questions and answers about OT
 
 ## Our organization uses proprietary non-standard industrial protocols. Are they supported? 
 
-Microsoft Defender for IoT provides comprehensive protocol support. In addition to embedded protocol support, you can secure IoT and OT devices running proprietary and custom protocols, or protocols that deviate from any standard. Using the Horizon Open Development Environment (ODE) SDK, developers can create dissector plugins that decode network traffic based on defined protocols. Traffic is analyzed by services to provide complete monitoring, alerting, and reporting. Use Horizon to:
+Microsoft Defender for IoT provides comprehensive protocol support. In addition to embedded protocol support, you can secure IoT and OT devices running proprietary and custom protocols, or protocols that deviate from any standard. Use the Horizon Open Development Environment (ODE) SDK, to create dissector plugins that decode network traffic based on defined protocols. Traffic is analyzed by services to provide complete monitoring, alerting, and reporting. Use Horizon to:
+
 - Expand visibility and control without the need to upgrade to new versions.
 - Secure proprietary information by developing on-site as an external plugin. 
 - Localize text for alerts, events, and protocol parameters.
@@ -25,11 +26,11 @@ Certified hardware has been tested in our labs for driver stability, packet drop
 
 ## Regulation doesn't allow us to connect our system to the Internet. Can we still utilize Defender for IoT?
 
-Yes you can! The Microsoft Defender for IoT platform on-premises solution is deployed as a physical or virtual sensor appliance that passively ingests network traffic (via SPAN, RSPAN, or TAP) to analyze, discover, and continuously monitor IT, OT, and IoT networks. For larger enterprises, multiple sensors can aggregate their data to an on-premises management console.
+Yes you can! The Microsoft Defender for IoT platform on-premises solution is deployed as a physical or virtual sensor appliance that passively ingests network traffic, such as via SPAN, RSPAN, or TAP, to analyze, discover, and continuously monitor IT, OT, and IoT networks. For larger enterprises, multiple sensors can aggregate their data to an on-premises management console.
 
 ## Where in the network should I connect monitoring ports?
 
-The Microsoft Defender for IoT sensor connects to a SPAN port or network TAP and immediately begins collecting ICS network traffic via passive (agentless) monitoring. It has zero impact on OT networks since it isn’t placed in the data path and doesn’t actively scan OT devices.
+The Microsoft Defender for IoT sensor connects to a SPAN port or network TAP and immediately begins collecting ICS network traffic via passive (agentless) monitoring. It has zero effect on OT networks since it isn’t placed in the data path and doesn’t actively scan OT devices.
 
 For example:
 - A single appliance (virtual of physical) can be in the Shop Floor DMZ layer, having all Shop Floor cell traffic routed to this layer.

articles/defender-for-iot/organizations/manage-users-sensor.md

@@ -38,7 +38,7 @@ This procedure describes how to create new users for a specific OT network senso
     |**First Name**     |    Enter the user's first name.     |
     |**Last Name**     |   Enter the user's last name.      |
     |**Role**     |  Select one of the following user roles: **Admin**, **Security Analyst**, or **Read Only**. For more information, see [On-premises user roles](roles-on-premises.md#on-premises-user-roles).      |
-    |**Password**     |   Select the user type, either **Local** or **Active Directory User**. <br><br>For local users, enter a password for the user. Password requirements include: <br>- At least eight characters<br>- Both lowercase and uppercase alphabetic characters<br>- At least one numbers<br>- At least one symbol<br><br>Local user passwords can only be modified by **Admin** users.|
+    |**Password**     |   Select the user type, either **Local** or **Active Directory User**. <br><br>For local users, enter a password for the user. Password requirements include: <br>- At least eight characters<br>- Both lowercase and uppercase alphabetic characters<br>- At least one number<br>- At least one symbol<br><br>Local user passwords can only be modified by **Admin** users.|
 
     > [!TIP]
     > Integrating with Active Directory lets you associate groups of users with specific permission levels. If you want to create users using Active Directory, first configure [Active Directory on the sensor](manage-users-sensor.md#integrate-ot-sensor-users-with-active-directory) and then return to this procedure.
@@ -75,7 +75,7 @@ For more information, see [Active Directory support on sensors and on-premises m
     |Name  |Description  |
     |---------|---------|
     |**Domain Controller FQDN**     | The fully qualified domain name (FQDN), exactly as it appears on your LDAP server. For example, enter `host1.subdomain.domain.com`.        |
-    |**Domain Controller Port**     | The port on which your LDAP is configured.        |
+    |**Domain Controller Port**     | The port where your LDAP is configured.        |
     |**Primary Domain**     | The domain name, such as `subdomain.domain.com`, and then select the connection type for your LDAP configuration. <br><br>Supported connection types include: **LDAPS/NTLMv3** (recommended), **LDAP/NTLMv3**, or **LDAP/SASL-MD5**        |
     |**Active Directory Groups**     | Select **+ Add** to add an Active Directory group to each permission level listed, as needed. <br><br>        When you enter a group name, make sure that you enter the group name exactly as it's defined in your Active Directory configuration on the LDAP server. You'll use these group names when [adding new sensor users](#add-new-ot-sensor-users) with Active Directory.<br><br>        Supported permission levels include **Read-only**, **Security Analyst**, **Admin**, and **Trusted Domains**.        |
 
@@ -158,7 +158,7 @@ This procedure descries how to recover privileged access to a sensor, for the *c
     >
     > Return to Azure, and select the settings icon in the top toolbar. On the **Directories + subscriptions** page, make sure that you've selected the subscription where your sensor was onboarded to Defender for IoT. Then repeat the steps in Azure to download the **password_recovery.zip** file and upload it on the sensor again.
 
-1. Select **Next**. A system-generated password for your sensor appears for you to use for the selected user. Make sure to write the password down as it won't be shown again.
+1. Select **Next**. A system-generated password for your sensor appears for you to use for the selected user. Make sure to write down the password as it won't be shown again.
 
 1. Select **Next** again to sign into your sensor with the new password.
 
@@ -176,7 +176,7 @@ For more information, see [Defender for IoT CLI users and access](references-wor
     nano /var/cyberx/components/xsense-web/cyberx_web/settings.py
     ```
 
-1. In the **settings.py** file, set the the `"MAX_FAILED_LOGINS"` value to the maximum number of failed sign ins you want to define. Make sure that you consider the number of concurrent users in your system.
+1. In the **settings.py** file, set the `"MAX_FAILED_LOGINS"` value to the maximum number of failed sign ins you want to define. Make sure that you consider the number of concurrent users in your system.
 
 1. Exit the file and run `sudo monit restart all` to apply your changes.
 

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

@@ -18,8 +18,8 @@ To access the Defender for IoT CLI, you'll need access to the sensor or on-premi
 
 Privileged users for OT monitoring are pre-defined together with the [OT monitoring software installation](../how-to-install-software.md), as part of the hardened operating system.
 
-- On the sensor, this includes the *cyberx*, *support*, and *cyberx_host* users.
-- On the on-premises management console, this includes the *cyberx* and *support* users.
+- On the OT sensor, users include the *cyberx*, *support*, and *cyberx_host* users.
+- On the on-premises management console, users include the *cyberx* and *support* users.
 
 The following table describes the access available to each privileged user:
 
@@ -54,7 +54,7 @@ The following tables list the activities available by CLI and the privileged use
 |Restore     | *support*, *cyberx*        | [Restore data from the most recent backup](cli-ot-sensor.md#restore-data-from-the-most-recent-backup)        |
 |Backup disk space     |  *cyberx*       |  [Display backup disk space allocation](cli-ot-sensor.md#display-backup-disk-space-allocation)       |
 
-### SSL and TLS certificates commands
+### TLS/SSL certificate commands
 
 |Service area  |Users  |Actions  |
 |---------|---------|---------|