You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Frequently asked questions about Firmware Analysis
12
-
This article addresses frequent questions about Defender for IoT Firmware Analysis.
11
+
# Frequently asked questions about Firmware analysis
12
+
This article addresses frequent questions about Firmware analysis.
13
13
14
-
[Defender for IoT Firmware Analysis](overview-firmware-analysis) is a tool that analyzes firmware images and provides an understanding of security vulnerabilities in the firmware images.
14
+
[Firmware analysis](overview-firmware-analysis) is a tool that analyzes firmware images and provides an understanding of security vulnerabilities in the firmware images.
15
15
16
-
## What types of firmware images does Defender for IoT Firmware Analysis support?
17
-
Defender for IoT Firmware Analysis supports unencrypted images that contain file systems with embedded Linux operating systems. Defender for IoT Firmware Analysis supports the following file system formats:
16
+
## What types of firmware images does Firmware analysis support?
17
+
Firmware analysis supports unencrypted images that contain file systems with embedded Linux operating systems. Firmware analysis supports the following file system formats:
18
18
19
19
* Android sparse image
20
20
* bzip2 compressed data
@@ -45,7 +45,7 @@ Defender for IoT Firmware Analysis supports unencrypted images that contain file
45
45
* ZStandard compressed data
46
46
* Zip archive
47
47
48
-
## Where are the Defender for IoT Firmware Analysis Azure CLI/PowerShell docs?
48
+
## Where are the Firmware analysis Azure CLI/PowerShell docs?
49
49
You can find the documentation for our Azure CLI commands [here](/cli/azure/firmwareanalysis/firmware) and the documentation for our Azure PowerShell commands [here](/powershell/module/az.firmwareanalysis/?#firmwareanalysis).
50
50
51
51
You can also find the Quickstart for our Azure CLI [here](quickstart-upload-firmware-using-azure-command-line-interface) and the Quickstart for our Azure PowerShell [here](quickstart-upload-firmware-using-powershell). To run a Python script using the SDK to upload and analyze firmware images, visit [Quickstart: Upload firmware using Python](quickstart-upload-firmware-using-python).
Copy file name to clipboardExpand all lines: articles/firmware-analysis/firmware-analysis-rbac.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,56 +7,56 @@ ms.topic: conceptual
7
7
ms.date: 01/10/2024
8
8
---
9
9
10
-
# Overview of Azure Role-Based Access Control for Firmware Analysis
11
-
As a user of Defender for IoT Firmware Analysis, you may want to manage access to your firmware image analysis results. Azure Role-Based Access Control (RBAC) is an authorization system that enables you to control who has access to your analysis results, what permissions they have, and at what level of the resource hierarchy. This article explains how to store firmware analysis results in Azure, manage access permissions, and use RBAC to share these results within your organization and with third parties. To learn more about Azure RBAC, visit [What is Azure role-based access control (Azure RBAC)?](/articles/role-based-access-control/overview.md).
10
+
# Overview of Azure Role-Based Access Control for Firmware analysis
11
+
As a user of Firmware analysis, you may want to manage access to your firmware image analysis results. Azure Role-Based Access Control (RBAC) is an authorization system that enables you to control who has access to your analysis results, what permissions they have, and at what level of the resource hierarchy. This article explains how to store firmware analysis results in Azure, manage access permissions, and use RBAC to share these results within your organization and with third parties. To learn more about Azure RBAC, visit [What is Azure role-based access control (Azure RBAC)?](/articles/role-based-access-control/overview.md).
12
12
13
13
## Roles
14
14
Roles are a collection of permissions packaged together. There are two types of roles:
15
15
16
16
***Job function roles** give users permission to perform specific job functions or tasks, such as **Key Vault Contributor** or **Azure Kubernetes Service Cluster Monitoring User**.
17
17
***Privileged administrator roles** give elevated access privileges, such as **Owner**, **Contributor**, or **User Access Administrator**. To learn more about roles, visit [Azure built-in roles](/articles/role-based-access-control/built-in-roles.md).
18
18
19
-
In Defender for IoT Firmware Analysis, the most common roles are Owner, Contributor, Security Admin, and Firmware Analysis Admin. Learn more about [which roles you need for different permissions](defender-iot-firmware-analysis-rbac.md#defender-for-iot-firmware-analysis-roles-scopes-and-capabilities), such as uploading firmware images or sharing firmware analysis results.
19
+
In Firmware analysis, the most common roles are Owner, Contributor, Security Admin, and Firmware Analysis Admin. Learn more about [which roles you need for different permissions](firmware-analysis-rbac.md#firmware-analysis-roles-scopes-and-capabilities), such as uploading firmware images or sharing firmware analysis results.
20
20
21
21
## Understanding the Representation of Firmware Images in the Azure Resource Hierarchy
22
22
Azure organizes resources into resource hierarchies, which are in a top-down structure, and you can assign roles at each level of the hierarchy. The level at which you assign a role is the "scope," and lower scopes may inherit roles assigned at higher scopes. Learn more about the [levels of hierarchy and how to organize your resources in the hierarchy](/azure/cloud-adoption-framework/ready/azure-setup-guide/organize-resources).
23
23
24
-
When you onboard your subscription to Defender for IoT Firmware Analysis and select your resource group, the action automatically creates the **default** resource within your resource group.
24
+
When you onboard your subscription to Firmware analysis and select your resource group, the action automatically creates the **default** resource within your resource group.
25
25
26
26
Navigate to your resource group and select **Show hidden types** to show the **default** resource. The **default** resource has the **Microsoft.IoTFirmwareDefense.workspaces** type.
27
27
28
-
:::image type="content" source="media/defender-for-iot-firmware-analysis-rbac/default-workspace.png" alt-text="Screenshot of the toggle button 'Show hidden types' that reveals a resource named 'default'." lightbox="media/defender-for-iot-firmware-analysis-rbac/default-workspace.png":::
28
+
:::image type="content" source="media/firmware-analysis-rbac/default-workspace.png" alt-text="Screenshot of the toggle button 'Show hidden types' that reveals a resource named 'default'." lightbox="media/firmware-analysis-rbac/default-workspace.png":::
29
29
30
30
Although the **default** workspace resource isn't something that you'll regularly interact with, each firmware image that you upload will be represented as a resource and stored here.
31
31
32
32
You can use RBAC at each level of the hierarchy, including at the hidden **default Firmware Analysis Workspace** resource level.
33
33
34
-
Here's the resource hierarchy of Defender for IoT Firmware Analysis:
34
+
Here's the resource hierarchy of Firmware Analysis:
35
35
36
-
:::image type="content" source="media/defender-for-iot-firmware-analysis-rbac/resource-hierarchy.png" alt-text="Diagram that shows the resource hierarchy of firmware images of Defender for IoT Firmware Analysis." lightbox="media/defender-for-iot-firmware-analysis-rbac/resource-hierarchy.png":::
36
+
:::image type="content" source="media/firmware-analysis-rbac/resource-hierarchy.png" alt-text="Diagram that shows the resource hierarchy of firmware images of Firmware Analysis." lightbox="media/firmware-analysis-rbac/resource-hierarchy.png":::
37
37
38
38
## Apply Azure RBAC
39
39
40
40
> [!Note]
41
-
> To begin using Defender for IoT Firmware Analysis, the user that onboards the subscription onto Defender for IoT Firmware Analysis***must be*** an Owner, Contributor, Firmware Analysis Admin, or Security Admin at the subscription level. Follow the tutorial at [Analyze a firmware image with Microsoft Defender for IoT](tutorial-analyze-firmware.md#onboard-your-subscription-to-use-defender-for-firmware-analysis) to onboard your subscription. Once you've onboarded your subscription, a user only needs to be a Firmware Analysis Admin to use Defender for IoT Firmware Analysis.
41
+
> To begin using Firmware analysis, the user that onboards the subscription onto Firmware analysis***must be*** an Owner, Contributor, Firmware Analysis Admin, or Security Admin at the subscription level. Follow the tutorial at [Analyze a firmware image with Firmware analysis](tutorial-analyze-firmware.md#onboard-your-subscription-to-use-firmware-analysis) to onboard your subscription. Once you've onboarded your subscription, a user only needs to be a Firmware Analysis Admin to use Firmware Analysis.
42
42
>
43
43
44
-
As a user of Defender for IoT Firmware Analysis, you may need to perform certain actions for your organization, such as uploading firmware images or sharing analysis results.
44
+
As a user of Firmware analysis, you may need to perform certain actions for your organization, such as uploading firmware images or sharing analysis results.
45
45
46
-
Actions like these involve Role Based Access Control (RBAC). To effectively use RBAC for Defender for IoT Firmware Analysis, you must know what your role assignment is, and at what scope. Knowing this information will inform you about what permissions you have, and thus whether you can complete certain actions. To check your role assignment, refer to [Check access for a user to a single Azure resource - Azure RBAC](/azure-docs-pr/articles/role-based-access-control/check-access.md). Next, see the following table to check what roles and scopes are necessary for certain actions.
46
+
Actions like these involve Role Based Access Control (RBAC). To effectively use RBAC for Firmware analysis, you must know what your role assignment is, and at what scope. Knowing this information will inform you about what permissions you have, and thus whether you can complete certain actions. To check your role assignment, refer to [Check access for a user to a single Azure resource - Azure RBAC](/azure-docs-pr/articles/role-based-access-control/check-access.md). Next, see the following table to check what roles and scopes are necessary for certain actions.
47
47
48
-
### Common roles in Defender for IoT Firmware Analysis
48
+
### Common roles in Firmware analysis
49
49
50
50
This table categorizes each role and provides a brief description of their permissions:
51
51
52
52
**Role** | **Category** | **Description**
53
53
---|---|---
54
54
**Owner** | Privileged administrator role | Grants full access to manage all resources, including the ability to assign roles in Azure RBAC.
55
55
**Contributor** | Privileged administrator role | Grants full access to manage all resources, but doesn't allow you to assign roles in Azure RBAC, manage assignments in Azure Blueprints, or share image galleries.
56
-
**Security Admin** | Job function role | Allows the user to upload and analyze firmware images in Defender for IoT, add/assign security initiatives, and edit the security policy. [Learn more](/azure/defender-for-cloud/permissions).
57
-
**Firmware Analysis Admin** | Job function role | Allows the user to upload and analyze firmware images in Defender for IoT. The user has no access beyond firmware analysis (can't access other resources in the subscription, create or delete resources, or invite other users).
56
+
**Security Admin** | Job function role | Allows the user to upload and analyze firmware images, add/assign security initiatives, and edit the security policy. [Learn more](/azure/defender-for-cloud/permissions).
57
+
**Firmware Analysis Admin** | Job function role | Allows the user to upload and analyze firmware images. The user has no access beyond firmware analysis (can't access other resources in the subscription, create or delete resources, or invite other users).
58
58
59
-
## Defender for IoT Firmware Analysis Roles, Scopes, and Capabilities
59
+
## Firmware analysis roles, scopes, and capabilities
60
60
61
61
The following table summarizes what roles you need to perform certain actions. These roles and permissions apply at the Subscription and Resource Group levels, unless otherwise stated.
62
62
@@ -69,7 +69,7 @@ Invite users to the Subscription | Owner at the **Subscription** level (Owner at
69
69
## Uploading Firmware images
70
70
To upload firmware images:
71
71
72
-
* Confirm that you have sufficient permission in [Defender for IoT Firmware Analysis Roles, Scopes, and Capabilities](#defender-for-iot-firmware-analysis-roles-scopes-and-capabilities).
72
+
* Confirm that you have sufficient permission in [Firmware Analysis Roles, Scopes, and Capabilities](#firmware-analysis-roles-scopes-and-capabilities).
73
73
*[Upload a firmware image for analysis](tutorial-analyze-firmware.md#upload-a-firmware-image-for-analysis).
74
74
75
75
## Invite third parties to interact with your firmware analysis results
Copy file name to clipboardExpand all lines: articles/firmware-analysis/overview-firmware-analysis.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,28 @@
1
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.
2
+
title: Firmware analysis for device builders
3
+
description: Learn how firmware analysis helps device builders to market and deploy highly secure IoT/OT devices.
4
4
ms.topic: conceptual
5
5
ms.date: 06/15/2023
6
6
author: karengu0
7
7
ms.author: karenguo
8
8
#Customer intent: As a device builder, I want to understand how firmware analysis can help secure my IoT/OT devices and products.
9
9
---
10
10
11
-
# Firmware analysis for device builders
11
+
# Firmware analysis
12
12
13
13
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.
14
14
15
15
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.
16
16
17
-
Use Microsoft Defender for IoT's firmware analysis to identify embedded security threats, vulnerabilities, and common weaknesses that may be otherwise undetectable.
17
+
Use the Firmware analysis service to identify embedded security threats, vulnerabilities, and common weaknesses that may be otherwise undetectable.
18
18
19
19
> [!NOTE]
20
-
> 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.
20
+
> The **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.
21
21
>
22
22
23
23
## How to be sure your firmware is secure
24
24
25
-
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.
25
+
Firmware analysis 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.
26
26
27
27
-**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.
28
28
@@ -41,5 +41,5 @@ Defender for IoT can analyze your firmware for common weaknesses and vulnerabili
41
41
## Next steps
42
42
43
43
-[Analyze a firmware image](tutorial-analyze-firmware.md)
44
-
-[Understand Role-Based Access Control for Firmware Images](defender-iot-firmware-analysis-rbac.md)
45
-
-[Frequently asked questions about Defender for IoT Firmware Analysis](defender-iot-firmware-analysis-FAQ.md)
44
+
-[Understand Role-Based Access Control for Firmware Images](firmware-analysis-rbac.md)
45
+
-[Frequently asked questions about Firmware analysis](firmware-analysis-FAQ.md)
Copy file name to clipboardExpand all lines: articles/firmware-analysis/quickstart-upload-firmware-using-azure-command-line-interface.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,22 @@
1
1
---
2
-
title: "Quickstart: Upload firmware images to Defender for IoT Firmware Analysis using Azure CLI"
3
-
description: "Learn how to upload firmware images for analysis using the Azure CLI."
2
+
title: "Quickstart: Upload firmware images to Firmware analysis using Azure CLI"
3
+
description: "Learn how to upload firmware images for analysis using the Azure command line interface."
4
4
author: karengu0
5
5
ms.author: karenguo
6
6
ms.topic: quickstart
7
7
ms.custom: devx-track-azurecli
8
8
ms.date: 01/29/2024
9
9
---
10
10
11
-
# Quickstart: Upload firmware images to Defender for IoT Firmware Analysis using Azure CLI
11
+
# Quickstart: Upload firmware images to Firmware Analysis using Azure CLI
12
12
13
-
This article explains how to use the Azure CLI to upload firmware images to Defender for IoT Firmware Analysis.
13
+
This article explains how to use the Azure CLI to upload firmware images to Firmware analysis.
14
14
15
-
[Defender for IoT Firmware Analysis](overview-firmware-analysis) is a tool that analyzes firmware images and provides an understanding of security vulnerabilities in the firmware images.
15
+
[Firmware analysis](overview-firmware-analysis) is a tool that analyzes firmware images and provides an understanding of security vulnerabilities in the firmware images.
16
16
17
17
## Prerequisites
18
18
19
-
This quickstart assumes a basic understanding of Defender for IoT Firmware Analysis. For more information, see [Firmware analysis for device builders](overview-firmware-analysis). For a list of the file systems that are supported, see [Frequently asked Questions about Defender for IoT Firmware Analysis](defender-iot-firmware-analysis-faq.md#what-types-of-firmware-images-does-defender-for-iot-firmware-analysis-support).
19
+
This quickstart assumes a basic understanding of Firmware analysis. For more information, see [Firmware analysis for device builders](overview-firmware-analysis). For a list of the file systems that are supported, see [Frequently asked Questions about Firmware analysis](firmware-analysis-faq.md#what-types-of-firmware-images-does-firmware-analysis-support).
20
20
21
21
### Prepare your environment for the Azure CLI
22
22
@@ -25,14 +25,14 @@ This quickstart assumes a basic understanding of Defender for IoT Firmware Analy
25
25
* Sign in to the Azure CLI by using the [az login](/cli/azure/reference-index?#az-login) command. Follow the steps displayed in your terminal to finish the authentication process. For other sign-in options, see [Sign in with the Azure CLI](/cli/azure/authenticate-azure-cli).
26
26
27
27
* When you're prompted, install the Azure CLI extension on first use. For more information about extensions, see [Use extensions with the Azure CLI](/cli/azure/azure-cli-extensions-overview).
28
-
* Install the Defender for IoT Firmware Analysis extension by running the following command:
28
+
* Install the Firmware analysis extension by running the following command:
29
29
```azurecli
30
30
az extension add --name firmwareanalysis
31
31
```
32
32
33
33
* To find the version and dependent libraries that are installed, run the command [az version](/cli/azure/reference-index?#az-version). To upgrade to the latest version, run the command [az upgrade](/cli/azure/reference-index?#az-upgrade).
34
34
35
-
*[Onboard](tutorial-analyze-firmware.md#onboard-your-subscription-to-use-defender-for-firmware-analysis) your subscription to Defender for IoT Firmware Analysis.
35
+
*[Onboard](tutorial-analyze-firmware.md#onboard-your-subscription-to-use-firmware-analysis) your subscription to Firmware analysis.
36
36
37
37
* Select the appropriate subscription ID where you'd like to upload your firmware images by running the command [az account set](/cli/azure/account?#az-account-set).
0 commit comments