Skip to content

Commit 9f3261b

Browse files
committed
Adding screenshots
1 parent cec871d commit 9f3261b

11 files changed

+14
-16
lines changed

articles/sentinel/connect-google-cloud-platform.md

Lines changed: 14 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,14 @@ author: limwainstein
55
ms.topic: how-to
66
ms.date: 03/23/2023
77
ms.author: lwainstein
8-
#Customer intent: As a security operator, I want to ingest GCP audit log data into Microsoft Sentinel to get full security coverage and analyze and detect attacks in my multi-cloud environment.
8+
#Customer intent: As a security operator, I want to ingest GCP audit log data into Microsoft Sentinel to get full security coverage and analyze and detect attacks in my multicloud environment.
99
---
1010

1111
# Stream Google Cloud Platform audit logs with the GCP Pub/Sub Audit Logs connector
1212

13-
Organizations are increasingly moving to multi-cloud architectures, whether by design or due to ongoing requirements. A growing number of these organizations use applications and store data on multiple public clouds, including the Google Cloud Platform (GCP).
13+
Organizations are increasingly moving to multicloud architectures, whether by design or due to ongoing requirements. A growing number of these organizations use applications and store data on multiple public clouds, including the Google Cloud Platform (GCP).
1414

15-
This article describes how to ingest GCP data into Microsoft Sentinel to get full security coverage and analyze and detect attacks in your multi-cloud environment.
15+
This article describes how to ingest GCP data into Microsoft Sentinel to get full security coverage and analyze and detect attacks in your multicloud environment.
1616

1717
With the **GCP Pub/Sub Audit Logs** connector, based on our [Codeless Connector Platform](create-codeless-connector.md?tabs=deploy-via-arm-template%2Cconnect-via-the-azure-portal) (CCP), you can ingest logs from your GCP environment using the GCP [Pub/Sub capability](https://cloud.google.com/pubsub/docs/overview).
1818

@@ -45,7 +45,7 @@ You can set up the GCP environment in one of two ways:
4545

4646
### Create GCP resources via the Terraform API
4747

48-
1. Open [GCP CloudShell](https://cloud.google.com/shell/).
48+
1. Open [GCP Cloud Shell](https://cloud.google.com/shell/).
4949
1. Open the editor and type:
5050

5151
```
@@ -108,8 +108,6 @@ You can set up the GCP environment in one of two ways:
108108
1. In the **Configuration** area, select **Add new**.
109109
1. Type the resource parameters you created when you [created the GCP resources](#create-gcp-resources-via-the-terraform-api). Make sure that the Data Collection Endpoint Name and the Data Collection Rule Name begin with **Microsoft-Sentinel-** and select **Connect**.
110110
111-
TBD - screenshot
112-
113111
## Verify that the GCP data is in the Microsoft Sentinel environment
114112
115113
1. To ensure that the GCP logs were successfully ingested into Microsoft Sentinel, run the following query 30 minutes after you finish to [set up the connector](#set-up-the-gcp-pubsub-audit-logs-connector-in-microsoft-sentinel).
@@ -123,7 +121,7 @@ TBD - screenshot
123121
124122
### Set up the GCP environment manually via the GCP portal
125123
126-
This section shows you how to manually set up the GCP environment. Alternatively, you can set up the environment [via the Terraform API](#create-gcp-resources-via-the-terraform-api). If you already set up the environment via the API, skip this section.
124+
This section shows you how to set up the GCP environment manually. Alternatively, you can set up the environment [via the Terraform API](#create-gcp-resources-via-the-terraform-api). If you already set up the environment via the API, skip this section.
127125
128126
#### Create the role
129127
@@ -133,7 +131,7 @@ This section shows you how to manually set up the GCP environment. Alternatively
133131
1. Filter the permissions by the **Pub/Sub Subscriber** and **Pub/Sub Viewer** roles, and select **pubsub.subscriptions.consume** and **pubsub.subscriptions.get** permissions.
134132
1. To confirm, select **ADD**.
135133
136-
:::image type="content" source="media/connect-google-cloud-platform/gcp-create-role.png" alt-text="Screenshot of adding permissions when adding a GCP role." lightbox="media/connect-google-cloud-platform/gcp-create-role.png":::
134+
:::image type="content" source="media/connect-google-cloud-platform/gcp-create-role.png" alt-text="Screenshot of adding permissions when adding a GCP role.":::
137135
138136
1. To create the role, select **Create**.
139137
@@ -154,32 +152,32 @@ This section shows you how to manually set up the GCP environment. Alternatively
154152
155153
1. Make sure that **Enable pool** is selected.
156154
157-
TBD - screenshot
155+
:::image type="content" source="media/connect-google-cloud-platform/gcp-create-identity-pool.png" alt-text="Screenshot of creating the identity pool as part of creating the GCP workload identity federation.":::
158156
159157
1. To add a provider to the pool:
160158
- Select **OIDC**
161159
- Type the **Issuer (URL)**: \https://sts.windows.net/33e01921-4d64-4f8c-a055-5bdaffd5e33d
162160
- Next to **Audiences**, select **Allowed audiences**, and next to **Audience 1**, type: *api://2041288c-b303-4ca0-9076-9612db3beeb2*.
163161
164-
TBD - screenshot
162+
:::image type="content" source="media/connect-google-cloud-platform/gcp-add-provider-pool.png" alt-text="Screenshot of adding the provider to the pool when creating the GCP workload identity federation.":::
165163
166-
TBD - screenshot
164+
:::image type="content" source="media/connect-google-cloud-platform/gcp-add-provider-pool-audiences.png" alt-text="Screenshot of adding the provider pool audiences when creating the GCP workload identity federation.":::
167165
168166
#### Configure the provider attributes
169167
170168
1. Under **OIDC 1**, select **assertion.sub**.
171169
172-
TBD - screenshot
170+
:::image type="content" source="media/connect-google-cloud-platform/gcp-configure-provider-attributes.png" alt-text="Screenshot of configuring the GCP provider attributes.":::
173171
174172
1. Select **Continue** and **Save**.
175173
1. In the **Workload Identity Pools** main page, select the created pool.
176174
1. Select **Grant access**, select the [service account you created previously](#create-the-service-account), and select **All identities in the pool** as the principals.
177175
178-
TBD - screenshot
176+
:::image type="content" source="media/connect-google-cloud-platform/gcp-grant-access.png" alt-text="Screenshot of granting access to the GCP service account.":::
179177
180178
1. Confirm that the connected service account is displayed.
181179
182-
TBD - screenshot
180+
:::image type="content" source="media/connect-google-cloud-platform/gcp-connected-service-account.png" alt-text="Screenshot of viewing the connected GCP service accounts.":::
183181
184182
#### Create a topic
185183
@@ -193,7 +191,7 @@ This section shows you how to manually set up the GCP environment. Alternatively
193191
1. Select **Create sink** and fill in the relevant details.
194192
1. Under **Sink destination**, select **Cloud Pub/Sub topic** and select [the topic you created previously](#create-a-topic).
195193
196-
TBD - screenshot
194+
:::image type="content" source="media/connect-google-cloud-platform/gcp-sink-destination.png" alt-text="Screenshot of defining the GCP sink destination.":::
197195
198196
1. If needed, filter the logs by selecting specific logs to include. Otherwise, all logs are sent.
199197
1. Select **Create sink**.
@@ -203,7 +201,7 @@ This section shows you how to manually set up the GCP environment. Alternatively
203201
> 1. Select the organization under **Project**.
204202
> 1. Repeat steps 2-4, and under **Choose logs to include in the sink** in the **Log Router** section, select **Include logs ingested by this organization and all child resources**.
205203
206-
TBD - screenshot
204+
:::image type="content" source="media/connect-google-cloud-platform/gcp-choose-logs.png" alt-text="Screenshot of choosing which GCP logs to include in the sink.":::
207205
208206
#### Verify that GCP can receive incoming messages
209207
54.8 KB
Loading
62.3 KB
Loading
76.7 KB
Loading
65.6 KB
Loading
44.5 KB
Loading
61.4 KB
Loading
92.2 KB
Loading
Binary file not shown.
60.7 KB
Loading

0 commit comments

Comments
 (0)