How the attack works
In Google Cloud, a project inherits allow policies, deny policies and organization policies from the folders above it and from the organization. Most guardrails are set there and not on the project. Moving a project, or a folder with everything in it, changes that parent. Google documents the effect plainly. Roles granted directly on the project move with it, roles inherited from the source folder or organization are lost, and the organization policy constraints of the source are replaced by those of the destination. Google calls this out as a change of security posture at the moment of the move.
An attacker with the right to move resources uses this to take a project out from under its controls without touching any of them. Moved into a folder with weaker policies, the project is no longer bound by a key creation ban or a domain restriction that was set higher up. Moved to an organization the attacker controls, it leaves the owner's administrators behind as well, since their inherited roles do not follow. A move between organizations is restricted by default and needs the constraints resourcemanager.allowedExportDestinations and resourcemanager.allowedImportSources to allow it, so that variant is preceded by organization policy changes. A project that belongs to no organization needs only the import policy on the destination side. Resource Manager records moves as Admin Activity audit entries, which are always written.
What an attacker needs
- For a project, the Project Mover role (
resourcemanager.projects.move) on the source and the destination parent, andresourcemanager.projects.updateon the project. For a folder,resourcemanager.folders.moveon the source and the destination. - For a move to another organization, the Project IAM Admin role on the project, the Project Creator role on the destination organization, and organization policies on both sides that allow the export and the import, which Google says are restricted by default.
- A destination folder or organization with weaker policies, or one that the attacker controls.
Impact
The project or folder is governed by the policies of its new parent. Inherited role bindings of administrators and security teams are lost, organization policy constraints set at the old parent stop applying, and deny policies attached higher up no longer reach it. The resources keep running under the same project ID and number, so nothing looks broken. After a move to another organization the previous owner has only the roles that were granted directly on the project.
Detection rules
Google Cloud Folder Moved Under Another Parent
Detects a folder being moved under another folder or under the organization (Admin Activity audit log, always written). Every project and folder below it moves with it and inherits the allow policies, deny policies and organization policies of the new parent in place of the old ones. Google's audit logging page lists the operations as cloudresourcemanager.v3.folders.move, v2.folders.move and v2beta1.folders.move, and its API reference names the method MoveFolder. Google publishes no example of the entry, and its example entries for other Resource Manager calls show a short method name, so the rule accepts either ending. The folder is named in protoPayload.resourceName and the request names the new parent in destinationParent.
title: Google Cloud Folder Moved Under Another Parent
id: 22812447-e3bc-4467-81d5-a0b9feb0ecb3
status: experimental
description: >-
Detects a folder being moved under another folder or under the
organization (Admin Activity audit log, always written). Every project and
folder below it moves with it and inherits the allow policies, deny
policies and organization policies of the new parent in place of the old
ones. Google's audit logging page lists the operations as
cloudresourcemanager.v3.folders.move, v2.folders.move and
v2beta1.folders.move, and its API reference names the method MoveFolder.
Google publishes no example of the entry, and its example entries for
other Resource Manager calls show a short method name, so the rule accepts
either ending. The folder is named in protoPayload.resourceName and the
request names the new parent in destinationParent.
references:
- https://docs.cloud.google.com/resource-manager/docs/audit-logging
- https://docs.cloud.google.com/resource-manager/reference/rest/v3/folders/move
- https://docs.cloud.google.com/resource-manager/docs/manage-folders
- https://docs.cloud.google.com/python/docs/reference/cloudresourcemanager/latest/google.cloud.resourcemanager_v3.services.folders.FoldersClient
author: Forestall
date: 2026-11-18
tags:
- attack.defense-impairment
- attack.t1666
logsource:
product: gcp
service: gcp.audit
detection:
selection:
protoPayload.serviceName: cloudresourcemanager.googleapis.com
protoPayload.methodName|endswith:
- folders.move
- MoveFolder
condition: selection
falsepositives:
- Planned reorganizations of the folder structure by the platform team. Folder moves are rare. Confirm each one against a change record.
level: medium
False positives
- Planned reorganizations of the folder structure by the platform team. Folder moves are rare. Confirm each one against a change record.
Google Cloud Project Moved to Another Folder or Organization
Detects a project being moved to a new parent through the Resource Manager v3 API (Admin Activity audit log, always written). After the move the project is governed by the policies of the new parent, and Google documents that inherited roles are lost and that the organization policy constraints of the source are replaced by those of the destination. Google's audit logging page lists the operation as cloudresourcemanager.v3.projects.move and its API reference names the method MoveProject. Google publishes no example of the entry, and its example entries for other Resource Manager calls show a short method name, so the rule accepts either ending. The project is named in protoPayload.resourceName and the request names the new parent in destinationParent. The same project can also be given a parent through the v1 API, which has a rule of its own on this page.
title: Google Cloud Project Moved to Another Folder or Organization
id: c0ece608-58ea-45a1-8f97-db52b3295d18
status: experimental
description: >-
Detects a project being moved to a new parent through the Resource Manager
v3 API (Admin Activity audit log, always written). After the move the
project is governed by the policies of the new parent, and Google documents
that inherited roles are lost and that the organization policy constraints
of the source are replaced by those of the destination. Google's audit
logging page lists the operation as cloudresourcemanager.v3.projects.move
and its API reference names the method MoveProject. Google publishes no
example of the entry, and its example entries for other Resource Manager
calls show a short method name, so the rule accepts either ending. The
project is named in protoPayload.resourceName and the request names the new
parent in destinationParent. The same project can also be given a parent
through the v1 API, which has a rule of its own on this page.
references:
- https://docs.cloud.google.com/resource-manager/docs/audit-logging
- https://docs.cloud.google.com/resource-manager/reference/rest/v3/projects/move
- https://docs.cloud.google.com/resource-manager/docs/project-migration
- https://docs.cloud.google.com/python/docs/reference/cloudresourcemanager/latest/google.cloud.resourcemanager_v3.services.projects.ProjectsClient
author: Forestall
date: 2026-11-18
tags:
- attack.defense-impairment
- attack.t1666
logsource:
product: gcp
service: gcp.audit
detection:
selection:
protoPayload.serviceName: cloudresourcemanager.googleapis.com
protoPayload.methodName|endswith:
- projects.move
- MoveProject
condition: selection
falsepositives:
- Planned reorganizations of the folder structure and migrations between organizations by the platform team. Moves are rare. Confirm each one against a change record and exclude the migration identity by principalEmail only for the duration of the migration.
level: medium
False positives
- Planned reorganizations of the folder structure and migrations between organizations by the platform team. Moves are rare. Confirm each one against a change record and exclude the migration identity by principalEmail only for the duration of the migration.
Google Cloud Project Updated Through the Resource Manager v1 API
Detects projects.update calls to the Resource Manager v1 and v1beta1 APIs (Admin Activity audit log, always written). Google's v1 reference states that the parent of a project can be set with the projects.update method, so this call is a second way to place a project under a folder or an organization, next to the v3 move method. The same call also changes the name and the labels of a project. Google documents the operation name and the log type but not which request fields the entry keeps, so the rule matches on the event alone and cannot tell a parent change from a label change. Its level is low for that reason. The rule uses the operation names as Google lists them. Check them against one of your own entries, because Google's example entries for other Resource Manager calls show shorter method names. Compare the parent of the project named in protoPayload.resourceName before and after the call. The v3 update method, which Google documents as unable to change the parent, is not matched.
title: Google Cloud Project Updated Through the Resource Manager v1 API
id: 16fac2c7-df3f-4c4b-878e-b046e245f3de
status: experimental
description: >-
Detects projects.update calls to the Resource Manager v1 and v1beta1 APIs
(Admin Activity audit log, always written). Google's v1 reference states
that the parent of a project can be set with the projects.update method,
so this call is a second way to place a project under a folder or an
organization, next to the v3 move method. The same call also changes the
name and the labels of a project. Google documents the operation name and
the log type but not which request fields the entry keeps, so the rule
matches on the event alone and cannot tell a parent change from a label
change. Its level is low for that reason. The rule uses the operation
names as Google lists them. Check them against one of your own entries,
because Google's example entries for other Resource Manager calls show
shorter method names. Compare the parent of the
project named in protoPayload.resourceName before and after the call. The
v3 update method, which Google documents as unable to change the parent,
is not matched.
references:
- https://docs.cloud.google.com/resource-manager/docs/audit-logging
- https://docs.cloud.google.com/resource-manager/reference/rest/v1/projects
- https://docs.cloud.google.com/resource-manager/reference/rest/v1/projects/update
- https://docs.cloud.google.com/python/docs/reference/cloudresourcemanager/latest/google.cloud.resourcemanager_v3.services.projects.ProjectsClient
author: Forestall
date: 2026-11-18
tags:
- attack.defense-impairment
- attack.t1666
logsource:
product: gcp
service: gcp.audit
detection:
selection:
protoPayload.serviceName: cloudresourcemanager.googleapis.com
protoPayload.methodName:
- cloudresourcemanager.v1.projects.update
- cloudresourcemanager.v1beta1.projects.update
condition: selection
falsepositives:
- Label and display name changes by tools that still use the v1 API, including infrastructure-as-code runs. Exclude those identities by principalEmail in a filter_* selection and review updates by people.
level: low
False positives
- Label and display name changes by tools that still use the v1 API, including infrastructure-as-code runs. Exclude those identities by principalEmail in a filter_* selection and review updates by people.
Detection logic
Patterns that need more than one event, a baseline or knowledge of your own environment. Each is a hypothesis to build and tune in your SIEM, not a ready rule.
Project moved shortly after the migration constraints were changed
A move to another organization needs two organization policies that are restricted by default. An attacker who wants a project out of the organization has to set the export constraint first. A constraint change followed by a project move is the two halves of that path.
- An organization policy change from
orgpolicy.googleapis.com, methodgoogle.cloud.orgpolicy.v2.OrgPolicy.CreatePolicyorUpdatePolicy, whoseprotoPayload.request.policy.namecontainsresourcemanager.allowedExportDestinationsorresourcemanager.allowedImportSources. - Within 7 days a project move entry from
cloudresourcemanager.googleapis.com, the event of the project rule on this page. - Compare the callers of the two entries and check the destination of the move against the organizations your company owns.
Eventsgoogle.cloud.orgpolicy.v2.OrgPolicy.CreatePolicygoogle.cloud.orgpolicy.v2.OrgPolicy.UpdatePolicycloudresourcemanager.v3.projects.move
LimitsA planned migration produces the same two entries, in the same order, so the change record decides. A move between folders of one organization needs no constraint change and is not seen by the first step. The 7 days are a starting point.
Triage
- Identify the caller (protoPayload.authenticationInfo.principalEmail) and the project or folder in protoPayload.resourceName, and find the destination. The move request names it in
destinationParent, and the resource's current ancestry shows where it is now. - Check whether a planned reorganization or migration covers the move. Moves are rare and are normally announced.
- Compare the organization policies, deny policies and inherited role bindings of the old and the new parent. Note which constraints no longer apply.
- Look for organization policy changes to
resourcemanager.allowedExportDestinationsorresourcemanager.allowedImportSources, and for grants of the Project Mover role, in the days before the move. - Review what happened in the project after the move, starting with service account keys, allow policy changes and public access, which the old constraints may have blocked.
Response
Once the attack is confirmed:
- Move the project or folder back to its original parent. Google documents that a migration between organizations is not rolled back automatically and has to be reversed by hand, by swapping source and destination in the two constraints.
- Remove the Project Mover, Folder Mover and Organization Policy Administrator roles from the caller, and contain that identity.
- Review everything that was done in the project while it was outside its controls, and remove keys, role bindings and resources that the old policies would have blocked.
- Remove the
resourcemanager.allowedExportDestinationsandresourcemanager.allowedImportSourcespolicies again if they were set for the move. - Confirm that the inherited roles and organization policies apply again, and that log exports and monitoring still cover the project.
Mitigation
- Grant the Project Mover and Folder Mover roles only for the duration of a planned move, on dedicated folders, and remove them afterwards, as Google's migration guidance describes.
- Leave the organization policy constraints
resourcemanager.allowedExportDestinationsandresourcemanager.allowedImportSourcesunset outside a planned migration. Google documents that project migration between organizations is restricted by default. - Restrict the Organization Policy Administrator role, since changing those two constraints is what opens a move to another organization.
- Set the security-critical policies of sensitive projects directly on the project as well, so that they move with it.
- Create projects inside the organization. Google documents that a project without an organization can be moved into an organization with only the destination's policy and the caller's roles on the project and the destination.
Frequently asked questions
What changes for a project when it is moved?
Google documents that the project ID and number, the data and resources, the billing account and the roles granted directly on the project stay the same. Roles inherited from the source organization or folder are lost, and the organization policy constraints of the source are replaced by those of the destination. The move is a change of the parent, not a transfer of data, so services keep running.
Can a project be moved to another organization without anyone noticing?
Not by default. Google documents that project migration between organizations is restricted, and that the source organization needs the constraint `resourcemanager.allowedExportDestinations` and the destination needs `resourcemanager.allowedImportSources`. Setting them is an organization policy change that is logged. A move between folders of the same organization needs no such policy, only the move permission on both folders.
Which spelling of the method name do the rules match?
Both documented ones. Google's Resource Manager audit logging page lists the operations as `cloudresourcemanager.v3.projects.move` and `cloudresourcemanager.v3.folders.move`, and Google's API reference names the same methods `MoveProject` and `MoveFolder`. Google's own example entries for Resource Manager show a short method name that differs from the listed operation name, so the rules accept either ending.
Has this been used in real attacks?
No public incident report describes a project move at the audit event level. The technique is in MITRE ATT&CK as Modify Cloud Resource Hierarchy, and the page follows from what Google documents about inheritance and moves. Treat the rules as a watch on a rare and powerful administrative action.
References
- MITRE ATT&CK T1666: Modify Cloud Resource Hierarchy
- Resource Manager audit logging
- Move a project
- Migrate projects between organization resources
- Perform a project migration (required roles and organization policies, rollback)
- Create a migration plan (dedicated import and export folders)
- Deny policies (deny policy inheritance)
- Manage folders (move a folder into another folder)
- Resource Manager API: projects.move
- Resource Manager API v1: projects (the parent field and projects.update)
- Resource Manager client library reference: ProjectsClient (MoveProject)