This page provides supplemental information for using Cloud Audit Logs with Cloud Storage. Use Cloud Audit Logs to generate logs for API operations performed in Cloud Storage. To set up Cloud Audit Logs, see Configuring Data Access Logs.
Google Cloud services write audit logs to help you answer the questions, "Who did what, where, and when?" Your Cloud projects contain only the audit logs for resources that are directly within the project. Other entities, such as folders, organizations, and Cloud Billing accounts, contain the audit logs for the entity itself.
Cloud Audit Logs generates the following audit logs for operations in Cloud Storage:
Admin Activity logs: Entries for operations that modify the configuration or metadata of a project, bucket, or object.
Data Access logs: Entries for operations that modify objects or read a project, bucket, or object. There are several sub-types of data access logs:
ADMIN_READ: Entries for operations that read the configuration or metadata of a project, bucket, or object.
DATA_READ: Entries for operations that read an object.
DATA_WRITE: Entries for operations that create or modify an object.
The following table summarizes which Cloud Storage operations correspond to each audit log type:
|Log entry type||Sub-type||Operations|
1 Copying and composing objects involve both reading and writing data. As a result, these actions each generate two log entries.
3 Admin Activity logs are not generated if/when ACLs are initially set at object creation. Additionally, if an object ACL is set to public, audit logs are not generated for reads or writes to that object or its ACL.
Audit log format
Audit log entries include the following components:
The log entry itself, which is a
LogEntryobject. Useful fields within a log entry include the following:
logNamecontains the project identification and audit log type.
resourcecontains the target of the audited operation.
timeStampcontains the time of the audited operation.
protoPayloadcontains the audited information.
The audit logging data, which is an
AuditLogobject held in the
protoPayloadfield of the log entry. An
AuditLogobject entry contains information such as:
- The user who made the request, including the email address of that user.
- The resource name on which the request was made.
- The outcome of the request.
- Optionally, detailed request and response information. For more information, see Detailed Audit Logging mode.
For other fields in these objects, and how to interpret them, review Understanding audit logs.
logName field indicates the Cloud project or other
Google Cloud entity that owns the audit logs and whether the log entry
contains Admin Activity or Data Access logging data. For example, the following
shows the log names for a project's Admin Activity audit logs and its Data
Access audit logs. The variable denotes the project associated with the log.
Logs pertaining to Cloud Storage operations use the service name
For information about all logging services, see Mapping services to resources.
Logs pertaining to Cloud Storage are categorized under the resource
For a list of other resource types, see Monitored resource types.
Admin Activity logs are recorded by default. These logs do not count towards your log ingestion quota.
Data Access logs pertaining to Cloud Storage operations are not recorded by default. To learn how to enable logs for data access-type operations, see Configuring Data Access Logs. Note that unlike Admin Activity logs, Data Access logs count towards your log ingestion quota and can affect your Cloud Logging charges.
The following users can view Admin Activity logs:
- Project owners, editors, and viewers.
- Users with the Logs Viewer IAM role.
- Users with the
The following users can view Data Access logs:
- Project owners.
- Users with the Private Logs Viewer IAM role.
- Users with the
See Adding IAM members to a project for instructions on granting access.
You can export audit logs in the same way that you export other kinds of logs. For details about how to export your logs, see Exporting logs.
The following restrictions apply to Cloud Audit Logs with Cloud Storage:
- Cloud Audit Logs does not track access to public objects.
- Cloud Audit Logs does not track changes made by the Object Lifecycle Management feature.
- Data Access logs cause authenticated browser downloads to fail.