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 From the official documentation: “The generated MySQL audit logs for a given instance are sent to Cloud Logging as [Data Access audit logs](/logging/docs/audit#data-access).”
• Data Access audit logs works with Logs Explorer From the official documentation: “Once configured, you can [view Data Access audit logs](/logging/docs/audit#data-access) of successful logins using the **Logs Explorer**.”
• 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”
• Logs Explorer is part of Cloud Logging From the official documentation: “To view and filter Model Armor logs, use the Logs Explorer in Logging:”
• 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 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 Service Mesh works with VPC Service Controls From the official documentation: “You can now use VPC Service Controls with Cloud Service Mesh.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
• 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.”
• 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 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 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.”
• 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 Storage From the official documentation: “Use Cloud Audit Logs to generate logs for API operations performed in Cloud Storage.”
• App Engine works with Cloud Logging From the official documentation: “App Engine automatically sends both the request logs and app logs to the [Cloud Logging](/logging/docs/overview) agent.”
• App Engine works with Cloud Storage From the official documentation: “To use a Cloud Storage bucket from an App Engine app:”
• App Engine works with Pub/Sub From the official documentation: “Pub/Sub is now the preferred way of performing pull queue work in App Engine.”
• 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”
• App Engine works with BigQuery From the official documentation: “App Engine - Scalable platform as a service (PaaS) solution used to call the Monitoring API and write to BigQuery.”
• App Engine works with Cloud Audit Logs From the official documentation: “This document describes the audit logs created by App Engine as part of [Cloud Audit Logs](/logging/docs/audit).”
• App Engine depends on Cloud Storage From the official documentation: “App Engine creates a [default Cloud Storage multi-regional bucket](/appengine/docs/flexible/locations#cloud-storage-location) on your behalf on the same region where it creates your application. It requires this bucket to store the contents of your application.”
• App Engine is an alternative to Cloud Storage From the official documentation: “You can use durable storage like Cloud Storage or an in-memory cache like App Engine to share data between pipeline instances.”
• App Engine works with Logs Explorer From the official documentation: “This guides shows you how to view App Engine logs by using the Logs Explorer and the Google Cloud console.”
• 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 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 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 Cloud Service Mesh From the official documentation: “This document describes the audit logs created by Cloud Service Mesh as part of [Cloud Audit Logs](/logging/docs/audit).”
• Cloud Audit Logs secures Cloud Service Mesh From the official documentation: “Cloud Audit Logs audits mesh operations.”
• Cloud Audit Logs works with Logs Explorer From the official documentation: “You can audit the history of BigQuery tables by querying Cloud Audit Logs in Logs Explorer.”
• 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 Logs Explorer From the official documentation: “VM serial console logs are streamed to Cloud Logging and can be viewed in Logs Explorer.”
• 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.”
• Logs Explorer works with Pub/Sub From the official documentation: “You can use **Logs Explorer** to view Pub/Sub logs.”
• 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.”
• VPC Service Controls secures Cloud Service Mesh From the official documentation: “VPC Service Controls help defend against data exfiltration attacks and prevent external attackers from accessing services inside a mesh.”