audit logging

Related topics

• audit logging works with Cloud Logging From the official documentation: “The Access Context Manager audit log is written into the "Audited Resource" logging stream and is available in Cloud Logging.”
• audit logging works with Cloud Audit Logs From the official documentation: “GKE clusters integrate a default configuration for [GKE audit logging](/kubernetes-engine/docs/how-to/audit-logging) with [Cloud Audit Logs](/logging/docs/audit) and [Logging](/logging/docs).”
• audit logging works with row-level access policies From the official documentation: “Creation and deletion of row-level access policies are audit logged, and can be accessed through [Cloud Logging](/logging/docs/overview).”
• Cloud Audit Logs works with Logs Explorer From the official documentation: “You can query these logs in the Logs Explorer and check which API methods generate Cloud Audit Logs.”
• 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: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud Logging works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh integrates with Cloud Logging and Cloud Monitoring.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• 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 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 Audit Logs works with Cloud Storage From the official documentation: “This page provides supplemental information for using [Cloud Audit Logs](/logging/docs/audit) with Cloud Storage.”
• 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 Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
• 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 Security Command Center From the official documentation: “Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Security Command Center From the official documentation: “Security Command Center supports discovery and inventory of BigQuery datasets.”
• 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 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.”
• 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.”
• Logs Explorer is part of Cloud Logging From the official documentation: “To view and filter Model Armor logs, use the Logs Explorer in Logging:”
• Pub/Sub works with Security Command Center From the official documentation: “You can configure whether Security Command Center exports a snapshot of deleted findings to Pub/Sub.”
• 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 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 [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 Security Command Center From the official documentation: “Cloud Audit Logs for Security Command Center let you track administrative and data-access operations on your resources to help you monitor access and configuration changes.”
• Cloud Logging is an alternative to Security Command Center From the official documentation: “After you revoke compromised credentials and restore your service, review all access to your Google Cloud resources. You can use Cloud Logging or Security Command Center.”
• Logs Explorer works with Pub/Sub From the official documentation: “You can use **Logs Explorer** to view Pub/Sub logs.”
• row-level access policies is part of BigQuery From the official documentation: “At a high level, row-level security involves the creation of row-level access policies on a target BigQuery table.”
• Security Command Center secures BigQuery From the official documentation: “Security Command Center analyzes various logs for potential threats that affect BigQuery resources.”
• Security Command Center depends on Cloud Logging From the official documentation: “By using Security Command Center, you can see when high-risk threats such as malware, cryptomining, unauthorized access to Google Cloud resources, outgoing DDoS attacks, port scanning, and brute-force SSH have been detected based on your Cloud Logging logs.”
• Security Command Center secures Cloud Storage From the official documentation: “Security Command Center analyzes various logs for potential threats that affect Cloud Storage resources.”