#SCOPEBOX SERIAL KEY HOW TO#
#SCOPEBOX SERIAL KEY INSTALL#
#SCOPEBOX SERIAL KEY UPDATE#

The code will simulate a device using a sample from the Azure IoT C SDK. The device code demonstrated in this article will follow the same pattern as the Quickstart: Provision a simulated symmetric key device. The device will use that derived device key with its unique registration ID to attest with the Device Provisioning Service and be assigned to an IoT hub. That master key will be used to hash each unique registration ID to produce a unique device key for each device. The enrollment group will include a group master key. For example, the MAC address or a serial number.ДЄn enrollment group that uses symmetric key attestation will be created with the Device Provisioning Service. Visual Studio 2015 and Visual Studio 2017 are also supported.ДЄ unique registration ID will be defined for each device based on information that identifies that device. Visual Studio 2019 with the 'Desktop development with C++' workload enabled. For Linux or macOS, see the appropriate section in Prepare your development environment in the SDK documentation. The following prerequisites are for a Windows development environment.

Completion of the Set up IoT Hub Device Provisioning Service with the Azure portal quickstart.

You can also create individual enrollments using the sample. You can follow the instructions in this article to create a symmetric key enrollment group using the portal and to find the ID Scope and enrollment group primary and secondary keys needed to run the sample. To use this sample, download or clone the azure-iot-samples-csharp repository and follow the in-line instructions in the sample code. There is also a C# device provisioning symmetric key sample available. The sample used in this article is written in C.

#SCOPEBOX SERIAL KEY HOW TO#

For a Linux example, see How to provision for multitenancy. However, you can perform the procedures on Linux.

This article is oriented toward a Windows-based workstation.

#SCOPEBOX SERIAL KEY UPDATE#

This article also assumes that the device update takes place in a secure environment to prevent unauthorized access to the master group key or the derived device key. However, it is assumed that you do have some method of updating device code to use the Device Provisioning Service to provision these devices. This article assumes that neither an HSM or a certificate is a viable option. Using an HSM will allow you to bypass updating the code deployed to all your devices, and you would not have a secret key embedded in your device images.

#SCOPEBOX SERIAL KEY INSTALL#

If you can easily install a hardware security module (HSM) and a certificate, then that may be a better approach for identifying and provisioning your devices. Symmetric key attestation can be used to identify a device based off unique information like the MAC address or a serial number. The Device Provisioning Service includes symmetric key attestation. Some devices may not have a certificate, TPM, or any other security feature that can be used to securely identify the device. This article demonstrates how to securely provision multiple simulated symmetric key devices to a single IoT Hub using an enrollment group.

Scopebox serial key