News

Azure IoT Dev Tooling, Security Service Make GA Debuts

Microsoft-centric Internet of Things (IoT) development was bolstered with the recent release of Azure IoT Edge Tooling and Azure Security Center for IoT, both of which are now generally available.

Azure IoT Edge, described as cloud intelligence deployed locally on IoT edge devices, is a fully managed service built on Azure IoT Hub, helping developers deploy AI, services from Azure or third parties and custom business logic to edge devices in containers.

The open source project hit GA in June, working with use cases such as machine learning, stream analytics, SQL Server databases and more.

Now, the associated tooling has also become generally available, consisting of:

More information on the tooling is available here.

Microsoft also announced the general availability of the Azure Security Center for IoT, which helps developers and pros manage their security posture for cloud workloads, follow best practices and fix common Azure infrastructure misconfigurations.

"Azure Security Center allows you to protect your end-to-end IoT deployment by identifying and responding to emerging threats, as well as finding issues in your configurations before attackers can use them to compromise your deployment," Microsoft said. "As organizations use Azure Security Center for IoT to manage their security roadblocks, they remove the barriers keeping them from business transformation."

Azure Security Center for IoT
[Click on image for larger view.] Azure Security Center for IoT (source: Microsoft).

The company said the security service goes beyond just protecting devices, a common target, also covering IoT components such as cloud services, supporting infrastructure, and the accounts of admins who access them. Microsoft claims the service is the first of its kind to prevent, detect and help remediate potential attacks against such a variety of IoT components including small sensors, edge computing devices and gateways, Azure IoT Hub, the compute, storage, databases and AI/ML workloads.

The service provides a list of potential threats, ranked by importance, along with possible misconfigurations and insecure settings to help with remediation and fixes.

Microsoft said its emphasis on IoT security addresses a major problem, as exemplified in Bain research that indicates security concerns are the main reason organizations have slowed or paused IoT implementations.

"Because IoT requires integrating many different technologies (heterogeneous devices must be linked to IoT cloud services that connect to analytics services and business applications), organizations face the challenge of securing both the pieces of their IoT solution and the connections between those pieces," Microsoft said. "Attackers target weak spots; even one weak device configuration, cloud service, or admin account can provide a way into your solution."

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube