edits

Author: tarTech23

articles/defender-for-iot/organizations/best-practices/certificate-requirements.md

@@ -16,6 +16,7 @@ Use the content below to learn about the requirements for [creating SSL/TLS cert
 Defender for IoT uses SSL/TLS certificates to secure communication between the following system components:
 
 - Between users and the OT sensor
+- Between an OT sensor and a high availability (HA) server, if configured
 - Between OT sensors and partners servers defined in [alert forwarding rules](../how-to-forward-alert-information-to-partners.md)
 
 Some organizations also validate their certificates against a Certificate Revocation List (CRL) and the certificate expiration date, and the certificate trust chain. Invalid certificates can't be uploaded to OT sensors, and will block encrypted communication between Defender for IoT components.

articles/defender-for-iot/organizations/tutorial-cyberark.md

@@ -77,11 +77,11 @@ CyberArk must be configured to allow communication with Defender for IoT. This c
 
 ## Enable the integration in Defender for IoT
 
-In order to enable the integration, Syslog Server needs to be enabled in the Defender for IoT on-premises management console. By default, the Syslog Server listens to the IP address of the system using port 514 UDP.
+In order to enable the integration, Syslog Server needs to be enabled in the OT sensor. By default, the Syslog Server listens to the IP address of the system using port 514 UDP.
 
 **To configure Defender for IoT**:
 
-1. Sign into your Defender for IoT on-premises management console, then navigate to **System Settings**.
+1. Sign into your OT sensor, then navigate to **System Settings**.
 
 1. Toggle the Syslog Server to **On**.
 
@@ -101,7 +101,7 @@ Whenever the Defender for IoT platform identifies remote sessions that haven't b
 
 **To view alerts**:
 
-1. Sign into your on-premises management console, then select **Alerts**.
+1. Sign into your OT sensor, then select **Alerts**.
 
 1. From the list of alerts, select the alert titled **Unauthorized Remote Session**.
 
@@ -131,7 +131,7 @@ At any point in time, you can stop the integration from communicating.
 
 **To stop the integration**:
 
-1. In the Defender for IoT on-premises management console, navigate to **System Settings**.
+1. In the OT sensor, navigate to **System Settings**.
 
 1. Toggle the Syslog Server option to **Off** .
 

articles/defender-for-iot/organizations/tutorial-fortinet.md

@@ -125,7 +125,7 @@ The source of suspicious alerts can be blocked in order to prevent further occur
 
 **To block the source of suspicious alerts**:
 
-1. Sign in to the on-premises management console, then select **Alerts**.
+1. Sign in to the OT sensor, then select **Alerts**.
 
 1. Select the alert related to Fortinet integration.
 

articles/defender-for-iot/organizations/tutorial-qradar.md

@@ -66,7 +66,7 @@ A **QID** is a QRadar event identifier. Since all Defender for IoT reports are t
 
 ## Create QRadar forwarding rules
 
-Create a forwarding rule from your on-premises management console to forward alerts to QRadar.
+Create a forwarding rule from your OT sensor to forward alerts to QRadar.
 
 Forwarding alert rules run only on alerts triggered after the forwarding rule is created. The rule doesn't affect any alerts already in the system from before the forwarding rule was created.
 
@@ -129,7 +129,7 @@ For example:
 ```
 
 > [!NOTE]
-> The forwarding rule you create for QRadar uses the `UUID` API from the on-premises management console. For more information, see [UUID (Manage alerts based on the UUID)](api/management-alert-apis.md#uuid-manage-alerts-based-on-the-uuid).
+> The forwarding rule you create for QRadar uses the `UUID` API from the OT sensor. For more information, see [UUID (Manage alerts based on the UUID)](api/management-alert-apis.md#uuid-manage-alerts-based-on-the-uuid).
 
 ## Add custom fields to the alerts