Skip to content

Commit 679862f

Browse files
committed
Acrolinx
1 parent 25f5adf commit 679862f

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/iot/iot-overview-security.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ You can divide security in an edge-based IoT solution into the following three a
2424

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

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

2929
- **Edge security**: Secure your data while it moves through, and is stored in the edge.
3030

@@ -35,7 +35,7 @@ Typically on an edge-based solution, you want to secure your end-to-end operatio
3535
- View and monitor your clusters using [Azure Monitor for containers](/azure/azure-monitor/containers/kubernetes-monitoring-enable).
3636
- Enforce threat protection using [Microsoft Defender for Containers](/azure/defender-for-cloud/defender-for-containers-introduction).
3737
- Ensure governance through applying policies with [Azure Policy for Kubernetes](/azure/governance/policy/concepts/policy-for-kubernetes).
38-
- 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.
38+
- Grant access and connect to your Kubernetes clusters from anywhere, and manage access by using [Azure role-based access control (Azure RBAC)](/azure/azure-arc/kubernetes/azure-rbac) on your cluster.
3939

4040
## Microsoft Defender for IoT and for Containers
4141

@@ -56,7 +56,7 @@ Both Defender for IoT and Defender for Containers can automatically monitor some
5656

5757
- **Enable secure updates for asset firmware**: Use services that enable over-the-air updates for your assets. Build assets with secure paths for updates and cryptographic assurance of firmware versions to secure your assets during and after updates.
5858

59-
- **Deploy asset hardware securely**: Ensure that asset hardware deployment is as tamper-proof as possible, especially in unsecure locations such as public spaces or unsupervised locales. Only enable necessary features to minimize the physical attack footprint, such as securely covering USB ports if they are not needed.
59+
- **Deploy asset hardware securely**: Ensure that asset hardware deployment is as tamper-proof as possible, especially in unsecure locations such as public spaces or unsupervised locales. Only enable necessary features to minimize the physical attack footprint, such as securely covering USB ports if they aren't needed.
6060

6161
- **Follow device manufacturer security and deployment best practices**: If the device manufacturer provides security and deployment guidance, follow that guidance in addition to the generic guidance listed in this article.
6262

@@ -90,7 +90,7 @@ Both Defender for IoT and Defender for Containers can automatically monitor some
9090

9191
- **Deploy observability resources and set up logs**: Observability provides visibility into every layer of your Azure IoT Operations configuration. It gives you insight into the actual behavior of issues, which increases the effectiveness of site reliability engineering. Azure IoT Operations offers observability through custom curated Grafana dashboards that are hosted in Azure. These dashboards are powered by Azure Monitor managed service for Prometheus and by Container Insights. [Deploy observability resources](../iot-operations/configure-observability-monitoring/howto-configure-observability.md) on your cluster before deploying Azure IoT Operations.
9292

93-
- **Secure access to assets and asset endpoints with Azure role-based access control (Azure RBAC)**: Assets and asset endpoints in Azure IoT Operations have representations in both the Kubernetes cluster and the Azure portal. You can use Azure role-based access control (Azure RBAC) to secure access to these resources. Azure RBAC is an authorization system that enables you to manage access to Azure resources. You can use Azure RBAC to grant permissions to users, groups, and applications at a certain scope. To learn more, see [Secure access to assets and asset endpoints](../iot-operations/discover-manage-assets/howto-secure-assets.md).
93+
- **Secure access to assets and asset endpoints with Azure RBAC**: Assets and asset endpoints in Azure IoT Operations have representations in both the Kubernetes cluster and the Azure portal. You can use Azure RBAC to secure access to these resources. Azure RBAC is an authorization system that enables you to manage access to Azure resources. You can use Azure RBAC to grant permissions to users, groups, and applications at a certain scope. To learn more, see [Secure access to assets and asset endpoints](../iot-operations/discover-manage-assets/howto-secure-assets.md).
9494

9595

9696
# [Cloud-based solution](#tab/cloud)
@@ -101,7 +101,7 @@ The following diagram shows a high-level view of the components in a typical clo
101101
:::image type="content" source="media/iot-overview-security/iot-cloud-security-architecture.svg" alt-text="Diagram that shows the high-level IoT cloud-based solution architecture highlighting security." border="false":::
102102

103103

104-
You can divide security in an cloud-based IoT solution into the following three areas:
104+
You can divide security in a cloud-based IoT solution into the following three areas:
105105

106106
- **Device security**: Secure the IoT device while it's deployed in the wild.
107107

@@ -141,7 +141,7 @@ Microsoft Defender for IoT can automatically monitor some of the recommendations
141141

142142
- **Keep the system up-to-date**: Ensure that device operating systems and all device drivers are upgraded to the latest versions. Keeping operating systems up-to-date helps ensure that they're protected against malicious attacks.
143143

144-
- **Protect against malicious activity**: If the operating system permits, install the latest antivirus and antimalware capabilities on each device operating system.
144+
- **Protect against malicious activity**: If the operating system permits, install the latest antivirus and anti-malware capabilities on each device operating system.
145145

146146
- **Audit frequently**: Auditing IoT infrastructure for security-related issues is key when responding to security incidents. Most operating systems provide built-in event logging that you should review frequently to make sure no security breach has occurred. A device can send audit information as a separate telemetry stream to the cloud service where it can be analyzed.
147147

0 commit comments

Comments
 (0)