8/23/2020 BigQuery audit logs overview | Google Cloud BigQuery audit logs overview Overview Cloud Audit Logs are a collection of logs provided by Google Cloud that provide insight into operational concerns related to your use of Google Cloud services. This page provides details about BigQuery specic log information, and it demonstrates how to use BigQuery to analyze logged activity. Versions The audit log message system relies on structured logs, and the BigQuery service provides three distinct kinds of messages: AuditData (#auditdata_examples): The old version of logs, which reports API invocations. BigQueryAuditMetadata (#bigqueryauditmetadata_examples): The new version of logs, which reports resource interactions such as which tables were read from and written to by a given query job and which tables expired due to having an expiration time congured. In general, users will want to leverage the new BigQueryAuditMetadata logs functionality. AuditLog (#auditlog_examples): The logs that BigQuery Reservations (/bigquery/docs/reservations-intro) and BigQuery Connections (/bigquery/docs/reference/bigqueryconnection/rest) use when reporting requests. Message Formats AuditData format The AuditData (/bigquery/docs/reference/auditlogs/rest/Shared.Types/AuditData) messages are communicated within the protoPayload.serviceData submessage within the Cloud Logging LogEntry (/logging/docs/reference/v2/rest/v2/LogEntry) message. https://cloud.google.com/bigquery/docs/reference/auditlogs 1/11 8/23/2020 BigQuery audit logs overview | Google Cloud BigQueryAuditMetadata format You can nd BigQueryAuditMetadata (/bigquery/docs/reference/auditlogs/rest/Shared.Types/BigQueryAuditMetadata) details in the protoPayload.metadata submessage that is in the Cloud Logging LogEntry (/logging/docs/reference/v2/rest/v2/LogEntry) message. In the Cloud Logging logs, the protoPayload.serviceData information is not set or used. In BigQueryAuditMetadata messages, there is more information: resource.type is set to one of the following values: bigquery_project for jobs resource.labels.location contains the location of the job. bigquery_dataset for storage resource.labels.dataset_id contains the encapsulating dataset. protoPayload.methodName is set to one of the following values: google.cloud.bigquery.v2.TableService.InsertTable google.cloud.bigquery.v2.TableService.UpdateTable google.cloud.bigquery.v2.TableService.PatchTable google.cloud.bigquery.v2.TableService.DeleteTable google.cloud.bigquery.v2.DatasetService.InsertDataset google.cloud.bigquery.v2.DatasetService.UpdateDataset google.cloud.bigquery.v2.DatasetService.PatchDataset google.cloud.bigquery.v2.DatasetService.DeleteDataset google.cloud.bigquery.v2.TableDataService.List google.cloud.bigquery.v2.JobService.InsertJob google.cloud.bigquery.v2.JobService.Query google.cloud.bigquery.v2.JobService.GetQueryResults InternalTableExpired https://cloud.google.com/bigquery/docs/reference/auditlogs 2/11 8/23/2020 BigQuery audit logs overview | Google Cloud protoPayload.resourceName now contains the URI for the referenced resource. For example, a table created by using an insert job reports the resource URI of the table The earlier format reported the API resource (the job identier). protoPayload.authorizationInfo only includes information relevant to the specic event. With earlier AuditData messages, you could merge multiple records when source and destination tables were in the same dataset in a query job. AuditLog format BigQuery Reservations (/bigquery/docs/reservations-intro) uses the AuditLog (/logging/docs/reference/audit/auditlog/rest/Shared.Types/AuditLog) format when reporting requests. Logs contain information such as: resource.type is set to: bigquery_project for jobs resource.labels.location contains the location of the reservation-related resource. protoPayload.methodName is set to one of the following values: google.cloud.bigquery.reservation.v1beta1.ReservationService.CreateReserva tion google.cloud.bigquery.reservation.v1beta1.ReservationService.DeleteReserva tion google.cloud.bigquery.reservation.v1beta1.ReservationService.UpdateReserva tion google.cloud.bigquery.reservation.v1beta1.ReservationService.CreateCapacit yCommitment google.cloud.bigquery.reservation.v1beta1.ReservationService.DeleteCapacit yCommitment google.cloud.bigquery.reservation.v1beta1.ReservationService.CreateAssignm ent google.cloud.bigquery.reservation.v1beta1.ReservationService.DeleteAssignm ent https://cloud.google.com/bigquery/docs/reference/auditlogs 3/11 8/23/2020 BigQuery audit logs overview | Google Cloud google.cloud.bigquery.reservation.v1beta1.ReservationService.MoveAssignmen t BigQuery Connections (/bigquery/docs/reference/bigqueryconnection/rest) uses the AuditLog (/logging/docs/reference/audit/auditlog/rest/Shared.Types/AuditLog) format when reporting requests. Logs contain information such as: resource.type is set to: audited_resource resource.labels.method contains the full method name. resource.labels.project_id contains the project name. resource.service contains service name. protoPayload.methodName is set to one of the following values: google.cloud.bigquery.connection.v1.ConnectionService.CreateConnection google.cloud.bigquery.connection.v1.ConnectionService.DeleteConnection google.cloud.bigquery.connection.v1.ConnectionService.UpdateConnection google.cloud.bigquery.connection.v1.ConnectionService.SetIamPolicy Mapping audit entries to log streams Audit logs are organized into the following three streams. For more information about the streams, see the Cloud Audit Logs (/logging/docs/audit) documentation. Data access System event Admin activity Data access (data_access) The data_access stream contains entries about jobs by using the JobInsertion and JobChange events and about table data modications by using the TableDataChange and TableDataRead https://cloud.google.com/bigquery/docs/reference/auditlogs 4/11 8/23/2020 BigQuery audit logs overview | Google Cloud events. For example, when a load job appends data to a table, the data_access stream adds a TableDataChange event. A TableDataRead event indicates when a consumer reads a table. Note: BigQuery does not emit data access log entries in the following scenarios: Data appended to a table by using the streaming insert mechanism does not generate TableDataChange log entries. Recursive dataset deletions, such as removing a dataset and its contents in a single API call, do not yield deletion entries for each resource contained in the dataset. The dataset removal is present in the activity log. Partitioned tables do not generate TableDataChange entries for partition expirations. Wildcard tables access generates a single TableDataRead entry and doesn't write a separate entry for each queried table. System event (system_event) You can set an expiration time on tables to remove them at a specied time. The system_event stream reports a TableDeletion event when the table expires and is removed. Admin activity (activity) The main activity stream reports all remaining activities and events such as table and dataset creation. Creating, deleting, and updating resources related to BigQuery Reservations (/bigquery/docs/reservations-concepts) are reported in the admin activity stream. Visibility and access control BigQuery audit logs can include information that users might consider sensitive, such as SQL text, schema denitions, and identiers for resources such as table and datasets. For information about managing access to this information, see the Cloud Logging access control documentation (/logging/docs/access-control). https://cloud.google.com/bigquery/docs/reference/auditlogs 5/11 8/23/2020 BigQuery audit logs overview | Google Cloud Caller identities and resource names Caller identities and IP addresses are redacted from the audit logs if all of the following conditions are true: This is a read-only access. The resource is public. The identity is not a service account that belongs to the project. The identity does not belong to the same customer as the project. For cross-project access, there are additional rules that apply: The billing project must be the project that sends the request, and the data project must be the project whose resources are also accessed during the job. For example, a query job in a billing project reads some table data from the data project. The billing project resource ID is redacted from the data project log unless the projects have the same domain associated with them or are in the same organization. Identities and caller IP addresses are not redacted from the data project log if either one of the preceding conditions apply or the billing project and the data project are in the same organization and the billing project already includes the identity and caller IP address. Cloud Logging expos BigQuery automatically sends audit logs to Cloud Logging. Cloud Logging lets users lter and export messages to other services (/logging/docs/export), including Pub/Sub, Cloud Storage, and BigQuery. With long term log retention and log exports to BigQuery, you can do aggregated analysis on logs data. Cloud Logging documents how messages are transformed (/logging/docs/export/bigquery) when exported to BigQuery. Filtering expos To lter relevant BigQuery Audit messages, you can express lters as part of the export. https://cloud.google.com/bigquery/docs/reference/auditlogs 6/11 8/23/2020 BigQuery audit logs overview | Google Cloud For example, the following advanced lter represents an export that only includes the newer BigQueryAuditMetadata format: Payload.metadata."@type"="type.googleapis.com/google.cloud.audit.BigQueryAuditMetada