Merge pull request #295333 from asergaz/naming-iot

iot-overview-security PG suggested changes

Author: v-ccolin

articles/iot-operations/breadcrumb/toc.yml

@@ -0,0 +1,15 @@
+- name: Azure
+  tocHref: /azure
+  topicHref: /azure/index
+  items: 
+  - name: Internet of Things
+    tocHref: /azure/iot/
+    topicHref: /azure/iot/index
+    items:
+    - name: IoT Operations
+      tocHref: /azure/iot-operations/
+      topicHref: /azure/iot-operations/index
+    #For Contextual TOC
+    - name: IoT Operations
+      tocHref: /azure/iot/
+      topicHref: /azure/iot-operations/index

articles/iot-operations/toc.yml

@@ -39,6 +39,8 @@ items:
         href: secure-iot-ops/howto-manage-secrets.md
       - name: Validate images
         href: secure-iot-ops/howto-validate-images.md
+      - name: Secure your solution
+        href: ../iot/iot-overview-security.md?toc=/azure/iot-operations/toc.json&bc=/azure/iot-operations/breadcrumb/toc.json&tabs=edge
     - name: Discover and manage assets
       items:
       - name: Asset management overview

articles/iot/iot-overview-security.md

@@ -21,7 +21,7 @@ The following diagram shows a high-level view of the components in a typical edg
 <!-- Art Library Source# ConceptArt-0-000-032 -->
 :::image type="content" source="media/iot-overview-security/iot-edge-security-architecture.svg" alt-text="Diagram that shows the high-level IoT edge-based solution architecture highlighting security." border="false":::
 
-You can divide security in an edge-based IoT solution into the following three areas:
+You can divide security in an edge-based IoT solution into the following four areas:
 
 - **Asset security**: Secure the physical or virtual item of value that you want to manage, monitor, and collect data from.
 
@@ -83,8 +83,6 @@ Both Defender for IoT and Defender for Containers can automatically monitor some
 
 - **Provide the least privilege needed for the topic asset in your MQTT broker**: Authorization policies determine what actions the clients can perform on the broker, such as connecting, publishing, or subscribing to topics. Configure the MQTT broker to use one or multiple authorization policies with the BrokerAuthorization resource. To learn more, see [Configure MQTT broker authorization](../iot-operations/manage-mqtt-broker/howto-configure-authorization.md).
 
-- **Configure isolated network environments by using Azure IoT Layered Network Management (preview)**: Azure IoT Layered Network Management (preview) is a component that facilitates the connection between Azure and clusters in isolated network environments. In industrial scenarios, the isolated networks follow the *[ISA-95](https://www.isa.org/standards-and-publications/isa-standards/isa-standards-committees/isa95)/[Purdue Network architecture](https://en.wikipedia.org/wiki/Purdue_Enterprise_Reference_Architecture)*. To learn more, see [What is Azure IoT Layered Network Management (preview)?](../iot-operations/manage-layered-network/overview-layered-network.md).
-
 ## Cloud security
 
 - **Use user-assigned managed identities for cloud connections**: Always use managed identity authentication. When possible, [use user-assigned managed identity](../iot-operations/connect-to-cloud/howto-configure-mqtt-endpoint.md#user-assigned-managed-identity) in data flow endpoints for flexibility and auditability.