Google Cloud security checklist: 12 access checks for every organization and project
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
The Google Cloud security checklist here picks 12 of the 40 access-layer checks and says where to look: Cloud Identity, IAM policies, organization policy constraints, VPC Service Controls, Cloud Logging and Policy Intelligence. Run them at the organization node and in each project. Read 16 Nov 2026.
Start the assessment ยท All guides
Twelve checks cover the Google Cloud access layer
Google Cloud policy attaches at the organization, folder and project levels and is inherited downward. The checks below, taken from the assessment checklist, say which setting to read at which level.
| Check | Where to look in Google Cloud |
|---|---|
| People sign in through single sign-on with MFA | In Cloud Identity, check that Google Cloud sign-in is bound to your SSO profile, and that IAM policies contain no consumer accounts (gmail.com). |
| Long-lived keys removed or rotated every 90 days | Run gcloud iam service-accounts keys list for each service account with --managed-by=user, and use the Policy Intelligence service account insights to find unused keys. |
| Workloads use platform-issued identities | Check that workloads use attached service accounts or workload identity federation, and that the iam.disableServiceAccountKeyCreation org policy is enforced. |
| Administrator roles are few, named and separate | Run gcloud projects get-iam-policy and the organization equivalent, and count members with roles/owner or roles/editor. |
| No public IP address by default | List instances with external IPs (gcloud compute instances list) and check that the compute.vmExternalIpAccess org policy constraint is enforced. |
| Metadata service hardened | Check that GKE clusters use Workload Identity (metadata server mode GKE_METADATA) and that Compute Engine instances do not run with the default service account. |
| Public object storage blocked organization-wide | Check that the storage.publicAccessPrevention org policy constraint is enforced and that buckets show Public access prevention on. |
| Sharing limited to your own organization | Check that the iam.allowedPolicyMemberDomains org policy (domain restricted sharing) is enforced and lists only your own customer IDs. |
| Sensitive data readable from trusted networks only | List VPC Service Controls perimeters and access levels, and check the sensitive projects are inside one in enforced mode, not dry run. |
| Deny policies at the organization level | List organization policy constraints enforced at the organization node (gcloud org-policies list) and check the security-relevant ones are set. |
| Audit logs on in every account and region | Check that Admin Activity logs are always on and that Data Access audit logs are enabled for sensitive services at the organization level. |
| Logs stored where workload admins cannot change them | Check log sinks to a bucket in a separate project with bucket lock or locked log buckets with a retention period. |
Organization policy constraints do the work of guardrails
Four of the twelve checks rest on organization policy constraints: iam.disableServiceAccountKeyCreation, compute.vmExternalIpAccess, storage.publicAccessPrevention and iam.allowedPolicyMemberDomains. Enforcing a constraint at the organization node covers every project below it, so check there before you check projects one by one.
The long-lived keys check is one case. Google Cloud documentation says to choose a more secure alternative for authentication and to avoid user-managed service account keys, and the workload identity check asks whether you got there (Google Cloud documentation, read 16 Nov 2026).
Basic roles changed in October 2026
Google Cloud IAM release notes of 29 October 2026 say the Admin, Writer and Reader basic roles are generally available and that the legacy Owner, Editor and Viewer roles remain available and maintained. Google recommends granting the new roles instead, because they support IAM Conditions (Google Cloud release notes, read 16 Nov 2026).
For the administrator roles check, count both the legacy and the new basic roles.
Security Command Center and the recommender supply evidence
Google describes Security Command Center as a cloud-based risk management solution with Standard, Premium and Enterprise tiers, and its pricing page lists Standard as free of charge (Google Cloud documentation, read 16 Nov 2026). Role recommendations from the IAM recommender identify excess permissions, which feeds access reviews.
The options page lists both beside the AWS and Azure tools.
VPC Service Controls is the data perimeter check
The trusted network condition check asks whether sensitive projects sit inside a perimeter in enforced mode. A perimeter in dry run mode logs violations but blocks nothing, so it fails the check until it is enforced.
Related pages
Sources
- Google Cloud security best practices, read 16 Nov 2026
- IAM release notes, read 16 Nov 2026
- Security Command Center overview, read 16 Nov 2026
- Security Command Center pricing, read 16 Nov 2026
- Best practices for managing service account keys, read 16 Nov 2026
- Role recommendations overview, read 16 Nov 2026
Last reviewed 16 Nov 2026.