Data Access audit logs

Related topics

• Data Access audit logs is part of Cloud Audit Logs From the official documentation: “You need to turn on [Data Access audit logs](/logging/docs/audit#data-access) for login tracking.”
• Data Access audit logs is part of Cloud Logging
• 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”
• 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 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 Storage works with Database Migration Service From the official documentation: “Database Migration Service replicates data from SQL Server backup and transaction log files that you upload to a Cloud Storage bucket.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
• Cloud Audit Logs works with VPC Service Controls From the official documentation: “VPC Service Controls integrate with Cloud Audit Logs to monitor access to the control plane.”
• Cloud Logging works with Database Migration Service From the official documentation: “Database Migration Service uses Cloud Logging.”
• 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.”
• 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.”
• Database Migration Service depends on Cloud Logging From the official documentation: “Database Migration Service uses Cloud Logging.”
• BigQuery works with Cloud Key Management Service From the official documentation: “Checks if BigQuery tables are encrypted using CustomerManaged Encryption Keys (CMEK) in Cloud KMS.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud Audit Logs works with Cloud Key Management Service From the official documentation: “Cloud Audit Logs for Cloud KMS in the Activity stream read like generic logs, and are not easily read by a human.”
• Cloud Audit Logs works with Cloud Storage From the official documentation: “Use Cloud Audit Logs to generate logs for API operations performed in Cloud Storage.”
• 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 Audit Logs works with Pub/Sub From the official documentation: “Working with audit logs Learn about the default and optional logs created by Pub/Sub as part of Cloud Audit Logs”
• Cloud Key Management Service secures BigQuery From the official documentation: “You can encrypt data at the dataset or project level with the default customer-managed Cloud Key Management Service keys in BigQuery.”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
• 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.”
• 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.”
• 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 Audit Logs secures BigQuery From the official documentation: “For BigQuery, [Cloud Audit Logs](/logging/docs/audit) is used for both data access logs and audit logs, which are enabled by default.”
• Cloud Audit Logs works with Cloud Logging From the official documentation: “For real-time analysis, alerting, and visualization, stream the audit logs to [Cloud Logging](/logging/docs/overview).”
• Cloud Audit Logs works with Database Migration Service From the official documentation: “This document describes audit logging for Database Migration Service. Google Cloud services generate audit logs that record administrative and access activities within your Google Cloud resources.”
• 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 Storage From the official documentation: “If you select **Cloud KMS key**, then provide a [Cloud Key Management Service key](/storage/docs/encryption/using-customer-managed-keys).”
• Cloud Key Management Service works with Database Migration Service From the official documentation: “If you need more control over the keys used to encrypt data at rest within a Google Cloud project, then Database Migration Service offers the ability to protect your data using encryption keys managed by you within [Cloud Key Management Service (KMS)](/kms/docs).”
• 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 works with VPC Service Controls From the official documentation: “This page describes how you can find VPC Service Controls errors using Cloud Logging.”
• Database Migration Service depends on Cloud Storage From the official documentation: “If you use file export and import to migrate, or use the Database Migration Service migration tool, you need to create a Cloud Storage bucket.”
• VPC Service Controls secures Database Migration Service
• VPC Service Controls secures Pub/Sub From the official documentation: “If you use [VPC Service Controls](/vpc-service-controls/docs/overview) and your Pub/Sub topic is part of a project inside a service perimeter, you must grant access to projects in order to create notifications.”