Skip to content

Commit 3575dcd

Browse files
author
Tristan Desktop
committed
First small changes through
1 parent 60843a4 commit 3575dcd

File tree

7 files changed

+11
-6
lines changed

7 files changed

+11
-6
lines changed
Loading
72.2 KB
Loading
90.6 KB
Loading

articles/active-directory/cloud-infrastructure-entitlement-management/onboard-azure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ This article describes how to onboard a Microsoft Azure subscription or subscrip
2020
2121
## Explanation
2222

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:
2424

2525
1. When your tenant is onboarded, an application is created in the tenant.
2626
1. This app requires 'reader' permissions on the subscriptions

articles/active-directory/cloud-infrastructure-entitlement-management/onboard-gcp.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,11 @@ This article describes how to onboard a Google Cloud Platform (GCP) project on P
2020
2121
## Explanation
2222

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.
2424

2525
<!-- Diagram from Gargi-->
2626

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.
2828

2929
1. An AAD OIDC App
3030
1. An Workload Identity in GCP
@@ -60,13 +60,13 @@ Choose from 3 options to manage GCP projects.
6060

6161
#### Option 1: Automatically manage
6262

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:
6464

6565
Firstly, grant Viewer and Security Reviewer role to service account created in previous step at organization, folder or project scope.
6666

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.
6868

69-
Once this has been configured, click next, then 'Verify Now & Save'.
69+
Once everything has been configured, click next, then 'Verify Now & Save'.
7070

7171
Any current or future projects found get onboarded automatically.
7272

articles/active-directory/cloud-infrastructure-entitlement-management/overview.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,7 @@ Permissions Management allows customers to address three key use cases: *discov
3434

3535
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.
3636

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":::
3738

3839
### Discover
3940

articles/active-directory/cloud-infrastructure-entitlement-management/ui-dashboard.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ ms.author: kenwith
1616

1717
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).
1818

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+
1921
## View metrics related to avoidable risk
2022

2123
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:
7476

7577
## The PCI heat map
7678

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+
7781
The **Permission Creep Index** heat map shows the incurred risk of users with access to high-risk permissions, and provides information about:
7882

7983
- 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

Comments
 (0)