> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/gcp-sensitive-cloud-run-role-granted.md).
# GCP sensitive Cloud Run role granted
### Synopsis
| Field | Value |
| -------------------- | -------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 5 Days |
| Required Data | Gcp Audit Log |
| Detection Modules | Cloud |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation (T1098), Account Manipulation: Additional Cloud Roles (T1098.003) |
| Severity | Informational |
### Description
A cloud identity granted itself a sensitive Cloud Run IAM role.
### Attacker's Goals
Maintain persistent access or escalate privileges within the cloud environment.
### Investigative actions
* Verify which permissions were granted to the identity.
### Variations
GCP sensitive Cloud Run role granted
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation (T1098), Account Manipulation: Additional Cloud Roles (T1098.003) |
| Severity | Medium |
**Description**
A cloud identity granted itself a sensitive Cloud Run IAM role.
**Attacker's Goals**
Maintain persistent access or escalate privileges within the cloud environment.
**Investigative actions**
* Verify which permissions were granted to the identity.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/gcp-sensitive-cloud-run-role-granted.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.