- Cloud Collectors Overview
- Administration
- Administrative Access
- Shareable Service Accounts
- Add Accounts for AWS Cloud Collectors
- Add Accounts for Cisco Duo Cloud Collector
- Add Accounts for Google Cloud Collectors
- Add Accounts for Microsoft Cloud Collectors
- Add Accounts for Okta Cloud Collectors
- Add Accounts for Salesforce Cloud Collectors
- Add Accounts for Splunk Cloud Collectors
- Add Accounts for Trend Micro Cloud Collectors
- Add Accounts for Wiz
- Define a Unique Site Name
- Sign Up for the Early Access Program
- Onboard Cloud Collectors
- Abnormal Security Cloud Collector
- Anomali Cloud Collector
- AWS CloudTrail Cloud Collectors
- AWS CloudWatch Cloud Collector
- AWS CloudWatch Alarms Cloud Collector
- AWS GuardDuty Cloud Collector
- AWS S3 Cloud Collector
- AWS Security Lake Cloud Collector
- AWS SQS Cloud Collector
- Azure Activity Logs Cloud Collector
- Azure Log Analytics Cloud Collector
- Azure Event Hub Cloud Collector
- Azure Storage Analytics Cloud Collector
- Box Cloud Collector
- Cato Networks Cloud Collector
- Cisco Duo Cloud Collector
- Cisco Meraki Cloud Collector
- Cisco Secure Endpoint Cloud Collector
- Cisco Umbrella Cloud Collector
- Cloudflare Cloud Collector
- Cribl Cloud Collector
- CrowdStrike Cloud Collectors
- DataBahn Cloud Collector
- Dropbox Cloud Collector
- GCP Cloud Logging Cloud Collector
- GCP Pub/Sub Cloud Collector
- GCP Security Command Center
- GitHub Cloud Collector
- Google Workspace Cloud Collector
- LastPass Cloud Collector
- Microsoft Defender XDR (via Azure Event Hub) Cloud Collector
- Microsoft Entra ID Context Cloud Collector
- Microsoft Entra ID Logs Cloud Collector
- Microsoft 365 Exchange Admin Reports Cloud Collector
- Supported Sources from Microsoft 365 Exchange Admin Reports
- Migrate to the Microsoft 365 Exchange Admin Reports Cloud Collector
- Prerequisites to Configure the Microsoft 365 Exchange Admin Reports Cloud Collector
- Configure the Microsoft 365 Exchange Admin Reports Cloud Collector
- Troubleshooting the Microsoft 365 Exchange Admin Reports Cloud Collector
- Microsoft 365 Management Activity Cloud Collector
- Microsoft Security Alerts Cloud Collector
- Microsoft Sentinel (via Event Hub) Cloud Collector
- Mimecast Cloud Collector
- Netskope Alerts Cloud Collector
- Netskope Events Cloud Collector
- Okta Cloud Collector
- Okta Context Cloud Collector
- Palo Alto Networks Cortex Data Lake Cloud Collector
- Progress ShareFile Cloud Collector
- Proofpoint On-Demand Cloud Collector
- Proofpoint Targeted Attack Protection Cloud Collector
- Qualys Cloud Collector
- Recorded Future Cloud Collector
- Recorded Future Context Cloud Collector
- Rest API Cloud Collector
- Salesforce Cloud Collector
- Slack Cloud Collector
- SentinelOne Alerts Cloud Collector
- SentinelOne Cloud Funnel Cloud Collector
- SentinelOne Threats Cloud Collector
- SentinelOne Cloud Collector
- ServiceNow Cloud Collector
- Sophos Central Cloud Collector
- Splunk Cloud Collector
- STIX/TAXII Cloud Collector
- Symantec Endpoint Security Cloud Collector
- Tenable Cloud Collector
- Trend Vision One Cloud Collector
- Trellix Endpoint Security Cloud Collector
- Vectra Cloud Collector
- Zoom Cloud Collector
- Zscaler ZIA Cloud Collector
- Webhook Cloud Collectors
- Wiz Issues Cloud Collector
- Wiz API Cloud Collector
- Troubleshooting Cloud Collectors
Prerequisites to Configure GCP Cloud Logging Cloud Collector
Before you configure the Google Cloud Platform (GCP) Cloud Logging cloud collector you must complete the following prerequisites.
Ensure that the https://*.cloud.google.com service is open for communication with the New-Scale Security Operations Platform.
Obtain the service credentials JSON file.
Ensure that you have the administrative rights to configure GCP.
Obtain a Subscription ID – Set up a subscription for the Pub/Sub topic to which the log data is exported. Note the Subscription ID that you set while creating a subscription in GCP Pub/Sub and subscription. Subscription ID is associated with your Pub/Sub topic. For more information, see Set up Pub/Sub topic and subscriptions in the Google documentation.
Obtain a Project ID – Note the Project ID that you set while creating the Google service account. See Create a Service Account and Obtain a Project ID.
Assign the required permissions to the service account – Assign the following permissions to the service account to support auto-scaling on your Google Cloud Platform:
dataflow.metrics.get
monitoring.metricDescriptors.get
monitoring.metricDescriptors.list
monitoring.monitoredResourceDescriptors.list
monitoring.timeSeries.list
Assign the required subscription permissions – Assign pubsub.subscriptions.consume permission to the service account.
Obtain the Service Credentials JSON File
The GCP APIs are authenticated via a service account. You must obtain the service credentials JSON with the API key that you can use while configuring the GCP connector.
To obtain the service credentials JSON file:
Enable the stack driver API via: https://console.cloud.google.com/apis/api/logging.googleapis.com/overview?project=<GCP project-to-monitor>
Note
The project where the service account is set up must grant permissions to other projects that contain Sinks with the data.
To create the service account key, in the Google cloud console, navigate to the APIs & Services > Credentials.
In the Credentials section, click Create Credentials then click Service account.
Specify the account name and description.
Select the roles Logs Viewer and Private Logs Viewer.
Click DONE.
On the Service Accounts list page, click the name of the account that you created.
Navigate to Keys > Add Key > Create New Key.
In the Key type section, select JSON.
Click Create. A JSON file is downloaded. For more information see the Google Cloud documentation.
Save the JSON file at a secure location to use while configuring the GCP connector. Copy the JSON file contents to se it while creating a sharable Google account.
Create a Service Account and Obtain a Project ID
To create a service account in the project in which the Pub/Sub subscription has been created, in the Google Cloud console, navigate to IAM & Admin > Service Accounts > CREATE SERVICE ACCOUNT page.
Select a Cloud project if you already created a project. If not, create a Cloud project.
Enter the project name and edit the automatically generated project ID. Note the Project ID that you set while creating the Google service account. You require to use the project ID while configuring the GCP Pub/Sub Cloud Collector.
For more information and relevant steps, see Creating and managing service accounts in the Google documentation.
Obtain a Subscription ID
To obtain a subscription ID, first create a sink and GCP Pub/Sub topic and a subscription. Open the Log Router page in your Google logging platform, then select the project containing the logs you want to route. Click Create sink, provide a name and an optional description, and choose the destination where the logs should be sent. Ensure that in the Sink destination section, you select Cloud Pub/Sub topic
as a sink service and create or select a pub/sub topic to which you want to send the data to.
While you select or create a particular pub/sub topic to receive the routed log entries, you can add a subscription. You must note this subscription ID that you need to provide while configuring the GCP Cloud Logging cloud collector.
Optionally, set an inclusion filter to specify which logs to route, and an exclusion filter to exclude certain logs. Finally, click Create sink to complete the setup.
For more information, see Create a sink in Google documentation.