Skip to content

Commit 24eeccc

Browse files
authored
Merge pull request #265625 from yelevin/yelevin/connect-gcp-scc
Doc for new GCP Security Command Center connector
2 parents 4f477b0 + 5f5fca9 commit 24eeccc

File tree

3 files changed

+97
-14
lines changed

3 files changed

+97
-14
lines changed

articles/sentinel/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -824,8 +824,6 @@
824824
href: connect-dns-ama.md
825825
- name: Custom log sources
826826
href: connect-custom-logs.md
827-
- name: GCP audit logs
828-
href: connect-google-cloud-platform.md
829827
- name: Logstash plugin with Data Collection Rules
830828
href: connect-logstash-data-connection-rules.md
831829
- name: Logstash plugin (legacy)
@@ -838,6 +836,8 @@
838836
href: connect-aws.md
839837
- name: CloudWatch events via Lambda function
840838
href: cloudwatch-lambda-function.md
839+
- name: Google Cloud Platform connectors
840+
href: connect-google-cloud-platform.md
841841
- name: Azure Active Directory
842842
href: connect-azure-active-directory.md
843843
- name: Azure Stack VMs

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

Lines changed: 84 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: yelevin
55
ms.author: yelevin
66
ms.topic: how-to
77
ms.date: 01/17/2024
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.
8+
#Customer intent: As a security operator, I want to ingest Google Cloud Platform log data into Microsoft Sentinel to get full security coverage and analyze and detect attacks in my multicloud environment.
99
---
1010

1111
# Ingest Google Cloud Platform log data into Microsoft Sentinel
@@ -14,22 +14,26 @@ Organizations are increasingly moving to multicloud architectures, whether by de
1414

1515
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

17-
With the **GCP Pub/Sub** 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).
17+
With the **GCP Pub/Sub** connectors, 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

19-
> [!IMPORTANT]
20-
> The GCP Pub/Sub Audit Logs connector is currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
19+
- The **Google Cloud Platform (GCP) Pub/Sub Audit Logs connector** collects audit trails of access to GCP resources. Analysts can monitor these logs to track resource access attempts and detect potential threats across the GCP environment.
20+
21+
- The **Google Cloud Platform (GCP) Security Command Center connector** collects findings from Google Security Command Center, a robust security and risk management platform for Google Cloud. Analysts can view these findings to gain insights into the organization's security posture, including asset inventory and discovery, detections of vulnerabilities and threats, and risk mitigation and remediation.
2122

22-
Google's Cloud Audit Logs records an audit trail that analysts can use to monitor access and detect potential threats across GCP resources.
23+
> [!IMPORTANT]
24+
> The GCP Pub/Sub connectors are currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
2325
2426
## Prerequisites
2527

2628
Before you begin, verify that you have the following:
2729

2830
- The Microsoft Sentinel solution is enabled.
2931
- A defined Microsoft Sentinel workspace exists.
30-
- A GCP environment (a **project**) exists and is collecting GCP audit logs.
32+
- A GCP environment exists and contains resources producing one of the following log type you want to ingest:
33+
- GCP audit logs
34+
- Google Security Command Center findings
3135
- Your Azure user has the Microsoft Sentinel Contributor role.
32-
- Your GCP user has access to edit and create resources in the GCP project.
36+
- Your GCP user has access to create and edit resources in the GCP project.
3337
- The GCP Identity and Access Management (IAM) API and the GCP Cloud Resource Manager API are both enabled.
3438

3539
## Set up GCP environment
@@ -49,8 +53,15 @@ There are two things you need to set up in your GCP environment:
4953
You can set up the environment in one of two ways:
5054

5155
- [Create GCP resources via the Terraform API](?tabs=terraform): Terraform provides APIs for resource creation and for Identity and Access Management (see [Prerequisites](#prerequisites)). Microsoft Sentinel provides Terraform scripts that issue the necessary commands to the APIs.
56+
5257
- [Set up GCP environment manually](?tabs=manual), creating the resources yourself in the GCP console.
5358

59+
> [!NOTE]
60+
> There is no Terraform script available for creating GCP Pub/Sub resources for log collection from **Security Command Center**. You must create these resources manually. You can still use the Terraform script to create the GCP IAM resources for authentication.
61+
62+
> [!IMPORTANT]
63+
> If you're creating resources manually, you must create *all* the authentication (IAM) resources in the **same GCP project**, otherwise it won't work. (Pub/Sub resources can be in a different project.)
64+
5465
### GCP Authentication Setup
5566

5667
# [Terraform API Setup](#tab/terraform)
@@ -170,6 +181,10 @@ For more information about granting access in Google Cloud Platform, see [Manage
170181

171182
### GCP Audit Logs Setup
172183

184+
The instructions in this section are for using the Microsoft Sentinel **GCP Pub/Sub Audit Logs** connector.
185+
186+
See [the instructions in the next section](#gcp-security-command-center-setup) for using the Microsoft Sentinel **GCP Pub/Sub Security Command Center** connector.
187+
173188
# [Terraform API Setup](#tab/terraform)
174189

175190
1. Copy the Terraform audit log setup script provided by Microsoft Sentinel from the Sentinel GitHub repository into a different folder in your GCP Cloud Shell environment.
@@ -252,15 +267,35 @@ Use the [Google Cloud Platform Log Router service](https://cloud.google.com/logg
252267

253268
---
254269

270+
If you're also setting up the **GCP Pub/Sub Security Command Center** connector, continue with the next section.
271+
272+
Otherwise, skip to [Set up the GCP Pub/Sub connector in Microsoft Sentinel](#set-up-the-gcp-pubsub-connector-in-microsoft-sentinel).
273+
274+
### GCP Security Command Center setup
275+
276+
The instructions in this section are for using the Microsoft Sentinel **GCP Pub/Sub Security Command Center** connector.
277+
278+
See [the instructions in the previous section](#gcp-audit-logs-setup) for using the Microsoft Sentinel **GCP Pub/Sub Audit Logs** connector.
279+
280+
#### Configure continuous export of findings
281+
282+
Follow the instructions in the Google Cloud documentation to [**configure Pub/Sub exports**](https://cloud.google.com/security-command-center/docs/how-to-export-data#configure-pubsub-exports) of future SCC findings to the GCP Pub/Sub service.
283+
284+
1. When asked to select a project for your export, select a project you created for this purpose, or [create a new project](https://cloud.google.com/resource-manager/docs/creating-managing-projects#creating_a_project).
285+
286+
1. When asked to select a Pub/Sub topic where you want to export your findings, follow the instructions above to [create a new topic](#create-a-publishing-topic).
287+
255288
## Set up the GCP Pub/Sub connector in Microsoft Sentinel
256289
290+
# [GCP Audit Logs](#tab/auditlogs)
291+
257292
1. Open the [Azure portal](https://portal.azure.com/) and navigate to the **Microsoft Sentinel** service.
258293
259294
1. In the **Content hub**, in the search bar, type *Google Cloud Platform Audit Logs*.
260295
261-
1. Install the **Google Cloud Platform Audit Logs** solution.
296+
1. Install the **Google Cloud Platform Audit Logs** solution.
262297
263-
1. Select **Data connectors**, and in the search bar, type *GCP Pub/Sub Audit Logs*.
298+
1. Select **Data connectors**, and in the search bar, type *GCP Pub/Sub Audit Logs*.
264299
265300
1. Select the **GCP Pub/Sub Audit Logs (Preview)** connector.
266301
@@ -274,17 +309,54 @@ Use the [Google Cloud Platform Log Router service](https://cloud.google.com/logg
274309
275310
:::image type="content" source="media/connect-google-cloud-platform/new-collector-dialog.png" alt-text="Screenshot of new collector side panel.":::
276311
277-
1. Make sure that the values in all the fields match their counterparts in your GCP project, and select **Connect**.
312+
1. Make sure that the values in all the fields match their counterparts in your GCP project (the values in the screenshot are samples, not literals), and select **Connect**.
313+
314+
# [Google Security Command Center](#tab/scc)
315+
316+
1. Open the [Azure portal](https://portal.azure.com/) and navigate to the **Microsoft Sentinel** service.
317+
318+
1. In the **Content hub**, in the search bar, type *Google Security Command Center*.
319+
320+
1. Install the **Google Security Command Center** solution.
321+
322+
1. Select **Data connectors**, and in the search bar, type *Google Security Command Center*.
323+
324+
1. Select the **Google Security Command Center (Preview)** connector.
325+
326+
1. In the details pane, select **Open connector page**.
327+
328+
1. In the **Configuration** area, select **Add new collector**.
329+
330+
:::image type="content" source="media/connect-google-cloud-platform/add-new-collector.png" alt-text="Screenshot of GCP connector configuration." lightbox="media/connect-google-cloud-platform/add-new-collector.png":::
331+
332+
1. In the **Connect a new collector** panel, type the resource parameters you created when you [created the GCP resources](#set-up-gcp-environment).
333+
334+
:::image type="content" source="media/connect-google-cloud-platform/new-collector-dialog.png" alt-text="Screenshot of new collector side panel.":::
335+
336+
1. Make sure that the values in all the fields match their counterparts in your GCP project (the values in the screenshot are samples, not literals), and select **Connect**.
337+
338+
---
278339
279340
## Verify that the GCP data is in the Microsoft Sentinel environment
280341
281342
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-connector-in-microsoft-sentinel).
282343
283-
```
344+
# [GCP Audit Logs](#tab/auditlogs)
345+
346+
```kusto
284347
GCPAuditLogs
285-
| take 10
348+
| take 10
286349
```
287350
351+
# [Google Security Command Center](#tab/scc)
352+
353+
```kusto
354+
GoogleSCC
355+
| take 10
356+
```
357+
358+
---
359+
288360
1. Enable the [health feature](enable-monitoring.md) for data connectors.
289361
290362
## Next steps

articles/sentinel/whats-new.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,10 +23,21 @@ The listed features were released in the last three months. For information abou
2323

2424
## February 2024
2525

26+
- [New Google Pub/Sub-based connector for ingesting Security Command Center findings (Preview)](#new-google-pubsub-based-connector-for-ingesting-security-command-center-findings-preview)
2627
- [Incident tasks now generally available (GA)](#incident-tasks-now-generally-available-ga)
2728
- [AWS and GCP data connectors now support Azure Government clouds](#aws-and-gcp-data-connectors-now-support-azure-government-clouds)
2829
- [Windows DNS Events via AMA connector now generally available (GA)](#windows-dns-events-via-ama-connector-now-generally-available-ga)
2930

31+
### New Google Pub/Sub-based connector for ingesting Security Command Center findings (Preview)
32+
33+
You can now ingest logs from Google Security Command Center, using the new Google Cloud Platform (GCP) Pub/Sub-based connector (now in PREVIEW).
34+
35+
The Google Cloud Platform (GCP) Security Command Center is a robust security and risk management platform for Google Cloud. It provides features such as asset inventory and discovery, detection of vulnerabilities and threats, and risk mitigation and remediation. These capabilities help you gain insights into and control over your organization's security posture and data attack surface, and enhance your ability to efficiently handle tasks related to findings and assets.
36+
37+
The integration with Microsoft Sentinel allows you to have visibility and control over your entire multicloud environment from a "single pane of glass."
38+
39+
- Learn how to [set up the new connector](connect-google-cloud-platform.md) and ingest events from Google Security Command Center.
40+
3041
### Incident tasks now generally available (GA)
3142

3243
Incident tasks, which help you standardize your incident investigation and response practices so you can more effectively manage incident workflow, are now generally available (GA) in Microsoft Sentinel.

0 commit comments

Comments
 (0)