AZ-220 Implement Security (15-20%)

Skills Measured:

Implement device authentication in the IoT Hub

  • Choose an appropriate form of authentication
  • Manage the X.509 certificates for a device
  • Manage the symmetric keys for a device

Implement device security by using DPS

  • Configure different attestation mechanisms with DPS
  • Generate and manage x.509 certificates for IoT Devices
  • Configure enrollment with x.509 certificates
  • Generate a TPM endorsements key for a device
  • Configure enrollment with symmetric keys

Implement Azure Security Center (ASC) for IoT

  • Enable ASC for IoT in Azure IoT Hub
  • Create security modules
  • Configure custom alerts

Homework:

AZ-220 IoT Labs

  • Module 10: Azure Security Center and IoT Security
    • Lab 19: Detect if your IoT Device was Tampered with Azure Security Center for IoT
      Exercise 1: Verify Lab Prerequisites
      Exercise 2: Enable Azure Security Center for IoT Hub
      Exercise 3: Create and Register a New Device
      Exercise 4: Create a Security Module Twin
      Exercise 5: Deploy Azure Security Center for IoT C# Security Agent
      Exercise 6: Configure Solution Management
      Exercise 7: Introduce custom alerts
      Exercise 8: Configure the Device App
      Exercise 9: Review Security Center Alerts

Quick Reference: Key Concepts and Terminology

  • Three widely used authentication types are X.509 certificates, Trusted Platform Modules (TPM), and symmetric keys.
    • X.509 certificate - A type of digital identity you can use for authentication. The X.509 certificate standard is documented in IETF RFC 5280. In Azure IoT, there are two ways to authenticate certificates:
      • Thumbprint. A thumbprint algorithm is run on a certificate to generate a hexadecimal string. The generated string is a unique identifer for the certificate.
      • CA authentication based on a full chain. A certificate chain is a hierarchical list of all certificates needed to authenticate an end-entity (EE) certificate. To authenticate an EE certificate, it’s necessary to authenticate each certificate in the chain including a trusted root CA.

      Pros for X.509

      • X.509 is the most secure authentication type supported in Azure IoT.
      • X.509 allows a high level of control for purposes of certificate management.
      • Many vendors are available to provide X.509 based authentication solutions.

      Cons for X.509

      • Many customers may need to rely on external vendors for their certificates.
      • Certificate management can be costly and adds to total solution cost.
      • Certificate life-cycle management can be difficult if logistics are not well thought out.
    • Trusted Platform Module (TPM) - A standard for securely generating and storing cryptographic keys, also known as ISO/IEC 11889. TPM also refers to a virtual or physical I/O device that interacts with modules that implement the standard. A TPM device can exist as discrete hardware, integrated hardware, a firmware-based module, or a software-based module. There are two key differences between TPMs and symmetric keys:
      • TPM chips can also store X.509 certificates.
      • TPM attestation in DPS uses the TPM endorsement key (EK), a form of asymmetric authentication. With asymmetric authentication, a public key is used for encryption, and a separate private key is used for decryption. In contrast, symmetric keys use symmetric authentication, where the private key is used for both encryption and decryption.

      Pros for TPM

      • TPMs are included as standard hardware on many Windows devices, with built-in support for the operating system.
      • TPM attestation is easier to secure than shared access signature (SAS) token-based symmetric key attestation.
      • You can easily expire and renew, or roll, device credentials. DPS automatically rolls the IoT Hub credentials whenever a TPM device is due for reprovisioning.

      Cons for TPM

      • TPMs are complex and can be difficult to use.
      • Application development with TPMs is difficult unless you have a physical TPM or a quality emulator.
      • You may have to redesign the board of your device to include a TPM in the hardware.
      • If you roll the EK on a TPM, it destroys the identity of the TPM and creates a new one. Although the physical chip stays the same, it has a new identity in your IoT solution.

    • Symmetric key - The same key is used to encrypt and decrypt messages. As a result, the same key is known to both the device and the service that authenticates it. Azure IoT supports SAS token-based symmetric key connections. Symmetric key authentication requires significant owner responsibility to secure the keys and achieve an equal level of security with X.509 authentication. If you use symmetric keys, the recommended practice is to protect the keys by using a hardware security module (HSM).

      Pros for symmetric key

      • Using symmetric keys is the simplest, lowest cost way to get started with authentication.
      • Using symmetric keys streamlines your process because there’s nothing extra to generate.

      Cons for symmetric key

      • Symmetric keys take a significant degree of effort to secure the keys. The same key is shared between device and cloud, which means the key must be protected in two places. In contrast, the challenge with TPM and X.509 certificates is proving possession of the public key without revealing the private key.
      • Symmetric keys make it easy to follow poor security practices. A common tendency with symmetric keys is to hard code the unencrypted keys on devices. While this practice is convenient, it leaves the keys vulnerable. You can mitigate some risk by securely storing the symmetric key on the device. However, if your priority is ultimately security rather than convenience, use X.509 certificates or TPM for authentication.

Resources

NOTE: In most cases, exams do NOT cover preview features, and some features will only be added to an exam when they are GA (General Availability).

Privacy & Cookies | Terms of Use | © Microsoft 2020 | This site is hosted for Microsoft by GitHub, also known as Microsoft. | Generated on 2021-02-12 23:24:14 +0000