Cloud Data Loss Prevention

Related topics

• Application Default Credentials secures Cloud Data Loss Prevention From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
• Cloud Data Loss Prevention is part of Sensitive Data Protection From the official documentation: “Cloud Data Loss Prevention (Cloud DLP) is now a part of Sensitive Data Protection.”
• BigQuery works with Cloud Data Loss Prevention From the official documentation: “You can use Sensitive Data Protection to compute numerical and categorical numerical statistics for individual columns in BigQuery tables.”
• inspection template configures Cloud Data Loss Prevention From the official documentation: “Use templates to create and persist configuration information for use with Cloud DLP.”
• 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.”
• Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• 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 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 Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up 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 Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Knowledge Catalog depends on Application Default Credentials From the official documentation: “To authenticate to Knowledge Catalog, 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.”
• BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
• 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.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• Pub/Sub works with Sensitive Data Protection From the official documentation: “Watch the Pub/Sub topic until the DLP job finishes”
• 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 Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
• Cloud Monitoring works with Cloud SQL From the official documentation: “You can also get more details by viewing the Cloud Monitoring logs for your Cloud SQL destination instance.”
• Cloud SQL works with Knowledge Catalog From the official documentation: “You can use Knowledge Catalog to organize and enrich the metadata of Cloud SQL resources.”
• Cloud Storage works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze a file on GCS.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Application Default Credentials secures Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, 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.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Security Command Center works with Sensitive Data Protection From the official documentation: “Sending Sensitive Data Protection scan results to Security Command Center”
• Application Default Credentials works with Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
• Cloud SQL works with Sensitive Data Protection From the official documentation: “Sensitive Data Protection starts identifying your Cloud SQL instances and creating a default connection for each instance.”
• Cloud Monitoring works with Pub/Sub From the official documentation: “Use Cloud Monitoring and Pub/Sub to set up custom monitoring and alerting policies for exported logs.”
• Application Default Credentials secures Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
• Application Default Credentials configures Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
• BigQuery works with Security Command Center From the official documentation: “Security Command Center supports discovery and inventory of BigQuery datasets.”
• inspection template is part of Sensitive Data Protection From the official documentation: “Inspection templates are a core component of the Sensitive Data Protection platform.”
• Knowledge Catalog works with Sensitive Data Protection From the official documentation: “Send the results of a [BigQuery inspection job](/sensitive-data-protection/docs/inspecting-storage#inspect_a_table) to Knowledge Catalog.”
• Pub/Sub works with Security Command Center From the official documentation: “This page explains how to use the Security Command Center API to enable finding notifications for Pub/Sub.”
• Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• Application Default Credentials works with Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
• Application Default Credentials works with Cloud SQL From the official documentation: “Application Default Credentials are part of the client libraries you can use to access Cloud SQL.”
• Application Default Credentials configures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
• Application Default Credentials configures Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
• Application Default Credentials secures Security Command Center From the official documentation: “To authenticate to Security Command Center, set up Application Default Credentials.”
• 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.”
• Cloud Monitoring works with Knowledge Catalog From the official documentation: “Knowledge Catalog is integrated with Cloud Monitoring, which collects metrics, events, and metadata from Knowledge Catalog services.”
• Cloud Monitoring works with Sensitive Data Protection From the official documentation: “Sensitive Data Protection sends detailed telemetry about your Sensitive Data Protection usage to Monitoring.”
• Cloud SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud Storage works with Knowledge Catalog From the official documentation: “To automatically discover and build inventories of the data assets, integrate Knowledge Catalog with your storage systems, such as [BigQuery](/bigquery/docs/introduction), [Cloud Storage](/storage/docs/introduction), and [Pub/Sub](/pubsub/docs/overview).”
• Knowledge Catalog depends on Cloud Storage From the official documentation: “Looker (Google Cloud core) publishes LookML metadata to regional Cloud Storage repositories for Knowledge Catalog to consume through a batch sync process.”
• Knowledge Catalog works with Pub/Sub From the official documentation: “To automatically discover and build inventories of the data assets, integrate Knowledge Catalog with your storage systems, such as [BigQuery](/bigquery/docs/introduction), [Cloud Storage](/storage/docs/introduction), and [Pub/Sub](/pubsub/docs/overview).”
• Security Command Center secures BigQuery From the official documentation: “Security Command Center analyzes various logs for potential threats that affect BigQuery resources.”