Build and operate the data processing systems behind analytics and ML on Google Cloud, including BigQuery, Dataflow, and Pub/Sub, and track your readiness for the Professional Data Engineer exam.
Advanced
Prepare and test your skills
Advanced
Prepare and test your skills
Google Cloud service
Google SecOps
Topic in 1 exam domain
Also called: Chronicle (Google SecOps), Chronicle SecOps, Chronicle SIEM, chronicleservicemanager.googleapis.com, Google Chronicle SIEM, Google SecOps application, Google SecOps instance, Google SecOps SDK, Modern Security Operations, Security Operations
Google's security operations platform supporting integration actions and playbooks.
Where this appears on the exam
1 objective in 1 of 5 domains
Related topics
FoundationsBuilding blocksThis topicWorks alongsideAppliedGoogle Cloud StorageServiceVPC Service ControlsServiceApplication Default CredentialsFeatureCloud LoggingServiceCloud StorageServiceCloud MonitoringServiceSensitive Data ProtectionServiceSecurity Command CenterServiceCompute EngineServiceStorage Transfer ServiceServiceCloud RunServiceBigQueryService
Google SecOpsService
BigQuery Data Transfer ServiceServiceBindplane agentServiceAmazon S3ServiceAzure Blob StorageServiceApigeeServiceUnified Data ModelConceptPoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Bindplane agent works with Google SecOps From the official documentation: “Configure Bindplane Agent to ingest Syslog and send to Google SecOps”
- Cloud Storage works with Google SecOps From the official documentation: “Configure a feed in Google SecOps to ingest from Google Cloud Storage”
- Amazon S3 works with Google SecOps From the official documentation: “Configure AWS S3 bucket and IAM for Google SecOps”
- Google Cloud Storage works with Google SecOps From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- Azure Blob Storage works with Google SecOps From the official documentation: “Google SecOps can use Azure Blob Storage to store Event Hub checkpoints, which track which events have been processed.”
- BigQuery works with Google SecOps From the official documentation: “Google SecOps exports the following categories of data to your BigQuery project:”
- Unified Data Model is part of Google SecOps From the official documentation: “The UDM is a Google Security Operations standard data structure that stores information about data received from sources.”
- Cloud Logging works with Google SecOps From the official documentation: “This document explains how to integrate Cloud Logging with Google Security Operations.”
- Cloud Monitoring works with Google SecOps From the official documentation: “Google SecOps uses Cloud Monitoring to send the ingestion notifications.”
- Google SecOps depends on Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- Google SecOps depends on Google Cloud Storage From the official documentation: “This document explains how to ingest Desynova Contido logs to Google Security Operations using Google Cloud Storage V2.”
- Google SecOps works with Security Command Center From the official documentation: “This document explains how to integrate Security Command Center with Google Security Operations.”
- Google SecOps works with Unified Data Model From the official documentation: “Google SecOps normalizes incoming SAP logs into the Unified Data Model (UDM) so that you can search for data and run detections.”
- Apigee works with Google SecOps From the official documentation: “This document explains how to integrate Apigee with [Google Security Operations](/chronicle/docs/secops/secops-overview) (Google SecOps).”
- Cloud Run works with Google SecOps From the official documentation: “This guide explains how to export Cloud Run logs to Google Security Operations using Cloud Storage.”
- Compute Engine works with Google SecOps From the official documentation: “This document explains how to integrate Compute Engine with Google Security Operations.”
- Google SecOps depends on Security Command Center From the official documentation: “Google SecOps requires [Security Command Center](/security-command-center/docs/security-command-center-overview) (Standard or Premium) for asset metadata ingestion.”
- Google SecOps is an alternative to Security Command Center From the official documentation: “Verify that you can correlate various events across your systems. Consider tools such as Google SecOps or Security Command Center.”
- Google SecOps works with Sensitive Data Protection From the official documentation: “You can export your Sensitive Data Protection data to Google SecOps.”
- Google SecOps works with Storage Transfer Service From the official documentation: “This feed source uses the Storage Transfer Service (STS) to transfer data from Azure storage to Google SecOps.”
- Google SecOps works with VPC Service Controls From the official documentation: “Configure Google Security Operations with VPC Service Controls so that Google SecOps can access resources and services outside its service perimeter.”
- VPC Service Controls secures Google SecOps From the official documentation: “The APIs for Google Security Operations can be protected by VPC Service Controls and Google SecOps can be used normally inside service perimeters.”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Sensitive Data Protection depends on Application Default Credentials From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Security Command Center depends on Application Default Credentials From the official documentation: “To authenticate to Security Command Center, set up Application Default Credentials.”
- BigQuery works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze BigQuery data.”
- BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
- BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- Application Default Credentials secures Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- BigQuery works with BigQuery Data Transfer Service From the official documentation: “The BigQuery Data Transfer Service uses load jobs to load Amazon S3 data into BigQuery.”
- Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Application Default Credentials works with Google Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Cloud Storage works with Storage Transfer Service From the official documentation: “Transfer data between Cloud Storage services such as AWS S3 and Cloud Storage.”
- Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Application Default Credentials works with Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- BigQuery is an alternative to Google Cloud Storage From the official documentation: “The training data can be either a CSV file in Cloud Storage or a table in BigQuery.”
- BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into BigQuery”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Cloud Storage works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze a file on GCS.”
- Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Application Default Credentials works with Security Command Center From the official documentation: “To authenticate to Security Command Center, set up Application Default Credentials.”
- Security Command Center works with Sensitive Data Protection From the official documentation: “Sending Sensitive Data Protection scan results to Security Command Center”
- VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
- Amazon S3 is an alternative to Cloud Storage From the official documentation: “Data must be stored in either a Cloud Storage or Amazon S3 bucket.”
- Amazon S3 works with Storage Transfer Service From the official documentation: “Storage Transfer Service provides multiple options for how to transfer your S3 data to Cloud Storage.”
- Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
- Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
- Cloud Logging works with Storage Transfer Service From the official documentation: “Enable Cloud Logging for agentless transfers, or transfers from S3-compatible sources, with `--log-actions` and `--log-action-states`.”
- Storage Transfer Service depends on Application Default Credentials From the official documentation: “To authenticate to Storage Transfer Service, set up Application Default Credentials.”
- BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
How learners score on this topic
Last updated