Sensitive Data Protection

Related topics

• BigQuery works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze BigQuery data.”
• Pub/Sub works with Sensitive Data Protection From the official documentation: “Watch the Pub/Sub topic until the DLP job finishes”
• Cloud Storage works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze a file on GCS.”
• 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.”
• Dataflow works with Sensitive Data Protection From the official documentation: “This proof-of-concept uses Dataflow and Sensitive Data Protection to securely tokenize and import data from a relational database to BigQuery.”
• 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.”
• 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 Monitoring works with Sensitive Data Protection From the official documentation: “Sensitive Data Protection sends detailed telemetry about your Sensitive Data Protection usage to Monitoring.”
• Google Cloud Storage works with Sensitive Data Protection From the official documentation: “This page describes how Sensitive Data Protection can create de-identified copies of data stored in Cloud Storage.”
• 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.”
• Sensitive Data Protection depends on Identity and Access Management From the official documentation: “Sensitive Data Protection uses Identity and Access Management (IAM) to control access to resources.”
• service perimeter secures Sensitive Data Protection From the official documentation: “To learn how to set up a new service perimeter to prohibit external access to Sensitive Data Protection resources, follow the instructions in [Creating a service perimeter](/vpc-service-controls/docs/create-service-perimeters).”
• 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.”
• customer-managed encryption keys depends on Cloud Key Management Service From the official documentation: “These keys are created and managed using Cloud KMS.”
• 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.”
• service perimeter is part of VPC Service Controls From the official documentation: “VPC Service Controls perimeters protect the AlloyDB API.”
• 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”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• BigQuery works with Bigtable From the official documentation: “External BigQuery data source backed by Bigtable”
• Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• Cloud Logging works with customer-managed encryption keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Cloud SQL works with Compute Engine From the official documentation: “This page describes how to use the mysql client, installed on a Compute Engine instance, to connect to Cloud SQL.”
• Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
• Cloud Key Management Service works with customer-managed encryption keys From the official documentation: “With CMEK, Cloud Key Management Service wraps your stored volume keys.”
• Cloud Storage works with Storage Transfer Service From the official documentation: “Transfer data between Cloud Storage services such as AWS S3 and Cloud Storage.”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• customer-managed encryption keys secures Cloud Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• Dataflow works with Spanner From the official documentation: “Use Dataflow to load data into Spanner.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• BigQuery is an alternative to Google Cloud Storage From the official documentation: “The training data can be either a CSV file in Cloud Storage or a table in BigQuery.”
• 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.”
• BigQuery works with Spanner From the official documentation: “Reverse ETL (BigQuery to Spanner)”
• Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
• BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into BigQuery”
• 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 Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• customer-managed encryption keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
• Cloud Key Management Service works with Cloud SQL From the official documentation: “Cloud KMS integrates with Cloud SQL.”
• Cloud Storage works with customer-managed encryption keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• customer-managed encryption keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• customer-managed encryption keys secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
• 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 Monitoring works with Spanner From the official documentation: “Monitor Spanner metrics using Cloud Monitoring.”
• 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).”
• 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.”
• customer-managed encryption keys secures Bigtable From the official documentation: “In a CMEK-protected instance, Bigtable uses your CMEK key to protect your data at rest.”
• customer-managed encryption keys is part of Cloud Key Management Service From the official documentation: “The Cloud KMS keys that you create are customer-managed keys.”
• Google Cloud Storage works with Storage Transfer Service From the official documentation: “We use Storage Transfer Service to transfer data from the appliance to your Cloud Storage bucket.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Spanner From the official documentation: “Identity and Access Management (IAM) lets you control user and group access to Spanner resources at the project, Spanner instance, and Spanner database levels.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Logging works with Storage Transfer Service From the official documentation: “Enable Cloud Logging for agentless transfers, or transfers from S3-compatible sources, with `--log-actions` and `--log-action-states`.”