Skip to content

Commit 50f0fd2

Browse files
committed
edge-based security initial paragraph
1 parent 27c2dd6 commit 50f0fd2

File tree

1 file changed

+24
-6
lines changed

1 file changed

+24
-6
lines changed

articles/iot/iot-overview-security.md

Lines changed: 24 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -20,21 +20,39 @@ The following diagram shows a high-level view of the components in a typical edg
2020
<!-- Art Library Source# ConceptArt-0-000-032 -->
2121
:::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":::
2222

23-
Typically on an edge-based solution, you want to secure your end-to-end operations by using Azure security capabilities. Azure IoT Operations has built-in security capabilities such as [secrets management](../iot-operations/secure-iot-ops/howto-manage-secrets.md), [certificate management](../iot-operations/secure-iot-ops/concept-default-root-ca.md), and [secure settings](../iot-operations/deploy-iot-ops/howto-enable-secure-settings.md) on an Azure Arc-enabled Kubernetes cluster. When a Kubernetes cluster is connected to Azure, an outbound connection to Azure is initiated, using industry-standard SSL to secure data in transit, and several other security features are enabled, such as:
23+
Typically on an edge-based solution, you want to secure your end-to-end operations by using Azure security capabilities. Azure IoT Operations has built-in security capabilities such as [secrets management](../iot-operations/secure-iot-ops/howto-manage-secrets.md), [certificate management](../iot-operations/secure-iot-ops/concept-default-root-ca.md), and [secure settings](../iot-operations/deploy-iot-ops/howto-enable-secure-settings.md) on an [Azure Arc-enabled Kubernetes](/azure/azure-arc/kubernetes/overview) cluster. When a Kubernetes cluster is connected to Azure, an outbound connection to Azure is initiated, using industry-standard SSL to secure data in transit, and several other security features are enabled, such as:
2424

2525
- View and monitor your clusters using [Azure Monitor for containers](/azure/azure-monitor/containers/kubernetes-monitoring-enable).
26-
- Enforce threat protection using [Microsoft Defender for Containers](/azure/defender-for-cloud/defender-for-containers-enable).
26+
- Enforce threat protection using [Microsoft Defender for Containers](/azure/defender-for-cloud/defender-for-containers-introduction).
2727
- Ensure governance through applying policies with [Azure Policy for Kubernetes](/azure/governance/policy/concepts/policy-for-kubernetes).
2828
- Grant access and connect to your Kubernetes clusters from anywhere, and manage access by using [Azure role-based access control (RBAC)](/azure/azure-arc/kubernetes/azure-rbac) on your cluster.
2929

3030
You can divide security in an edge-based IoT solution into the following three areas:
3131

32-
- **Asset security**:
32+
- **Asset security**: Secure the physical or virtual item of value that you want to manage, monitor, and collect data from.
3333

34-
- **Connection security**:
34+
- **Connection security**: Ensure all data in transit between the asset, edge and cloud services is confidential and tamper-proof.
3535

36-
- **Edge and Cloud security**:
36+
- **Edge security**: Secure your data while it moves through, and is stored in the edge.
3737

38+
- **Cloud security**: Secure your data while it moves through, and is stored in the cloud.
39+
40+
## Microsoft Defender for IoT and for Containers
41+
42+
Microsoft Defender for IoT is a unified security solution built specifically to identify IoT and operational technology (OT) devices, vulnerabilities, and threats. Microsoft Defender for Containers is a cloud-native solution to improve, monitor, and maintain the security of your containerized assets (Kubernetes clusters, Kubernetes nodes, Kubernetes workloads, container registries, container images and more), and their applications, across multicloud and on-premises environments.
43+
44+
Both Defender for IoT and Defender for Containers can automatically monitor some of the recommendations included in this article. Defender for IoT and Defender for Containers should be the frontline of defense to protect your edge-based solution. To learn more, see:
45+
46+
- [Microsoft Defender for Containers - overview](/azure/defender-for-cloud/defender-for-containers-introduction)
47+
- [Microsoft Defender for IoT for organizations - overview](../defender-for-iot/organizations/overview.md).
48+
49+
## Asset security
50+
51+
## Connection security
52+
53+
## Edge security
54+
55+
## Cloud security
3856

3957
# [Cloud-based solution](#tab/cloud)
4058

@@ -56,7 +74,7 @@ Implementing the recommendations in this article helps you meet the security obl
5674

5775
## Microsoft Defender for IoT
5876

59-
Microsoft Defender for IoT can automatically monitor some of the recommendations included in this article. Microsoft Defender for IoT should be the frontline of defense to protect your resources in Azure. Microsoft Defender for IoT periodically analyzes the security state of your Azure resources to identify potential security vulnerabilities. It then provides you with recommendations on how to address them. To learn more, see:
77+
Microsoft Defender for IoT can automatically monitor some of the recommendations included in this article. Microsoft Defender for IoT should be the frontline of defense to protect your cloud-based solution. Microsoft Defender for IoT periodically analyzes the security state of your Azure resources to identify potential security vulnerabilities. It then provides you with recommendations on how to address them. To learn more, see:
6078

6179
- [Enhance security posture with security recommendations](../defender-for-iot/organizations/recommendations.md).
6280
- [What is Microsoft Defender for IoT for organizations?](../defender-for-iot/organizations/overview.md).

0 commit comments

Comments
 (0)