GCP Vertex AI Role Granted to Principal
Description
Identifies an IAM policy change on a Google Cloud project, folder, or organization that grants a Vertex AI role
(roles/aiplatform.*) to a principal. Vertex AI roles control who can invoke models, deploy endpoints, run agents, and
read prompt and training data. An adversary who has gained IAM administration rights can grant a Vertex AI role to an
identity they control to keep model access after the original foothold is removed, or to run LLMjacking workloads under
the victim's billing. Google-managed service agent roles are excluded because Google grants them automatically when the
API is enabled.
Query · kuery
data_stream.dataset: "gcp.audit"
and event.action: (
"SetIamPolicy" or
google.cloud.resourcemanager.v*.Folders.SetIamPolicy or
google.cloud.resourcemanager.v*.Organizations.SetIamPolicy or
google.cloud.resourcemanager.v*.Projects.SetIamPolicy
)
and not event.outcome: "failure"
and gcp.audit.service_data.policy_delta.binding_deltas:{
action: "ADD" and
role: (roles/aiplatform.* and not (*ServiceAgent or *serviceAgent))
}
Investigation fields
Pivot points the source recommends for triage.
@timestampclient.user.emailevent.actiongcp.audit.resource_namegcp.audit.service_data.policy_delta.binding_deltas.actiongcp.audit.service_data.policy_delta.binding_deltas.rolegcp.audit.service_data.policy_delta.binding_deltas.membersource.ipuser_agent.original
Implementation guide
This rule requires Google Cloud Audit Logs ingested via the GCP integration (gcp.audit data stream). IAM policy
changes are Admin Activity audit logs and are always logged.
Known false positives
- Platform or ML engineering teams granting Vertex AI access to new users and service accounts. Confirm the grant against change records or the access request process.
- Infrastructure-as-code pipelines that manage project IAM bindings. Add exceptions for the service accounts that run these pipelines.
Analyst notes
Investigating GCP Vertex AI Role Granted to Principal
A Google Cloud IAM policy change added a binding for a Vertex AI role (roles/aiplatform.*). Roles such as
roles/aiplatform.admin and roles/aiplatform.user allow the member to call models, manage endpoints and agents, and
access prompt and training data in the project.
Possible investigation steps
- Identify the caller that changed the policy from
client.user.email, and reviewsource.ipanduser_agent.originalfor the change. - Review
gcp.audit.service_data.policy_delta.binding_deltasfor the role and member that were added. Members outside the organization's domain, newly created service accounts, andallUsersorallAuthenticatedUsersare the most concerning. - Check
gcp.audit.resource_nameto see whether the grant was made at the project, folder, or organization level. Grants above the project level reach every project underneath. - Look for follow-on activity by the new member in Vertex AI audit logs, such as inference calls from new networks, endpoint deployment, or agent creation.
- Review other recent IAM changes by the same caller, especially service account key creation and grants of IAM admin roles.
False positive analysis
- Approved access requests for ML and data science teams. Confirm with the request owner.
- IAM automation that reapplies bindings. Exclude those service accounts by email.
Response and remediation
- If the grant is not authorized, remove the binding and review what the member accessed since the grant.
- Investigate how the caller obtained IAM administration rights, rotate its credentials, and review its other changes.
- Restrict
resourcemanager.projects.setIamPolicyto a small set of administrators and consider an Organization Policy that limits allowed member domains.