Adding changes and what's new

Author: limwainstein

.openpublishing.redirection.json

@@ -3769,6 +3769,11 @@
       "source_path_from_root": "/articles/defender-for-iot/device-builders/defender-iot-firmware-analysis-faq.md",
       "redirect_url": "/azure/firmware-analysis/overview-firmware-analysis",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/defender-for-iot/device-builders/defender-iot-firmware-analysis-rbac.md",
+      "redirect_url": "/azure/firmware-analysis/overview-firmware-analysis",
+      "redirect_document_id": false
     }
   ]
 }

articles/defender-for-iot/device-builders/TOC.yml

@@ -16,10 +16,10 @@
     href: quickstart-onboard-iot-hub.md
   - name: Upload Firmware using Azure CLI
     displayName: Azure CLI, upload, firmware
-    href: quickstart-upload-firmware-using-azure-command-line-interface.md
+    href: /azure/firmware-analysis/quickstart-upload-firmware-using-azure-command-line-interface
   - name: Upload Firmware using Azure PowerShell
     displayName: Azure PowerShell, upload, firmware
-    href: quickstart-upload-firmware-using-powershell.md
+    href: /azure/firmware-analysis/quickstart-upload-firmware-using-powershell
   expanded: true
 - name: Tutorials
   items:
@@ -36,7 +36,7 @@
   - name: Investigate security alerts
     href: tutorial-investigate-security-alerts.md
   - name: Analyze an IoT/OT firmware image
-    href: tutorial-analyze-firmware.md
+    href: /azure/firmware-analysis/tutorial-analyze-firmware
 - name: Concepts
   items:
   - name: Agent portfolio overview and OS support
@@ -72,7 +72,7 @@
     href: overview-firmware-analysis.md
   - name: Azure role-based access control for Defender for IoT Firmware analysis
     displayName: RBAC, role, access, control, firmware, analysis
-    href: defender-iot-firmware-analysis-rbac.md
+    href: /azure/firmware-analysis/firmware-analysis-rbac
 - name: How-to guides
   items:
   - name: Install Defender for IoT micro agent for Edge

articles/defender-for-iot/device-builders/defender-iot-firmware-analysis-rbac.md

@@ -1,6 +1,8 @@
 ---
 title: Azure role-based access control for Defender for IoT Firmware analysis
 description: Learn about how to use Azure Role-Based Access Control for Defender for IoT Firmware Analysis.
+ms.author: lwainstein
+author: limwainstein
 ms.topic: conceptual
 ms.date: 01/10/2024
 ---

articles/defender-for-iot/device-builders/overview-firmware-analysis.md

@@ -12,32 +12,19 @@ Just like computers have operating systems, IoT devices have firmware, and it's
 
 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. 
 
-Use Microsoft Defender for IoT's firmware analysis to identify embedded security threats, vulnerabilities, and common weaknesses that may be otherwise undetectable.
+Use firmware analysis to identify embedded security threats, vulnerabilities, and common weaknesses that may be otherwise undetectable.
+
+For more information on firmware analysis for device builders, see the [firmware analysis documentation](/azure/firmware-analysis/overview-firmware-analysis).
 
 > [!NOTE]
 > 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.
 >
 
-## How to be sure your firmware is secure
-
-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.
-
-- **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.
-
-- **CVE analysis**: See which firmware components have publicly known security vulnerabilities and exposures.
-
-- **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.
-
-- **SSL certificate analysis**: Reveal expired and revoked TLS/SSL certificates.
-
-- **Public and private key analysis**: Verify that the public and private cryptographic keys discovered in the firmware are necessary and not accidental.
-
-- **Password hash extraction**: Ensure that user account password hashes use secure cryptographic algorithms.  
+## How to access firmware analysis
 
-:::image type="content" source="media/tutorial-firmware-analysis/overview.png" alt-text="Screenshot that shows the overview page of the analysis results.":::
+You can access firmware analysis data in one of two ways:
 
-## Next steps
+- In Defender for IoT, select **Firmware analysis**.
+- In the Azure portal, select **Firmware analysis**.
 
-- [Analyze a firmware image](tutorial-analyze-firmware.md)
-- [Understand Role-Based Access Control for Firmware Images](defender-iot-firmware-analysis-rbac.md)
-- [Frequently asked questions about Defender for IoT Firmware Analysis](defender-iot-firmware-analysis-FAQ.md)
+For more information on firmware analysis for device builders, see the [firmware analysis documentation](/azure/firmware-analysis/overview-firmware-analysis).  

articles/defender-for-iot/device-builders/release-notes.md

@@ -15,6 +15,12 @@ Noted features are in PREVIEW. The [Azure Preview Supplemental Terms](https://az
 
 For more information, see [Upgrade the Microsoft Defender for IoT micro agent](upgrade-micro-agent.md).
 
+## November 2025
+
+You can now access the **Firmware analysis** page both from Defender for IoT, and directly via the Azure portal.
+
+The firmware analysis documentation is now located and maintained as part of the Azure portal documentation. See the full [firmware analysis documentation set](/azure/firmware-analysis/overview-firmware-analysis).
+
 ## August 2024
 
 Defender for IoT plans to retire the micro agent on August 1, 2025.