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/active-directory/cloud-infrastructure-entitlement-management/onboard-azure.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ This article describes how to onboard a Microsoft Azure subscription or subscrip
20
20
21
21
## Explanation
22
22
23
-
Given Permissions Management is hosted on Azure and you are onboarding your Azure subscriptions to be monitored and managed, setup is simple with few moving parts to configure. Below is what is required to configure onboarding:
23
+
Given that Permissions Management is hosted on Azure and you are onboarding your Azure subscriptions to be monitored and managed, setup is simple with few moving parts to configure. Below is what is required to configure onboarding:
24
24
25
25
1. When your tenant is onboarded, an application is created in the tenant.
26
26
1. This app requires 'reader' permissions on the subscriptions
Copy file name to clipboardExpand all lines: articles/active-directory/cloud-infrastructure-entitlement-management/onboard-gcp.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,11 +20,11 @@ This article describes how to onboard a Google Cloud Platform (GCP) project on P
20
20
21
21
## Explanation
22
22
23
-
For GCP, permissions management is scoped to a *GCP project*. A GCP project is a logical collection of your resources in GCP, somewhat analogous to a subscription in Azure, albeit with further configurations you can perform e.g. application registrations.
23
+
For GCP, permissions management is scoped to a *GCP project*. A GCP project is a logical collection of your resources in GCP, somewhat analogous to a subscription in Azure, albeit with further configurations you can perform such as application registrations and OIDC configurations.
24
24
25
25
<!-- Diagram from Gargi-->
26
26
27
-
There are several moving parts across GCP and Azure which are required to be configured before onboarding.
27
+
There are several moving parts across GCP and Azure, which are required to be configured before onboarding.
28
28
29
29
1. An AAD OIDC App
30
30
1. An Workload Identity in GCP
@@ -60,13 +60,13 @@ Choose from 3 options to manage GCP projects.
60
60
61
61
#### Option 1: Automatically manage
62
62
63
-
This option allows projects to be automatically detected and monitored without additional configuration. Steps to detect list of projects and onboard for collection:
63
+
This option allows projects to be automatically detected and monitored without extra configuration. Steps to detect list of projects and onboard for collection:
64
64
65
65
Firstly, grant Viewer and Security Reviewer role to service account created in previous step at organization, folder or project scope.
66
66
67
-
Once done, the steps are listed in the screen to do this manually in the GPC console, or programatically with the gcloud CLI.
67
+
Once done, the steps are listed in the screen to do configure this manually in the GPC console, or programatically with the gcloud CLI.
68
68
69
-
Once this has been configured, click next, then 'Verify Now & Save'.
69
+
Once everything has been configured, click next, then 'Verify Now & Save'.
70
70
71
71
Any current or future projects found get onboarded automatically.
Copy file name to clipboardExpand all lines: articles/active-directory/cloud-infrastructure-entitlement-management/overview.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,7 @@ Permissions Management allows customers to address three key use cases: *discov
34
34
35
35
Permissions Management has been designed in such a way that we recommended your organization sequentially 'step-through' each of the below phases in order to gain insights into permissions across the organization. This is because you generally cannot action what is yet to be discovered, likewise you cannot continually evaluate what is yet to be remediated.
36
36
37
+
:::image type="content" source="media/overview/discover-remediate-monitor.png" alt-text="Use case for Permissions Management." lightbox="media/overview/discover-remediate-monitor.png":::
Copy file name to clipboardExpand all lines: articles/active-directory/cloud-infrastructure-entitlement-management/ui-dashboard.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,8 @@ ms.author: kenwith
16
16
17
17
Permissions Management provides a summary of key statistics and data about your authorization system regularly. This information is available for Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP).
18
18
19
+
:::image type="content" source="media/ui-dashboard/ui-dashboard.png" alt-text="An example of the Permissions Management dashboard, highlighting key statistics to investigate." lightbox="media/ui-dashboard/ui-dashboard.png":::
20
+
19
21
## View metrics related to avoidable risk
20
22
21
23
The data provided by Permissions Management includes metrics related to avoidable risk. These metrics allow the Permissions Management administrator to identify areas where they can reduce risks related to the principle of least permissions.
@@ -74,6 +76,8 @@ The Permissions Management **Dashboard** displays the following information:
74
76
75
77
## The PCI heat map
76
78
79
+
:::image type="content" source="media/ui-dashboard/pci-heat-map.png" alt-text="An example of the PCI heatmap showing hundreds of identities which require investigation." lightbox="media/ui-dashboard/pci-heat-map.png":::
80
+
77
81
The **Permission Creep Index** heat map shows the incurred risk of users with access to high-risk permissions, and provides information about:
78
82
79
83
- Users who were given access to high-risk permissions but aren't actively using them. *High-risk permissions* include the ability to modify or delete information in the authorization system.
0 commit comments