Folders should be organised by environment and data sensitivity
This check looks at how projects are grouped into folders under your Google Cloud organization. The safe setting is a folder layout that separates environments such as production and development, and data of different sensitivity, so that policies and access can be set once at the folder level.
Why it matters
Google Cloud resources form a hierarchy: organization, folders, projects, then resources. IAM policies and organization policies set on a folder are inherited by everything below it. A flat list of projects forces you to repeat settings project by project, and that is where gaps appear.
Grouping by environment and sensitivity lets you give a stricter policy to the folder holding sensitive workloads and a looser one to a sandbox folder, without touching each project.
Source: Google Cloud documentation, Resource hierarchy and Creating and managing folders.
How to check it yourself
In the Google Cloud console open IAM & Admin > Manage resources and look at the tree under your organization. Ask whether production, non-production and sensitive workloads sit in separate folders, or whether most projects hang directly off the organization.
A read-only listing with gcloud (the numeric IDs below are placeholders):
gcloud resource-manager folders list --organization=123456789012
gcloud projects list --format="table(projectId,parent.id,parent.type)"Projects whose parent type is organization are not in any folder.
How to fix it
Design the layout on paper first, then move projects in small groups:
- Decide the top-level split, for example production, non-production and shared services, and add a sensitive-data folder where that applies.
- In Manage resources choose Create folder under the organization or a parent folder.
- Select a project and use Move to place it in the right folder.
- Attach IAM bindings and organization policies to the folders rather than to single projects.
A script for creating a folder and moving one project:
gcloud resource-manager folders create --display-name="production" --organization=123456789012
gcloud projects move my-project-id --folder=FOLDER_IDConfigCobra never makes these changes for you: it reports the finding and suggests the steps.
What changes when you fix it
Moving a project changes which inherited IAM bindings and organization policies apply to it. People can gain or lose access, and a policy on the new parent can start to block an action that used to work, such as creating a resource in a certain region. Check the policies on the destination folder before each move.
Project IDs and resources stay the same, so applications keep running, but the permissions of the people who administer the folders deserve a review as part of the change.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Google Cloud Platform Foundation v5.0.0 | 1.1.3 | Level 2 |
Go further
- Identity and Access Management21 controls in this section
- CIS Google Cloud Platform Foundation v5.0.093 controls
- CIS Google Cloud Platform Foundation checklistEvery control in one list, as CSV
- RemediationSee what a fix changes in your tenant before you apply it, then use the generated script
- Monitoring & DriftScheduled scans, drift detection and email alerts when a control regresses
Check this on your Google Cloud
ConfigCobra runs this check with every other control of the CIS Google Cloud Platform Foundation Benchmark, read-only.