Introduction
Welcome to the learning path about the cloud-connected Altair 8800 on Azure Sphere. In this module, you'll learn how to help secure an Altair emulator that runs on Azure Sphere.
Scenario: IoT security
The traditional approach to Internet of Things (IoT) development is that, as an IoT developer, you're responsible for integrating and maintaining all aspects of a solution. You're responsible for security, authentication, certificates, identity, encryption libraries, update processes, your solution, and more. Not only are you a solutions expert, but you're also charged with tracking new and emerging security threats, mitigating the threats, and updating the solutions to protect IoT devices.
Azure Sphere is a highly secure IoT platform. It's designed to help manage identity, certificate, reporting, operating system, and application updates. Because Azure Sphere helps manage security on your behalf, you're freer to focus on the IoT solutions you're building.
Azure Sphere helps ensure greater security by design. As a result, apps that run on Azure Sphere can be considered more secure. As a developer, you grant certain capabilities to these apps. Granting specific capabilities and permissions is key to Azure Sphere security. When you do so, it's important to adhere to the principle of least privilege. That is, you grant only the capabilities that the Azure Sphere app needs to run correctly, and no more.
What will you learn?
In this module, you'll learn how to declare the network endpoint capabilities for Azure IoT Central and a Message Queuing Telemetry Transport (MQTT) broker. The Altair emulator can connect only to declared network endpoints.
What is the main goal?
This module focuses on clarifying how you declare the network endpoints that the Altair emulator will be using.