Firmware underpins IoT, OT, and network-device security, yet remains difficult to inventory, assess, and secure continuously.
Earlier this year, we expanded firmware analysis enabled by Azure Arc to connect vulnerabilities to devices through Azure Device Registry, enrich CVE prioritization, analyze complex firmware, and improve software-supply-chain collaboration.
At Microsoft Ignite, we're adding capabilities to surface firmware insights in device management, identify potentially risky function calls, refresh vulnerability information, and expand component discovery.
These updates turn point-in-time firmware assessments into actionable insights across the device lifecycle.
Bringing firmware security insights directly into Azure Device Registry
In April, we introduced an integration between firmware analysis and Azure Device Registry (ADR) that maps analyzed firmware to the devices and assets running it, revealing fleet impact rather than an isolated scan result.
At Ignite, we’re bringing firmware security insights directly into the Azure Device Registry experience.
From an ADR device or asset, customers can view a firmware security summary, see whether vulnerabilities appear in the CISA Known Exploited Vulnerabilities (KEV) Catalog, and open the full firmware analysis report. Firmware is associated with devices and assets by manufacturer, model, and software version.
Why it matters: Security teams can move from a vulnerability to affected devices, while operations teams can move from a device to firmware risk. Connecting firmware analysis and ADR reduces manual correlation and helps teams prioritize devices exposed to vulnerabilities known to be exploited in the wild.
This makes firmware security part of the device-management lifecycle rather than a separate workflow.
Keep firmware vulnerability information current with Latest CVEs
A firmware image doesn't become static from a security perspective simply because its bits haven't changed.
A firmware image’s security posture can change even when its bits do not. New CVEs or updated vulnerability data can introduce risk after the original analysis, requiring customers to re-upload firmware and compare results manually.
With Latest CVEs, now in Preview, firmware analysis provides a refreshed view of vulnerabilities affecting an existing firmware image while preserving the original results for comparison and audit. It includes original and newly identified CVEs, relevant metadata changes, and additions to the CISA Known Exploited Vulnerabilities (KEV) Catalog—the authoritative catalog of vulnerabilities with evidence of exploitation in the wild.
Customers can compare Original results captured at upload with the Latest view and filter for newly identified CVEs or severity-impacting metadata changes.
Why it matters: Firmware may remain deployed for years, so teams need a fresh risk picture—not only the original assessment. Latest CVEs surfaces newly introduced risk, including when a vulnerability enters CISA KEV, and helps identify affected firmware and devices for priority patching, mitigation, or investigation.
Finding potentially unsafe function calls in firmware
Vulnerabilities aren't limited to known CVEs. Security issues can also originate in the way firmware itself is implemented.
The new Unsafe Function Calls analysis, now in preview, scans supported ELF executables for functions that can create security issues without controls such as input validation, bounds checking, and buffer-size validation.
The preview identifies calls to functions including strcpy, strcat, printf, fprintf, sprintf, system, mmap, and popen. It also surfaces network-related function-call information, allowing analysts to consider prioritizing executables containing both unsafe function calls and network-related calls for further review.
This helps security and firmware-engineering teams identify binaries for deeper review and investigate risky implementation patterns beyond CVE analysis.
A flagged function does not necessarily indicate a vulnerability; exploitability depends on its use, input data, and surrounding protections.
The preview supports ELF user-space executables on AMD64/x86-64, ARM64/AArch64, ARM32 and MIPS32.
Broader SBOM discovery across firmware
An accurate Software Bill of Materials is essential to firmware risk assessment: unidentified components cannot be reliably mapped to disclosed vulnerabilities.
Over the past few months we have added 70 new SBOM component detectors to expand discovery of software embedded in firmware images.
These detectors expand the range of software components that firmware analysis can identify, improving software inventory visibility and supporting component-level vulnerability analysis.
This expansion addresses component-discovery gaps across real-world firmware through ongoing validation of customer firmware and comparison results.
Why it matters: Better component discovery improves software-supply-chain visibility and helps identify affected firmware when vulnerabilities are disclosed.
Extending firmware security visibility beyond the initial scan
Together, these capabilities make firmware security insights broader, more current, and easier to operationalize:
- Azure Device Registry integration connects firmware security posture—including CISA KEV findings—to the devices and assets customers manage.
- Latest CVEs helps customers understand how firmware vulnerability posture changes after initial analysis and prioritize affected firmware and devices when a CVE is added to CISA KEV.
- Unsafe Function Calls analysis adds another layer of static security analysis beyond known vulnerabilities and software inventory.
- Expanded SBOM detection increases visibility into the software components that make up firmware.
Firmware security should continue after the scan by connecting findings to devices, detecting risks beyond CVEs, tracking vulnerabilities over time, and maintaining visibility into fleet software.
These investments in firmware analysis, enabled by Azure Arc and Azure Device Registry, make firmware security more visible, actionable, and integrated into edge management and security.
As always, we welcome customer feedback as we expand firmware analysis.