Ensure Cloud Audit Logging is configured properly across all services and all users from a project

Using Command Line

1. To Read project's IAM policy and store it in a file run a command:

gcloud projects get-iam-policy \[PROJECT_ID\] > /tmp/policy.yaml

1. Edit policy in /tmp/policy.yaml, adding or changing only the audit logs configuration to:

auditConfigs:
- auditLogConfigs:
  - logType: DATA_WRITE
  - logType: DATA_READ
  service: allServices

Note: exemptedMembers: is not set as audit logging should be enabled for all the users

1. To write new IAM policy run command:

gcloud projects set-iam-policy \[PROJECT_ID\] /tmp/policy.yaml

If the preceding command reports a conflict with another change, then repeat these steps, starting with the first step.

Impact

There is no charge for Admin Activity audit logs. Enabling the Data Access audit logs might result in your project being charged for the additional logs usage.

Default Value

Admin Activity logs are always enabled. They cannot be disabled. Data Access audit logs are disabled by default because they can be quite large.

References

1. https://cloud.google.com/logging/docs/audit/ 2.https://cloud.google.com/logging/docs/audit/https://cloud.google.com/logging/docs/audit/configure-data-access

Notes

• Log type DATA_READ is equally important to that of DATA_WRITE to track detailed user activities.
• BigQuery Data Access logs are handled differently from other Data Access logs. BigQuery logs are enabled by default and cannot be disabled. They do not count against logs allotment and cannot result in extra logs charges.

Google Cloud Console (Asset-Level)

1. Open the affected project/resource from the finding details in Google Cloud Console.
2. Navigate to the resource security/configuration settings.
3. Apply the control-specific secure configuration.
4. Save and re-run the check.

Multiple Remediation Paths

Google Cloud

SERVICE-WIDE (RECOMMENDED when many resources are affected): Enforce Organization Policies at org/folder level so new resources inherit secure defaults.

gcloud org-policies set-policy policy.yaml

ASSET-LEVEL: Use the product-specific remediation steps above for only the impacted project/resources.

PREVENTIVE: Use org policy constraints/custom constraints and enforce checks in deployment pipelines.

References for Service-Wide Patterns

• GCP Organization Policy overview: https://cloud.google.com/resource-manager/docs/organization-policy/overview
• GCP Organization policy constraints catalog: https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints
• gcloud org-policies: https://cloud.google.com/sdk/gcloud/reference/org-policies

Operational Rollout Workflow

Use this sequence to reduce risk and avoid repeated drift.

1. Contain at Service-Wide Scope First (Recommended)

• Google Cloud: apply organization policy constraints at org/folder scope.

gcloud org-policies set-policy policy.yaml

2. Remediate Existing Affected Assets

• Execute the control-specific Console/CLI steps documented above for each flagged resource.
• Prioritize internet-exposed and production assets first.

3. Validate and Prevent Recurrence

• Re-scan after each remediation batch.
• Track exceptions with owner and expiry date.
• Add preventive checks in IaC/CI pipelines.