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/sentinel/connect-google-cloud-platform.md
+14-16Lines changed: 14 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,14 +5,14 @@ author: limwainstein
5
5
ms.topic: how-to
6
6
ms.date: 03/23/2023
7
7
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.
9
9
---
10
10
11
11
# Stream Google Cloud Platform audit logs with the GCP Pub/Sub Audit Logs connector
12
12
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).
14
14
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.
16
16
17
17
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).
18
18
@@ -45,7 +45,7 @@ You can set up the GCP environment in one of two ways:
45
45
46
46
### Create GCP resources via the Terraform API
47
47
48
-
1. Open [GCP CloudShell](https://cloud.google.com/shell/).
48
+
1. Open [GCP Cloud Shell](https://cloud.google.com/shell/).
49
49
1. Open the editor and type:
50
50
51
51
```
@@ -108,8 +108,6 @@ You can set up the GCP environment in one of two ways:
108
108
1. In the **Configuration** area, select **Add new**.
109
109
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**.
110
110
111
-
TBD - screenshot
112
-
113
111
## Verify that the GCP data is in the Microsoft Sentinel environment
114
112
115
113
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
123
121
124
122
### Set up the GCP environment manually via the GCP portal
125
123
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.
127
125
128
126
#### Create the role
129
127
@@ -133,7 +131,7 @@ This section shows you how to manually set up the GCP environment. Alternatively
133
131
1. Filter the permissions by the **Pub/Sub Subscriber** and **Pub/Sub Viewer** roles, and select **pubsub.subscriptions.consume** and **pubsub.subscriptions.get** permissions.
134
132
1. To confirm, select **ADD**.
135
133
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.":::
137
135
138
136
1. To create the role, select **Create**.
139
137
@@ -154,32 +152,32 @@ This section shows you how to manually set up the GCP environment. Alternatively
154
152
155
153
1. Make sure that **Enable pool** is selected.
156
154
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.":::
158
156
159
157
1. To add a provider to the pool:
160
158
- Select **OIDC**
161
159
- Type the **Issuer (URL)**: \https://sts.windows.net/33e01921-4d64-4f8c-a055-5bdaffd5e33d
162
160
- Next to **Audiences**, select **Allowed audiences**, and next to **Audience 1**, type: *api://2041288c-b303-4ca0-9076-9612db3beeb2*.
163
161
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.":::
165
163
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.":::
167
165
168
166
#### Configure the provider attributes
169
167
170
168
1. Under **OIDC 1**, select **assertion.sub**.
171
169
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.":::
173
171
174
172
1. Select **Continue** and **Save**.
175
173
1. In the **Workload Identity Pools** main page, select the created pool.
176
174
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.
177
175
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.":::
179
177
180
178
1. Confirm that the connected service account is displayed.
181
179
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.":::
183
181
184
182
#### Create a topic
185
183
@@ -193,7 +191,7 @@ This section shows you how to manually set up the GCP environment. Alternatively
193
191
1. Select **Create sink** and fill in the relevant details.
194
192
1. Under **Sink destination**, select **Cloud Pub/Sub topic** and select [the topic you created previously](#create-a-topic).
195
193
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.":::
197
195
198
196
1. If needed, filter the logs by selecting specific logs to include. Otherwise, all logs are sent.
199
197
1. Select **Create sink**.
@@ -203,7 +201,7 @@ This section shows you how to manually set up the GCP environment. Alternatively
203
201
> 1. Select the organization under **Project**.
204
202
> 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**.
205
203
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.":::
207
205
208
206
#### Verify that GCP can receive incoming messages
0 commit comments