You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Microsoft Connected Cache is deployed as an IoT Edge module to the on-premises server.
26
-
2. Device Update for IoT Hub clients are configured to download content from Microsoft Connected Cache by virtue of the GatewayHostName attribute of the device connection string for IoT leaf devices **OR** parent_hostname set in the config.toml for IoT Edge child devices.
27
-
3. Device Update for IoT Hub clients in both cases receive update content download commands from the Device Update service and request update content from the Microsoft Connected Cache instead of the CDN. Microsoft Connected Cache listens on HTTP port 80 by default, and the Delivery Optimization client makes the content request on port 80 so the parent must be configured to listen on this port. Only the HTTP protocol is supported at this time.
26
+
2. Device Update for IoT Hub clients are configured to download content from Microsoft Connected Cache by virtue of either the GatewayHostName attribute of the device connection string for IoT leaf devices **or** the parent_hostname set in the config.toml for IoT Edge child devices.
27
+
3. Device Update for IoT Hub clients receive update content download commands from the Device Update service and request update content from the Microsoft Connected Cache instead of the CDN. Microsoft Connected Cache listens on HTTP port 80 by default, and the Delivery Optimization client makes the content request on port 80 so the parent must be configured to listen on this port. Only the HTTP protocol is supported at this time.
28
28
4. The Microsoft Connected Cache server downloads content from the CDN, seeds its local cache stored on disk and delivers the content to the Device Update client.
29
29
30
30
>[!Note]
@@ -36,6 +36,6 @@ Microsoft Connected Cache is an intelligent, transparent cache for content publi
36
36
37
37
When a downstream or child IoT Edge gateway is hosting a Microsoft Connected Cache server, it will be configured to request update content from the parent IoT Edge gateway, also hosting a Microsoft Connected Cache server. This request is repeated for as many levels as necessary before reaching the parent IoT Edge gateway hosting a Microsoft Connected Cache server that has internet access. From the internet connected server, the content is requested from the CDN at which point the content is delivered back to the child IoT Edge gateway that originally requested the content. The content will be stored on disk at every level.
38
38
39
-
## Access to the Microsoft Connected Cache preview for Device Update for IoT Hub
39
+
## Request access to the preview
40
40
41
41
The Microsoft Connected Cache IoT Edge module is released as a preview for customers who are deploying solutions using Device Update for IoT Hub. Access to the preview is by invitation. [Request Access](https://aka.ms/MCCForDeviceUpdateForIoT) to the Microsoft Connected Cache preview for Device Update for IoT Hub and provide the information requested if you would like access to the module.
Copy file name to clipboardExpand all lines: articles/iot-hub-device-update/device-update-security.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Security for Device Update for Azure IoT Hub | Microsoft Docs
3
3
description: Understand how Device Update for IoT Hub ensures devices are updated securely.
4
4
author: andrewbrownmsft
5
5
ms.author: andbrown
6
-
ms.date: 06/24/2022
6
+
ms.date: 08/19/2022
7
7
ms.topic: conceptual
8
8
ms.service: iot-hub
9
9
---
@@ -12,7 +12,7 @@ ms.service: iot-hub
12
12
13
13
Device Update for IoT Hub offers a secure method to deploy updates for device firmware, images, and applications to your IoT devices. The workflow provides an end-to-end secure channel with a full chain-of-custody model that a device can use to prove an update is trusted, unmodified, and intentional.
14
14
15
-
Each step in the Device Update workflow is protected through various security features and processes to ensure that every step in the pipeline performs a secured handoff to the next. The Device Update agent reference code identifies and properly manages any legitimate update requests. The reference agent also checks every download to ensure that the content is trusted, unmodified, and intentional.
15
+
Each step in the Device Update workflow is protected through various security features and processes to ensure that every step in the pipeline performs a secured handoff to the next. The Device Update agent reference code identifies and properly manages any illegitimate update requests. The reference agent also checks every download to ensure that the content is trusted, unmodified, and intentional.
0 commit comments