Cloud Identity

Related topics

• Cloud Identity is an alternative to Google Workspace From the official documentation: “Use a Google Workspace or Cloud Identity account to access the data.”
• Cloud Identity is an alternative to Workforce Identity Federation From the official documentation: “To reduce complexity, we recommend using either Cloud Identity or Workforce Identity Federation.”
• Cloud Identity works with Google Cloud Directory Sync From the official documentation: “GCDS can provision users and groups from an LDAP directory to Cloud Identity or Google Workspace.”
• SAML profile is part of Cloud Identity From the official documentation: “Cloud Identity and Google Workspace let you create multiple SAML profiles.”
• Access Transparency works with Cloud Identity From the official documentation: “Enables Access Transparency controls for Cloud Identity.”
• Active Directory works with Cloud Identity From the official documentation: “This approach lets you [federate Active Directory with Cloud Identity](/architecture/identity/federating-gcp-with-azure-active-directory) without depending on the availability of resources or connectivity to the on-premises network.”
• Cloud Identity works with Cloud Logging From the official documentation: “Configure Cloud Identity to [route logs to Cloud Logging](/logging/docs/audit/configure-gsuite-audit-logs) so that you can handle these audit logs the same way as other Google Cloud logs, including setting up alerts or use an external Security information and event management…”
• Cloud Identity works with Cloud SQL From the official documentation: “After the IAM group users have lost membership to all the applicable groups in Cloud Identity, Cloud SQL removes those group users from the instance automatically.”
• Cloud Identity works with Google SecOps From the official documentation: “This document explains how to integrate Cloud Identity with Google Security Operations.”
• Cloud Identity works with Google Workspace From the official documentation: “You can add a Google Workspace subscription to either or both Cloud Identity subscriptions.”
• Cloud Identity works with identity provider From the official documentation: “If you selected an architecture that uses an external IdP, learn how to map the logical model of your external IdP to Cloud Identity or Google Workspace.”
• Cloud Identity works with single sign-on From the official documentation: “Enabling single sign-on between Cloud Identity or Google Workspace and your external IdP improves the user experience for employees.”
• Cloud Identity Policy API depends on Cloud Identity From the official documentation: “Before you use any of the Cloud Identity APIs, you must set up Cloud Identity.”
• single sign-on is part of Cloud Identity From the official documentation: “When you enable single sign-on in Cloud Identity or Google Workspace, all users (with the exception of super admins) are forced to use single sign-on.”
• 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”
• Cloud Storage works with Google SecOps From the official documentation: “Configure a feed in Google SecOps to ingest from Google Cloud Storage”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Certificate Authority Service works with Cloud SQL From the official documentation: “Cloud SQL hosts and manages the root CA and subordinate server CAs on Google Cloud Certificate Authority Service (CA Service).”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• 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:”
• Certificate Authority Service works with Cloud Storage From the official documentation: “For a Google-managed Cloud Storage bucket, CA Service creates a Google-managed bucket in the same location as the CA.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• 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.”
• Google Cloud Directory Sync works with Google Workspace From the official documentation: “GCDS can provision users and groups from an LDAP directory to Cloud Identity or Google Workspace.”
• VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
• Access Transparency works with Google Workspace From the official documentation: “You can use the Google Cloud console to access the Access Transparency logs that Google Workspace services generate.”
• BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
• BigQuery is an alternative to Google Workspace From the official documentation: “If your people data is not in Google Workspace, you can import it from Cloud Storage or BigQuery.”
• Certificate Authority Service works with VPC Service Controls From the official documentation: “Yes, CA Service supports VPC Service Controls.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Logging works with Google SecOps From the official documentation: “This document explains how to integrate Cloud Logging with Google Security Operations.”
• Cloud Logging works with Google Workspace From the official documentation: “Google Workspace lets you share its logs with the Google Cloud logging service.”
• Cloud SQL works with Workforce Identity Federation From the official documentation: “Workforce Identity Federation lets you use your existing identity provider (IdP), such as Microsoft Active Directory or Okta, to access Cloud SQL instances without requiring a Google Account.”
• 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 works with Google Workspace From the official documentation: “Connect Workspace and Google SecOps to detect insider risks in your environment”
• SAML profile is part of Google Workspace From the official documentation: “Cloud Identity and Google Workspace let you create multiple SAML profiles.”
• 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).”
• Workforce Identity Federation depends on Cloud Logging From the official documentation: “However, Workforce Identity Federation detailed audit logging uses Cloud Logging.”
• Access Transparency works with Certificate Authority Service 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)”
• Active Directory works with Google Cloud Directory Sync From the official documentation: “As part of the provisioning process, GCDS generates a list of users in Cloud Identity or Google Workspace that don't have corresponding matches in the Active Directory LDAP query results.”
• Active Directory works with Google SecOps From the official documentation: “This document explains how to integrate Active Directory with Google Security Operations.”
• 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.”
• 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 Workforce Identity Federation 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…”
• 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 works with VPC Service Controls From the official documentation: “This page describes how you can find VPC Service Controls errors using Cloud Logging.”
• Cloud Logging works with Workforce Identity Federation From the official documentation: “Errors at this stage are often visible in Cloud Logging for Workforce Identity Federation.”