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
+14-15Lines changed: 14 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,21 @@
1
1
---
2
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 might affect your resources.
3
+
description: This article details where to find information from Azure Service Health about how Azure security incidents impact your resources.
4
4
ms.topic: conceptual
5
5
ms.date: 3/3/2023
6
6
---
7
7
8
8
# Resource impact from Azure security incidents
9
9
10
-
In support of the experience of viewing affected resources, Service Health has enabled a new feature to:
10
+
In support of the experience of viewing impacted resources, Service Health has enabled a new feature to:
11
11
12
-
- Display resources that are confirmed to be impacted by a security incident.
13
-
- Resource Health status of both confirmed and potentially impacted resources showing the availability of the resource.
14
-
- Enabling role-based access control (RBAC) for viewing security incident impacted resource information.
12
+
- Display resources impacted by a security incident
13
+
- Enabling role-based access control (RBAC) for viewing security incident impacted resource information
15
14
16
15
This article details what is communicated to users and where they can view information about their impacted resources.
17
16
18
17
>[!Note]
19
-
>This feature will be rolled out in phases. Initially, only selected subscription-level customers will get the experience. The rollout will gradually expand to 100 percent of subscription customers. It will go live for tenant-level customers in the future.
18
+
>This feature will be rolled out in phases. Initially, only selected subscription-level customers will get the experience. The rollout will gradually expand to 100 percent of subscription and tenant customers.
20
19
21
20
## Role Based Access (RBAC) For Security Incident Resource Impact
22
21
@@ -34,35 +33,35 @@ This article details what is communicated to users and where they can view infor
34
33
35
34
## Viewing Impacted Resources for Security Incidents on the Service Health Portal
36
35
37
-
In the Azure portal, the Impacted Resources tab under Service Health > Security Advisories displays resources that are affected by a security incident. The following example of the Impacted Resources tab shows a security incident with impacted resources.
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 example of the Impacted Resources tab shows a security incident with impacted resources.
38
37
39
-
:::image type="content" source="./media/impacted-resource-sec/impact-security.PNG" alt-text="Screenshot of information about affected resources in Azure Service Health.":::
38
+
:::image type="content" source="./media/impacted-resource-sec/impact-security.PNG" alt-text="Screenshot of information about impacted resources in Azure Service Health.":::
40
39
41
-
Service Health provides the below information to users whose resources are impacted by a security incident:
40
+
Along with resource information, Service Health provides the below information to users whose resources are impacted by a security incident:
42
41
43
42
|Column |Description |
44
43
|---------|---------|
45
-
|**Subscription ID**|Unique ID for the subscription that contains the affected resource|
46
-
|**Subscription Name**|Subscription name for the subscription that contains the affected resource|
44
+
|**Subscription ID**|Unique ID for the subscription that contains the impacted resource|
45
+
|**Subscription Name**|Subscription name for the subscription that contains the impacted resource|
47
46
|**Resource Name**|This will be the resource name of the resource. It will be text only for security impacted resources|
48
47
|**Tenant Name**|Unique ID for the tenant that contains the impacted resource|
49
-
|**Tenant ID**|Unique ID for the tenant that contains the affected resource|
48
+
|**Tenant ID**|Unique ID for the tenant that contains the impacted resource|
50
49
|**App ID**| description
51
50
52
51
## Accessing Impacted Resources programmatically via an API
53
52
54
-
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, the following endpoints can be used by users authorized with the above-mentioned roles.
53
+
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