data residency

Related topics

• Certificate Authority Service works with data residency From the official documentation: “Certificate Authority Service supports the following Google Cloud security products: - [VPC Service Controls (VPC-SC)](/vpc-service-controls/docs/supported-products) - [Access Transparency](/cloud-provider-access-management/access-transparency/docs/supported-services) - [Access…”
• 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 Model Armor From the official documentation: “Model Armor provides the following security horizontals. - [Data Residency](/model-armor/data-residency)”
• 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`”
• Certificate Authority Service works with Cloud Service Mesh From the official documentation: “Configure Cloud Service Mesh to use CA Service”
• Identity and Access Management secures Cloud Service Mesh From the official documentation: “Access to Cloud Service Mesh in the Google Cloud console is controlled by [Identity and Access Management (IAM)](/iam/docs/overview).”
• Cloud Logging works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh stores the dry-run results to Cloud Logging in the following labels:”
• Cloud Monitoring works with Cloud Service Mesh From the official documentation: “Mesh telemetry is no longer automatically ingested into Cloud Monitoring.”
• Cloud Service Mesh works with VPC Service Controls From the official documentation: “You can now use VPC Service Controls with Cloud Service Mesh.”
• Cloud Service Mesh depends on Certificate Authority Service From the official documentation: “Cloud Service Mesh service security depends on the CA Service integration with GKE.”
• Certificate Authority Service works with Cloud Key Management Service From the official documentation: “CA Service is automatically configured to use Cloud Key Management Service for generating, storing, and utilizing CA signing keys.”
• Cloud Logging works with Model Armor From the official documentation: “Use Cloud Logging to analyze Model Armor usage patterns, errors, and performance metrics.”
• 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 Service Mesh works with Identity and Access Management From the official documentation: “For information about how and which permissions are evaluated for each method, see the Identity and Access Management documentation for Cloud Service Mesh.”
• Certificate Authority Service depends on Cloud Key Management Service From the official documentation: “The CA then issues a certificate using the corresponding key in Cloud KMS to sign the certificate digest.”
• Certificate Authority Service works with VPC Service Controls From the official documentation: “Yes, CA Service supports VPC Service Controls.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “If a log entry matches the filter of the alerting policy, then Cloud Logging extracts labels and forwards the data to Cloud Monitoring.”
• 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.”
• Cloud Monitoring works with Model Armor From the official documentation: “This graph uses the metrics that Model Armor publishes to Cloud Monitoring.”
• Cloud Service Mesh depends on Cloud Monitoring From the official documentation: “Cloud Service Mesh uses Cloud Monitoring to provide automatic telemetry and logs.”
• Google SecOps works with Security Command Center From the official documentation: “This document explains how to integrate Security Command Center with Google Security Operations.”
• 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.”
• Model Armor works with Security Command Center From the official documentation: “Model Armor findings are published to Security Command Center on the Premium and Enterprise tiers.”
• 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 Cloud Monitoring From the official documentation: “If you are behind a corporate proxy or firewall, Apigee may not be able to send metrics to Cloud Monitoring with its default settings.”
• Apigee depends on Cloud Service Mesh From the official documentation: “The objective of the runtime plane version support policy is to allow customers the flexibility to schedule upgrades when it meets their business needs, while balancing the rapid evolution of Apigee (and its dependency on underlying components like Anthos and Anthos Service…”
• 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 Model Armor From the official documentation: “The Model Armor and Apigee integration lets you use the AI protection capabilities of Model Armor directly within the Apigee API gateway layer.”
• Apigee works with VPC Service Controls From the official documentation: “Apigee integrations with VPC Service Controls have the following limitations:”
• Certificate Authority Service works with Cloud Monitoring From the official documentation: “[Cloud Monitoring](/monitoring) can be used to monitor operations performed on resources in Certificate Authority Service.”
• Certificate Authority Service works with Google SecOps From the official documentation: “This document provides guidance on how to integrate Symantec Content Analysis with Google SecOps.”
• Certificate Authority Service works with Identity and Access Management From the official documentation: “For information about how and which permissions are evaluated for each method, see the Identity and Access Management documentation for Certificate Authority Service.”
• 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 Cloud Monitoring From the official documentation: “Cloud KMS integrates with Cloud Monitoring.”
• 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 depends on Identity and Access Management From the official documentation: “Whatever the mechanism, Cloud KMS resolves the provided credential to identify the principal (the entity which is authenticated and is authorizing the request), and calls IAM to see whether the principal is authorized to make the request and whether an audit log is written.”
• Cloud Key Management Service works with Identity and Access Management From the official documentation: “The Cloud KMS platform is integrated with [IAM](/iam/docs/overview) and [Cloud Audit Logs](/logging/docs/audit) so that you can manage permissions on individual keys and audit how they are used.”
• 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 Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• 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.”
• Cloud Monitoring depends on Identity and Access Management From the official documentation: “To use Monitoring, you must have the appropriate [Identity and Access Management](/iam/docs/overview) (IAM) permissions.”
• Cloud Monitoring works with VPC Service Controls From the official documentation: “Cloud Monitoring performs the VPC perimeter check when a project is *added* to a metrics scope:”
• Google SecOps works with Identity and Access Management From the official documentation: “Test connectivity to the Identity and Access Management service with parameters provided at the integration configuration page in the Google Security Operations Marketplace tab.”
• 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 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.”
• Identity and Access Management secures Certificate Authority Service From the official documentation: “CA Service uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Cloud Key Management Service From the official documentation: “If you need to prevent a user from using a Cloud KMS resource during the time needed for propagation of an eventually consistent operation, remove the Identity and Access Management (IAM) permission for the resource.”
• Identity and Access Management secures Model Armor From the official documentation: “Model Armor uses Identity and Access Management (IAM) to control access to resources.”
• 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.”
• Model Armor depends on Identity and Access Management From the official documentation: “Model Armor uses Identity and Access Management (IAM) to control access to 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 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 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.”