|
| 1 | +--- |
| 2 | +title: Resource impact from Azure security incidents |
| 3 | +description: This article details where to find information from Azure Service Health about how Azure security incidents impact your resources. |
| 4 | +ms.topic: conceptual |
| 5 | +ms.date: 3/3/2023 |
| 6 | +--- |
| 7 | + |
| 8 | +# Resource impact from Azure security incidents |
| 9 | + |
| 10 | +In support of the experience of viewing impacted resources, Service Health has enabled a new feature to: |
| 11 | + |
| 12 | +- Display resources impacted by a security incident |
| 13 | +- Enabling role-based access control (RBAC) for viewing security incident impacted resource information |
| 14 | + |
| 15 | +This article details what is communicated to users and where they can view information about their impacted resources. |
| 16 | + |
| 17 | +>[!Note] |
| 18 | +>This feature will be rolled out in phases. The rollout will gradually expand to 100 percent of subscription and tenant customers. |
| 19 | +
|
| 20 | +## Role Based Access (RBAC) For Security Incident Resource Impact |
| 21 | + |
| 22 | +[Azure role-based access control (Azure RBAC)](../role-based-access-control/overview.md) helps you manage who has access to Azure resources, what they can do with those resources, and what areas they have access to. Given the sensitive nature of security incidents, role-based access is leveraged to limit the audience of their impacted resource information. Along with resource information, Service Health provides the below information to users whose resources are impacted by a security incident: |
| 23 | + |
| 24 | +Users authorized with the following roles can view security impacted resource information: |
| 25 | + |
| 26 | +**Subscription level** |
| 27 | +- Subscription Owner |
| 28 | +- Subscription Admin |
| 29 | +- Service Health Security Reader (New custom role) |
| 30 | + |
| 31 | +**Tenant level** |
| 32 | +- Security Admin/Security Reader |
| 33 | +- Global Admin/Tenant Admin |
| 34 | +- Azure Service Health Privacy reader (New custom role) |
| 35 | + |
| 36 | +## Viewing Impacted Resources for Security Incidents on the Service Health Portal |
| 37 | + |
| 38 | +In the Azure portal, the **Impacted Resources** tab under **Service Health** > **Security Advisories** displays resources that are impacted by a security incident. Along with resource information, Service Health provides the below information to users whose resources are impacted by a security incident: |
| 39 | + |
| 40 | +|Column |Description | |
| 41 | +|---------|---------| |
| 42 | +|**Subscription ID**|Unique ID for the subscription that contains the impacted resource| |
| 43 | +|**Subscription Name**|Subscription name for the subscription that contains the impacted resource| |
| 44 | +|**Tenant Name**|Unique ID for the tenant that contains the impacted resource| |
| 45 | +|**Tenant ID**|Unique ID for the tenant that contains the impacted resource| |
| 46 | + |
| 47 | +The following examples show a security incident with impacted resources from the subscription and tenant scope. |
| 48 | + |
| 49 | +**Subscription** |
| 50 | + |
| 51 | +:::image type="content" source="./media/impacted-resource-sec/impact-security.PNG" alt-text="Screenshot of information about impacted resources from subscription scope in Azure Service Health."::: |
| 52 | + |
| 53 | +**Tenant** |
| 54 | + |
| 55 | +:::image type="content" source="./media/impacted-resource-sec/security-tenant.PNG" alt-text="Screenshot of information about impacted resources from tenant scope in Azure Service Health."::: |
| 56 | + |
| 57 | + |
| 58 | +## Accessing Impacted Resources programmatically via an API |
| 59 | + |
| 60 | +Impacted resource information for security incidents can be retrieved programmatically using the Events API. To access the list of resources impacted by a security incident, users authorized with the above-mentioned roles can use the following endpoints. |
| 61 | + |
| 62 | +**Subscription** |
| 63 | + |
| 64 | +```HTTP |
| 65 | +https://management.azure.com/subscriptions/(“Subscription ID”)/providers/microsoft.resourcehealth/events/("Tracking ID")/listSecurityAdvisoryImpactedResources?api-version=2022-10-01 |
| 66 | +``` |
| 67 | + |
| 68 | +**Tenant** |
| 69 | + |
| 70 | +```HTTP |
| 71 | +https://management.azure.com/providers/microsoft.resourcehealth/events/("Tracking ID")/listSecurityAdvisoryImpactedResources?api-version=2022-10-01 |
| 72 | +``` |
| 73 | + |
| 74 | +## Next steps |
| 75 | +- [Introduction to the Azure Service Health dashboard](service-health-overview.md) |
| 76 | +- [Introduction to Azure Resource Health](resource-health-overview.md) |
| 77 | +- [Frequently asked questions about Azure Resource Health](resource-health-faq.yml) |
0 commit comments