Merge pull request #272438 from tarTech23/rtos

Replace azure rtos

Author: JamesJBarnett

.openpublishing.redirection.defender-for-iot.json

@@ -1,5 +1,35 @@
 {
-    "redirections": [          
+    "redirections": [  
+        {
+            "source_path_from_root": "/articles/defender-for-iot/device-builders/how-to-azure-rtos-security-module.md",
+            "redirect_url": "/azure/defender-for-iot/device-builders/how-to-threadx-security-module",
+            "redirect_document_id": false
+        }, 
+        {
+            "source_path_from_root": "/articles/defender-for-iot/device-builders/iot-security-azure-rtos.md",
+            "redirect_url": "/azure/defender-for-iot/device-builders/iot-security-threadx",
+            "redirect_document_id": false
+        }, 
+        {
+            "source_path_from_root": "/articles/defender-for-iot/device-builders/azure-rtos-security-module-api.md",
+            "redirect_url": "/azure/defender-for-iot/device-builders/threadx-security-module-api",
+            "redirect_document_id": false
+        }, 
+        {
+            "source_path_from_root": "/articles/defender-for-iot/device-builders/concept-rtos-security-alerts-recommendations.md",
+            "redirect_url": "/azure/defender-for-iot/device-builders/concept-threadx-security-alerts-recommendations",
+            "redirect_document_id": false
+        }, 
+        {
+            "source_path_from_root": "/articles/defender-for-iot/device-builders/concept-rtos-security-module.md",
+            "redirect_url": "/azure/defender-for-iot/device-builders/concept-threadx-security-module",
+            "redirect_document_id": false
+        },         
+        {
+            "source_path_from_root": "/articles/defender-for-iot/device-builders/how-to-rtos-security-module.md",
+            "redirect_url": "/azure/defender-for-iot/device-builders/how-to-threadx-security-module",
+            "redirect_document_id": false
+        },         
         {
             "source_path_from_root": "/articles/defender-for-iot/organizations/resources-manage-proprietary-protocols.md",
             "redirect_url": "/azure/defender-for-iot/organizations/how-to-manage-individual-sensors#manage-custom-plugins-legacy",

articles/defender-for-iot/device-builders/TOC.yml

@@ -41,7 +41,7 @@
 - name: Concepts
   items:
   - name: Agent portfolio overview and OS support 
-    displayName: standalone agent, micro agent, RTOS
+    displayName: standalone agent, micro agent, Eclipse Threadx
     href: concept-agent-portfolio-overview-os-support.md
   - name: Standalone micro agent overview 
     displayName: endpoint, posture, distribution, flexible, model
@@ -97,15 +97,15 @@
   - name: Create custom alerts
     displayName: security group
     href: quickstart-create-custom-alerts.md
-  - name: Defender-IoT-micro-agent for Azure RTOS (Preview)
-    href: iot-security-azure-rtos.md
+  - name: Defender-IoT-micro-agent for Eclipse ThreadX (Preview)
+    href: iot-security-threadx.md
     items:
-    - name: Work with Defender-IoT-micro-agent for Azure RTOS (Preview)
-      href: how-to-azure-rtos-security-module.md
-    - name: Understand the Defender-IoT-micro-agent for Azure RTOS (Preview)
-      href: concept-rtos-security-module.md
-    - name: Defender-IoT-micro-agent for Azure RTOS alerts and recommendations (Preview)
-      href: concept-rtos-security-alerts-recommendations.md
+    - name: Work with Defender-IoT-micro-agent for Eclipse ThreadX (Preview)
+      href: how-to-threadx-security-module.md
+    - name: Understand the Defender-IoT-micro-agent for Eclipse ThreadX (Preview)
+      href: concept-threadx-security-module.md
+    - name: Defender-IoT-micro-agent for Eclipse ThreadX alerts and recommendations (Preview)
+      href: concept-threadx-security-alerts-recommendations.md
   - name: Manage cloud device inventory
     href: how-to-manage-device-inventory-on-the-cloud.md
     displayName: device inventory, device, inventory, EIoT, eiot
@@ -182,9 +182,9 @@
     href: how-to-investigate-device.md
 - name: Reference
   items:
-  - name: Defender-IoT-micro-agent for Azure RTOS API (Preview)
+  - name: Defender-IoT-micro-agent for Eclipse ThreadX API (Preview)
     displayName: prototype, disable
-    href: azure-rtos-security-module-api.md
+    href: threadx-security-module-api.md
   - name: Frequently asked questions
     displayName: FAQ, embedded, dependencies, data, quota, internet, 
     href: resources-agent-frequently-asked-questions.md
@@ -209,7 +209,4 @@
     href: https://azure.microsoft.com/pricing/details/azure-defender/
   - name: Videos
     href: https://azure.microsoft.com/resources/videos/index/?services=security-center&service=internet-of-things&page=1&sort=newest
-  - name: Agent-based solution for device builders
-    items: 
-  - name: Azure RTOS Defender-IoT-micro-agent on Stack Overflow
-    href: https://stackoverflow.com/questions/tagged/azure-rtos+azure-iot-security-module
+  

articles/defender-for-iot/device-builders/agent-based-security-custom-alerts.md

@@ -2,7 +2,7 @@
 title: Agent based security custom alerts
 description: Learn about customizable security alerts and recommended remediation using Defender for IoT device's features and service.
 ms.topic: conceptual
-ms.date: 03/28/2022
+ms.date: 04/17/2024
 ---
 
 
@@ -18,12 +18,11 @@ The following lists of Defender for IoT alerts are definable by you based on you
 
 | Severity | Alert name | Data source | Description | Suggested remediation |
 |--|--|--|--|--|
-| Low | Custom alert - The number of active connections is outside the allowed range | Legacy Defender-IoT-micro-agent, Azure RTOS | Number of active connections within a specific time window is outside the currently configured and allowable range. | Investigate the device logs. Learn where the connection originated and determine if it is benign or malicious. If malicious, remove possible malware and understand source. If benign, add the source to the allowed connection list. |
-| Low | Custom alert - The outbound connection created to an IP that isn't allowed | Legacy Defender-IoT-micro-agent, Azure RTOS | An outbound connection was created to an IP that is outside your allowed IP list. | Investigate the device logs. Learn where the connection originated and determine if it is benign or malicious. If malicious, remove possible malware and understand source. If benign, add the source to the allowed IP list. |
-| Low | Custom alert - The number of failed local logins is outside the allowed range | Legacy Defender-IoT-micro-agent, Azure RTOS | The number of failed local logins within a specific time window is outside the currently configured and allowable range. |  |
-| Low | Custom alert - The sign in of a user that is not on the allowed user list | Legacy Defender-IoT-micro-agent, Azure RTOS | A local user outside your allowed user list, logged in to the device. | If you are saving raw data, navigate to your log analytics account and use the data to investigate the device, identify the source, and then fix the allow/block list for those settings. If you are not currently saving raw data, go to the device and fix the allow/block list for those settings. |
-| Low | Custom alert - A process was executed that is not allowed | Legacy Defender-IoT-micro-agent, Azure RTOS | A process that is not allowed was executed on the device. | If you are saving raw data, navigate to your log analytics account and use the data to investigate the device, identify the source, and then fix the allow/block list for those settings. If you are not currently saving raw data, go to the device and fix the allow/block list for those settings. |
-|
+| Low | Custom alert - The number of active connections is outside the allowed range | Legacy Defender-IoT-micro-agent, Eclipse ThreadX | Number of active connections within a specific time window is outside the currently configured and allowable range. | Investigate the device logs. Learn where the connection originated and determine if it's benign or malicious. If malicious, remove possible malware and understand source. If benign, add the source to the allowed connection list. |
+| Low | Custom alert - The outbound connection created to an IP that isn't allowed | Legacy Defender-IoT-micro-agent, Eclipse ThreadX | An outbound connection was created to an IP that is outside your allowed IP list. | Investigate the device logs. Learn where the connection originated and determine if it's benign or malicious. If malicious, remove possible malware and understand source. If benign, add the source to the allowed IP list. |
+| Low | Custom alert - The number of failed local logins is outside the allowed range | Legacy Defender-IoT-micro-agent, Eclipse ThreadX | The number of failed local logins within a specific time window is outside the currently configured and allowable range. |  |
+| Low | Custom alert - The sign in of a user that isn't on the allowed user list | Legacy Defender-IoT-micro-agent, Eclipse ThreadX | A local user outside your allowed user list, logged in to the device. | If you're saving raw data, navigate to your log analytics account and use the data to investigate the device, identify the source, and then fix the allow/block list for those settings. If you aren't currently saving raw data, go to the device and fix the allow/block list for those settings. |
+| Low | Custom alert - A process was executed that isn't allowed | Legacy Defender-IoT-micro-agent, Eclipse ThreadX | A process that isn't allowed was executed on the device. | If you're saving raw data, navigate to your log analytics account and use the data to investigate the device, identify the source, and then fix the allow/block list for those settings. If you aren't currently saving raw data, go to the device and fix the allow/block list for those settings. |
 
 ## Next steps
 

articles/defender-for-iot/device-builders/concept-agent-portfolio-overview-os-support.md

@@ -1,7 +1,7 @@
 ---
 title: Agent portfolio overview and OS support
 description: Microsoft Defender for IoT provides a large portfolio of agents based on the device type. 
-ms.date: 01/09/2022
+ms.date: 04/17/2024
 ms.topic: conceptual
 ---
 
@@ -28,9 +28,9 @@ For additional information on supported operating systems, or to request access
 
 For a more granular view of the micro agent-operating system dependencies, see [Linux dependencies](concept-micro-agent-linux-dependencies.md#linux-dependencies).
 
-## Azure RTOS micro agent
+## Eclipse ThreadX micro agent
 
-The Microsoft Defender for IoT micro agent comes built in as part of the Azure RTOS NetX Duo component, and monitors the device's network activity. The micro agent consists of a comprehensive and lightweight security solution that provides coverage for common threats, and potential malicious activities on a real-time operating system (RTOS) devices.
+The Microsoft Defender for IoT micro agent comes built in as part of the FileX NetX Duo component, and monitors the device's network activity. The micro agent consists of a comprehensive and lightweight security solution that provides coverage for common threats, and potential malicious activities on a real-time operating system (FileX) devices.
 
 ## Next steps
 

articles/defender-for-iot/device-builders/concept-event-aggregation.md

@@ -1,7 +1,7 @@
 ---
 title: Micro agent event collection
 description: Defender for IoT security agents collect data and system events from your local device, and send the data to the Azure cloud for processing, and analytics.
-ms.date: 04/26/2022
+ms.date: 04/17/2024
 ms.topic: conceptual
 ---
 
@@ -54,7 +54,7 @@ Network activity events are considered identical when the local port, remo
 
 The default buffer for a network activity event is 256. For situations where the cache is full:
 
-- **Azure RTOS devices**: No new network events will be cached until the next collection cycle starts.  
+- **Eclipse ThreadX devices**: No new network events will be cached until the next collection cycle starts.  
 
 - **Linux devices**: The oldest event will be replaced by every new event. A warning to increase the cache size will be logged.
 

articles/defender-for-iot/device-builders/concept-rtos-security-module.md

@@ -1,15 +1,15 @@
 ---
 title: Standalone micro agent overview 
 description: The Microsoft Defender for IoT security agents allow you to build security directly into your new IoT devices and Azure IoT projects.
-ms.date: 01/12/2023
+ms.date: 04/17/2024
 ms.topic: conceptual
 ---
 
 # Standalone micro agent overview
 
 Security is a near-universal concern for IoT implementers. IoT devices have unique needs for endpoint monitoring, security posture management, and threat detection – all with highly specific performance requirements.
 
-The Microsoft Defender for IoT security agent allows you to build security directly into your new IoT devices and Azure IoT projects. The micro agent has flexible deployment options, including the ability to deploy as a binary package or modify source code, and it's available for standard IoT operating systems like Linux and Azure RTOS.
+The Microsoft Defender for IoT security agent allows you to build security directly into your new IoT devices and Azure IoT projects. The micro agent has flexible deployment options, including the ability to deploy as a binary package or modify source code, and it's available for standard IoT operating systems like Linux and Eclipse ThreadX.
 
 The Microsoft Defender for IoT micro agent provides endpoint visibility into security posture management, threat detection, and integration into Microsoft's other security tools for unified security management.