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/defender-for-cloud/concept-gcp-connector.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,17 +36,17 @@ The authentication process works as follows:
36
36
37
37
(4) - Defender for Cloud's CSPM service uses the Google STS token to impersonate the service account. Defender for Cloud's CSPM receives service account credentials which will then be used to scan the project.
38
38
39
-
## What happens when you onboard a project
39
+
## What happens when you onboard a single project
40
40
41
41
There are four parts to the onboarding process that take place when you create the security connection between your GCP project and Microsoft Defender for Cloud.
42
42
43
43
### Organization details
44
44
45
45
In the first section you will need to add the basic properties of the connection between your GCP project and Defender for Cloud.
46
46
47
-
:::image type="content" source="media/concept-gcp-connector/organization-details.png" alt-text="Screenshot of the organization details page of the GCP project onboarding process.":::
47
+
:::image type="content" source="media/concept-gcp-connector/single-project-details.png" alt-text="Screenshot of the organization details page of the GCP project onboarding process.":::
48
48
49
-
Here you will name your connector, connect it to a subscription and resource group which will be sed to create an ARM resource which is called security connector. The security connector represents a configuation resource that holds the projects settings.
49
+
Here you will name your connector, select a subscription and resource group which will be used to create an ARM resource which is called security connector. The security connector represents a configuration resource that holds the projects settings.
50
50
51
51
You will also select a location and add the organization ID for your project.
52
52
@@ -73,25 +73,23 @@ The GCloud script creates all of the required resources on your GCP environment
73
73
- Service accounts
74
74
- Project level policy bindings (service account will have access only to the specific project)
75
75
76
-
## Review and generate
76
+
###Review and generate
77
77
78
78
The final step for onboarding is to review all of your selections and to create the connector.
79
79
80
80
:::image type="content" source="media/concept-gcp-connector/review-and-generate.png" alt-text="Screenshot of the review and generate screen with all of your selections listed.":::
81
81
82
82
## What happens when you onboard an organization
83
83
84
-
Similar to single project onboarding, the organization onboarding option creates a security connector too. The security connector represents the configuration that connects Defender for Cloud and your GCP organization. In order to create onboarding resources on each project automatically, you should enter the details for GCP projects that will be used by Defender for Cloud to provision resources.
85
-
86
-
When onboarding a GCP organization, MDC creates a security connector for each project under the organization (unless specific projects were excluded, see step 1 for more details).
84
+
Similar to onboarding a single project, When onboarding a GCP organization, Defender for Cloud creates a security connector for each project under the organization (unless specific projects were excluded).
87
85
88
86
### Organization details
89
87
90
-
In the first section you will need to add the basic properties of the connection between your GCP project and Defender for Cloud.
88
+
In the first section you will need to add the basic properties of the connection between your GCP organization and Defender for Cloud.
91
89
92
90
:::image type="content" source="media/concept-gcp-connector/organization-details.png" alt-text="Screenshot of the organization details page of the GCP project onboarding process.":::
93
91
94
-
Here you will name your connector, connect it to a subscription and resource group which will be sed to create an ARM resource which is called security connector. The security connector represents a configuation resource that holds the projects settings.
92
+
Here you will name your connector, select a subscription and resource group which will be used to create an ARM resource which is called security connector. The security connector represents a configuration resource that holds the projects settings.
95
93
96
94
You will also select a location and add the organization ID for your project.
97
95
@@ -118,7 +116,7 @@ The GCloud script creates all of the required resources on your GCP environment
118
116
- Service accounts
119
117
- Project level policy bindings (service account will have access only to the specific project)
120
118
121
-
## Review and generate
119
+
###Review and generate
122
120
123
121
The final step for onboarding is to review all of your selections and to create the connector.
0 commit comments