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
Copy file name to clipboardExpand all lines: articles/service-health/impacted-resources-security.md
+16-12Lines changed: 16 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,9 @@ This article details what is communicated to users and where they can view infor
19
19
20
20
## Role Based Access (RBAC) For Security Incident Resource Impact
21
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. Users authorized with the following roles can view security impacted resource information:
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:
23
25
24
26
**Subscription level**
25
27
- Subscription Owner
@@ -33,16 +35,7 @@ This article details what is communicated to users and where they can view infor
33
35
34
36
## Viewing Impacted Resources for Security Incidents on the Service Health Portal
35
37
36
-
In the Azure portal, the **Impacted Resources** tab under **Service Health** > **Security Advisories** displays resources that are impacted by a security incident. The following examples of the Impacted Resources tab shows a security incident with impacted resources.
37
-
38
-
**Subscription**
39
-
:::image type="content" source="./media/impacted-resource-sec/impact-security.PNG" alt-text="Screenshot of information about impacted resources in Azure Service Health.":::
40
-
41
-
**Tenant**
42
-
43
-
:::image type="content" source="./media/impacted-resource-sec/security-tenant.PNG" alt-text="Screenshot of information about impacted resources in Azure Service Health.":::
44
-
45
-
Along with resource information, Service Health provides the below information to users whose resources are impacted by a security incident:
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:
46
39
47
40
|Column |Description |
48
41
|---------|---------|
@@ -51,6 +44,17 @@ Along with resource information, Service Health provides the below information t
51
44
|**Tenant Name**|Unique ID for the tenant that contains the impacted resource|
52
45
|**Tenant ID**|Unique ID for the tenant that contains the impacted resource|
53
46
47
+
The following examples shows 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
+
54
58
## Accessing Impacted Resources programmatically via an API
55
59
56
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.
0 commit comments