data residency

Related topics

• 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 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”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Artifact Registry works with Compute Engine From the official documentation: “Compute Engine can pull containers directly from Artifact Registry repositories.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• 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.”
• Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
• VPC Service Controls secures Artifact Registry From the official documentation: “If your VPC Service Controls settings are blocking access to Artifact Registry, you must add the Artifact Registry service to the service perimeter of your VPC Service Controls.”
• BigQuery works with Security Command Center From the official documentation: “Security Command Center supports discovery and inventory of BigQuery datasets.”
• Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
• 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).”
• Artifact Registry works with Cloud Logging From the official documentation: “Artifact Registry sends the following types of audit log data to Cloud Logging:”
• Artifact Registry depends on Cloud Storage From the official documentation: “The registry service hosts your custom images in Cloud Storage under your Google Cloud project.”
• Artifact Registry works with Cloud Storage From the official documentation: “| Artifact Registry | Stored in Cloud Storage, for each data chunk | |”
• Artifact Registry is an alternative to Cloud Storage From the official documentation: “Re-upload the template or definition to Artifact Registry or Cloud Storage.”
• Artifact Registry works with Security Command Center From the official documentation: “Security Command Center aggregates vulnerability findings from Artifact Registry scans, allowing you to view container image vulnerabilities within your running workloads, across all projects alongside your other security risks in Security Command Center.”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• 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 Logging is an alternative to Cloud Storage From the official documentation: “When you specify your own service account for builds, you must store your build logs either in Cloud Logging or in a user-created Cloud Storage bucket.”
• 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 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.”
• Identity and Access Management secures Artifact Registry From the official documentation: “This page describes access control with Identity and Access Management (IAM) in Artifact Registry.”
• Identity and Access Management works with Security Command Center From the official documentation: “This page describes how to use Identity and Access Management (IAM) to control access to resources in an organization-level activation of Security Command Center.”
• Identity and Access Management secures Security Command Center From the official documentation: “Security Command Center uses Identity and Access Management (IAM) to control access to resources at different levels of your resource hierarchy.”
• 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 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 Cloud Storage From the official documentation: “Security Command Center analyzes various logs for potential threats that affect Cloud Storage resources.”
• 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).”
• 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 Security Command Center From the official documentation: “VPC Service Controls protects project-level Security Command Center API resources.”