Merge pull request #293242 from tarTech23/eiotdep

Delete mentions of EioT network sensor

Author: v-ccolin

articles/defender-for-iot/organizations/alert-engine-messages.md

@@ -246,9 +246,9 @@ Malware engine alerts describe detected malicious network activity.
 
 | Title | Description| Severity | Category | MITRE ATT&CK <br> Tactics and techniques | Learnable |
 |--|--|--|--|--|--|
-| **Connection Attempt to Known Malicious IP** | Suspicious network activity was detected. This activity might be associated with an attack exploiting a method used by known malware. <br><br>Triggered by both OT and Enterprise IoT network sensors. | High | Suspicion of Malicious Activity | **Tactics:** <br> - Initial Access <br> - Command And Control <br><br> **Techniques:** <br> - T0883: Internet Accessible Device <br> - T0884: Connection Proxy | Not learnable |
+| **Connection Attempt to Known Malicious IP** | Suspicious network activity was detected. This activity might be associated with an attack exploiting a method used by known malware. <br><br>Triggered by the OT network sensors. | High | Suspicion of Malicious Activity | **Tactics:** <br> - Initial Access <br> - Command And Control <br><br> **Techniques:** <br> - T0883: Internet Accessible Device <br> - T0884: Connection Proxy | Not learnable |
 | **Invalid SMB Message (DoublePulsar Backdoor Implant)** | Suspicious network activity was detected. This activity might be associated with an attack exploiting a method used by known malware. | High | Suspicion of Malware | **Tactics:** <br> - Initial Access <br> - LateralMovement <br><br> **Techniques:** <br> - T0866: Exploitation of Remote Services | Not learnable |
-| **Malicious Domain Name Request** | Suspicious network activity was detected. This activity might be associated with an attack exploiting a method used by known malware. <br><br>Triggered by both OT and Enterprise IoT network sensors. | High | Suspicion of Malicious Activity | **Tactics:** <br> - Initial Access <br> - Command And Control <br><br> **Techniques:** <br> - T0883: Internet Accessible Device <br> - T0884: Connection Proxy | Learnable |
+| **Malicious Domain Name Request** | Suspicious network activity was detected. This activity might be associated with an attack exploiting a method used by known malware. <br><br>Triggered by the OT network sensors. | High | Suspicion of Malicious Activity | **Tactics:** <br> - Initial Access <br> - Command And Control <br><br> **Techniques:** <br> - T0883: Internet Accessible Device <br> - T0884: Connection Proxy | Learnable |
 | **Malicious URL Path** | A request was made to a known malicious URL path. Requests made for this URL path may indicate that the source making the request is compromised. | High | Suspicion of Malicious Activity | **Tactics:** <br> - Initial Access <br> - Command And Control <br><br> **Techniques:** <br> - T0883: Internet Accessible Device <br> - T0884: Connection Proxy | Not learnable |
 | **Malware Test File Detected - EICAR AV Success** | An EICAR AV test file was detected in traffic between two devices (over any transport - TCP or UDP). The file isn't malware. It's used to confirm that the antivirus software is installed correctly. Demonstrate what happens when a virus is found, and check internal procedures and reactions when a virus is found. Antivirus software should detect EICAR as if it were a real virus. | High | Suspicion of Malicious Activity | **Tactics:** <br> - Discovery <br><br> **Techniques:** <br> - T0842: Network Sniffing | Not learnable |
 | **Suspicion of Conficker Malware** | Suspicious network activity was detected. This activity might be associated with an attack exploiting a method used by known malware. | Medium | Suspicion of Malware | **Tactics:** <br> - Initial Access <br> - Impact <br><br> **Techniques:** <br> - T0826: Loss of Availability <br> - T0828: Loss of Productivity and Revenue <br> - T0847: Replication Through Removable Media | Not learnable |

articles/defender-for-iot/organizations/architecture.md

@@ -23,9 +23,9 @@ Defender for IoT includes the following OT security monitoring components:
 
 - **The Azure portal**, for cloud management and integration to other Microsoft services, such as Microsoft Sentinel.
 
-- **Operational technology (OT) or Enterprise IoT network sensors**, to detect devices across your network. Defender for IoT network sensors are deployed on either a virtual machine or a physical appliance. OT sensors can be configured as cloud-connected sensors, or fully on-premises, locally managed sensors.
+- **Operational technology (OT) network sensors**, to detect devices across your network. Defender for IoT network sensors are deployed on either a virtual machine or a physical appliance. OT sensors can be configured as cloud-connected sensors, or fully on-premises, locally managed sensors.
 
-## OT and Enterprise IoT network sensors
+## OT network sensors
 
 Defender for IoT network sensors discover and continuously monitor network traffic across your network devices.
 

articles/defender-for-iot/organizations/concept-supported-protocols.md

@@ -52,7 +52,6 @@ OT network sensors can detect the following protocols when identifying assets an
 |**Toshiba**     |Toshiba Computer Link         |
 |**Yokogawa**     |   Centum ODEQ (Centum / ProSafe DCS)<br> HIS Equalize<br> FA-M3<br> Vnet/IP      |
 
-
 [!INCLUDE [active-monitoring-protocols](includes/active-monitoring-protocols.md)]
 
 ## Supported protocols for Enterprise IoT device discovery

articles/defender-for-iot/organizations/how-to-manage-cloud-alerts.md

@@ -8,7 +8,7 @@ ms.custom: enterprise-iot
 
 # View and manage alerts from the Azure portal
 
-Microsoft Defender for IoT alerts enhance your network security and operations with real-time details about events logged in your network. This article describes how to manage Microsoft Defender for IoT alerts on the Azure portal, including alerts generated by OT and Enterprise IoT network sensors.
+Microsoft Defender for IoT alerts enhance your network security and operations with real-time details about events logged in your network. This article describes how to manage Microsoft Defender for IoT alerts on the Azure portal generated by the OT network sensors.
 
 - OT alerts are also available on each [OT network sensor console](how-to-view-alerts.md).
 

articles/defender-for-iot/organizations/how-to-manage-sensors-on-the-cloud.md

@@ -15,7 +15,6 @@ This article describes how to view and manage sensors with [Microsoft Defender f
 Before you can use the procedures in this article, you need to have network sensors onboarded to Defender for IoT. For more information, see:
 
 - [Onboard OT sensors to Defender for IoT](onboard-sensors.md)
-- [Enhance IoT security monitoring with an Enterprise IoT network sensor (Public preview)](eiot-sensor.md)
 
 ## View your sensors
 

articles/defender-for-iot/organizations/manage-subscriptions-enterprise.md

@@ -139,10 +139,6 @@ After you cancel your plan, the integration stops and you'll no longer get added
 
 The cancellation takes effect one hour after confirming the change.  This change appears on your next monthly statement, and you're charged based on the length of time the plan was in effect.
 
-> [!IMPORTANT]
->
-> If you've [registered an Enterprise IoT network sensor](eiot-sensor.md) (Public preview), device data collected by the sensor remains in your Microsoft Defender XDR instance. If you're canceling the Enterprise IoT plan because you no longer need the service, make sure to manually delete data from Microsoft Defender XDR as needed.
-
 ## Next steps
 
 For more information, see: