data residency

Related topics

• data residency is part of Apigee From the official documentation: “**Dashboard availability:** This dashboard is not available if your Apigee organization was provisioned with compliance-related Apigee features, such as [data residency](/apigee/docs/api-platform/get-started/drz-concepts)…”
• data residency is part of Security Command Center From the official documentation: “*Data residency* gives you more control over where your Security Command Center data is located. This document provides essential information about how Security Command Center supports data residency.”
• data residency works with VPC Service Controls From the official documentation: “To use VPC Service Controls with data residency at rest, you must use the following regional endpoint: `CONTROL_PLANE_LOCATION-apigee.googleapis.com`”
• BigQuery works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze BigQuery data.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Security Command Center works with Sensitive Data Protection From the official documentation: “Sending Sensitive Data Protection scan results to Security Command Center”
• BigQuery works with Cloud Key Management Service From the official documentation: “Change the Cloud KMS key for a BigQuery table”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Google SecOps From the official documentation: “Google SecOps exports the following categories of data to your BigQuery project:”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Logging works with Security Command Center From the official documentation: “Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.”
• Apigee works with Compute Engine From the official documentation: “| [Compute Engine](https://console.cloud.google.com/apis/library/compute.googleapis.com) | `compute.googleapis.com` | Used for managing your Apigee runtime. |”
• BigQuery works with Security Command Center From the official documentation: “Security Command Center supports discovery and inventory of BigQuery datasets.”
• Cloud Key Management Service secures BigQuery From the official documentation: “You can encrypt data at the dataset or project level with the default customer-managed Cloud Key Management Service keys in BigQuery.”
• Cloud Logging works with Google SecOps From the official documentation: “This document explains how to integrate Cloud Logging with Google Security Operations.”
• Google SecOps works with Security Command Center From the official documentation: “This document explains how to integrate Security Command Center with Google Security Operations.”
• Sensitive Data Protection works with VPC Service Controls From the official documentation: “For information about VPC Service Controls support for Sensitive Data Protection, see the [Supported products](/vpc-service-controls/docs/supported-products#table_dlp) table in the VPC Service Controls documentation.”
• VPC Service Controls secures Compute Engine From the official documentation: “To further protect your Compute Engine resources, you can protect them using [VPC Service Controls](/vpc-service-controls/docs/overview).”
• Apigee works with BigQuery From the official documentation: “You can use the Apigee API to export all analytics data for an entire day from Apigee to your own data repository, such as Google Cloud Storage or BigQuery.”
• Apigee works with Cloud Key Management Service From the official documentation: “If you already created new Cloud KMS encryption keys for Apigee, you can use those rather than create new keys during your setup.”
• Apigee works with Cloud Logging From the official documentation: “This page describes how to find and use [Cloud Logging](/logging/docs) to query and view maintenance logs for an Apigee instance.”
• 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).”
• Apigee works with VPC Service Controls From the official documentation: “Apigee integrations with VPC Service Controls have the following limitations:”
• BigQuery works with Compute Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
• BigQuery works with VPC Service Controls From the official documentation: “BigQuery integrates with VPC Service Controls to restrict access to your BigQuery resources from specific networks.”
• Cloud Key Management Service works with Cloud Logging From the official documentation: “If you [enable audit logging for Cloud KMS](https://cloud.google.com/logging/docs/audit/configure-data-access#config-console-enable), all the operations on the key are logged and viewable in Cloud Logging.”
• Cloud Key Management Service works with Google SecOps From the official documentation: “To control your encryption keys, you can use CMEKs in Cloud KMS with CMEK-integrated services, including Google SecOps, as follows:”
• Cloud Key Management Service works with Sensitive Data Protection From the official documentation: “In contrast, if you're using a software Cloud KMS key with Sensitive Data Protection, no quota values apply.”
• Cloud Key Management Service works with VPC Service Controls From the official documentation: “If you want your Dataproc Metastore service to run inside a [VPC Service Controls](/dataproc-metastore/docs/vpc-sc) perimeter, you must add the Cloud Key Management Service (Cloud KMS) API to the perimeter.”
• Cloud Logging is an alternative to Security Command Center From the official documentation: “After you revoke compromised credentials and restore your service, review all access to your Google Cloud resources. You can use Cloud Logging or Security Command Center.”
• Cloud Logging works with VPC Service Controls From the official documentation: “This page describes how you can find VPC Service Controls errors using Cloud Logging.”
• Compute Engine works with Google SecOps From the official documentation: “This document explains how to integrate Compute Engine with Google Security Operations.”
• Compute Engine works with Security Command Center From the official documentation: “After you activate Security Command Center, it starts to analyze, or scan, your resources for Compute Engine and other Google Cloud services.”
• 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 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.”
• Security Command Center secures BigQuery From the official documentation: “Security Command Center analyzes various logs for potential threats that affect BigQuery resources.”
• Security Command Center secures Cloud Key Management Service From the official documentation: “In addition, Security Command Center has built-in Cloud KMS vulnerability detectors. These detectors help ensure that your projects which include keys follow our recommended best practices.”
• Security Command Center depends on Cloud Logging From the official documentation: “By using Security Command Center, you can see when high-risk threats such as malware, cryptomining, unauthorized access to Google Cloud resources, outgoing DDoS attacks, port scanning, and brute-force SSH have been detected based on your Cloud Logging logs.”
• Security Command Center secures Compute Engine From the official documentation: “Security Command Center performs [agentless](#runtime) and [log-based](#log-based) monitoring of Compute Engine resources.”
• Security Command Center works with VPC Service Controls From the official documentation: “[Enable Security Command Center with VPC Service Controls](/vpc-service-controls/docs/supported-products#table_security_command_center).”
• Sensitive Data Protection secures BigQuery From the official documentation: “To help meet compliance requirements, use Sensitive Data Protection to inspect your BigQuery tables and to help protect your sensitive data.”
• VPC Service Controls secures Cloud Key Management Service From the official documentation: “The Cloud KMS API can be protected by VPC Service Controls and the product can be used inside service perimeters.”
• VPC Service Controls secures Cloud Logging From the official documentation: “The API for Cloud Logging can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• 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.”
• VPC Service Controls secures Security Command Center From the official documentation: “VPC Service Controls protects project-level Security Command Center API resources.”
• VPC Service Controls secures Sensitive Data Protection From the official documentation: “VPC Service Controls enables you to define a security perimeter around your projects and resources, including Sensitive Data Protection resources.”