|
| 1 | +--- |
| 2 | +title: Firmware analysis for device builders - Microsoft Defender for IoT |
| 3 | +description: Learn how Microsoft Defender for IoT's firmware analysis helps device builders to market and deploy highly secure IoT/OT devices. |
| 4 | +ms.topic: conceptual |
| 5 | +ms.date: 06/15/2023 |
| 6 | +#Customer intent: As a device builder, I want to understand how firmware analysis can help secure my IoT/OT devices and products. |
| 7 | +--- |
| 8 | + |
| 9 | +# Firmware analysis for device builders |
| 10 | + |
| 11 | +Just like computers have operating systems, IoT devices have firmware, and it's the firmware that runs and controls IoT devices. For IoT device builders, security is a near-universal concern as IoT devices have traditionally lacked basic security measures. |
| 12 | + |
| 13 | +For example, IoT attack vectors typically use easily exploitable--but easily correctable--weaknesses such as hardcoded user accounts, outdated and vulnerable open-source packages, or a manufacturer's private cryptographic signing key. |
| 14 | + |
| 15 | +Use Microsoft Defender for IoT's firmware analysis to identify embedded security threats, vulnerabilities, and common weaknesses that may be otherwise undetectable. |
| 16 | + |
| 17 | +> [!NOTE] |
| 18 | +> The Defender for IoT **Firmware analysis** page is in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include other legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability. |
| 19 | +> |
| 20 | +
|
| 21 | +## How to be sure your firmware is secure |
| 22 | + |
| 23 | +Defender for IoT can analyze your firmware for common weaknesses and vulnerabilities, and provide insight into your firmware security. This analysis is useful whether you build the firmware in-house or receive firmware from your supply chain. |
| 24 | + |
| 25 | +- **Software bill of materials (SBOM)**: Receive a detailed listing of open-source packages used during the firmware's build process. See the package version and what license governs the use of the open-source package. |
| 26 | + |
| 27 | +- **CVE analysis**: See which firmware components have publicly known security vulnerabilities and exposures. |
| 28 | + |
| 29 | +- **Binary hardening analysis**: Identify binaries that haven't enabled specific security flags during compilation like buffer overflow protection, position independent executables, and more common hardening techniques. |
| 30 | + |
| 31 | +- **SSL certificate analysis**: Reveal expired and revoked TLS/SSL certificates. |
| 32 | + |
| 33 | +- **Public and private key analysis**: Verify that the public and private cryptographic keys discovered in the firmware are necessary and not accidental. |
| 34 | + |
| 35 | +- **Password hash extraction**: Ensure that user account password hashes use secure cryptographic algorithms. |
| 36 | + |
| 37 | +## Next steps |
| 38 | + |
| 39 | +- [Analyze a firmware image](tutorial-analyze-firmware.md) |
0 commit comments