Skip to content

Commit 26db030

Browse files
committed
fixes
1 parent 79bb693 commit 26db030

File tree

6 files changed

+8
-10
lines changed

6 files changed

+8
-10
lines changed

articles/defender-for-cloud/concept-gcp-connector.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -36,17 +36,17 @@ The authentication process works as follows:
3636

3737
(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.
3838

39-
## What happens when you onboard a project
39+
## What happens when you onboard a single project
4040

4141
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.
4242

4343
### Organization details
4444

4545
In the first section you will need to add the basic properties of the connection between your GCP project and Defender for Cloud.
4646

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.":::
4848

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

5151
You will also select a location and add the organization ID for your project.
5252

@@ -73,25 +73,23 @@ The GCloud script creates all of the required resources on your GCP environment
7373
- Service accounts
7474
- Project level policy bindings (service account will have access only to the specific project)
7575

76-
## Review and generate
76+
### Review and generate
7777

7878
The final step for onboarding is to review all of your selections and to create the connector.
7979

8080
:::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.":::
8181

8282
## What happens when you onboard an organization
8383

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).
8785

8886
### Organization details
8987

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

9290
:::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.":::
9391

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

9694
You will also select a location and add the organization ID for your project.
9795

@@ -118,7 +116,7 @@ The GCloud script creates all of the required resources on your GCP environment
118116
- Service accounts
119117
- Project level policy bindings (service account will have access only to the specific project)
120118

121-
## Review and generate
119+
### Review and generate
122120

123121
The final step for onboarding is to review all of your selections and to create the connector.
124122

22.9 KB
Loading
11 KB
Loading
26.9 KB
Loading
19.6 KB
Loading
47.8 KB
Loading

0 commit comments

Comments
 (0)