> 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/a-kubernetes-cluster-role-was-created.md).
# A Kubernetes cluster role was created
### Synopsis
| Field | Value |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
AWS Audit Log OR Azure Audit Log OR Gcp Audit Log OR Kubernetes Audit Logs
|
| Detection Modules | Cloud |
| Detector Tags | Kubernetes - API |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation: Additional Container Cluster Roles (T1098.006) |
| Severity | Informational |
### Description
A Kubernetes cluster role was created.
### Attacker's Goals
* Create overpermissive cluster roles to escalate privileges within the Kubernetes cluster.
### Investigative actions
* Check the permissions granted to the newly created Kubernetes cluster role.
* Check whether this cluster role was bound to an identity via a ClusterRoleBinding or RoleBinding.
* Verify whether the identity that created the cluster role is authorized to perform RBAC operations.
* Review subsequent API calls made by the same identity for signs of privilege escalation or lateral movement.
### Variations
Administrative Kubernetes cluster role was created for the first time
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation: Additional Container Cluster Roles (T1098.006) |
| Severity | Medium |
**Description**
A Kubernetes cluster role with administrative permissions was created for the first time by the identity.
**Attacker's Goals**
* Create overpermissive cluster roles to escalate privileges within the Kubernetes cluster.
**Investigative actions**
* Check the permissions granted to the newly created Kubernetes cluster role.
* Check whether this cluster role was bound to an identity via a ClusterRoleBinding or RoleBinding.
* Verify whether the identity that created the cluster role is authorized to perform RBAC operations.
* Review subsequent API calls made by the same identity for signs of privilege escalation or lateral movement.
A Kubernetes cluster role with administrative permissions was created
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation: Additional Container Cluster Roles (T1098.006) |
| Severity | Low |
**Description**
A Kubernetes cluster role with administrative permissions was created.
**Attacker's Goals**
* Create overpermissive cluster roles to escalate privileges within the Kubernetes cluster.
**Investigative actions**
* Check the permissions granted to the newly created Kubernetes cluster role.
* Check whether this cluster role was bound to an identity via a ClusterRoleBinding or RoleBinding.
* Verify whether the identity that created the cluster role is authorized to perform RBAC operations.
* Review subsequent API calls made by the same identity for signs of privilege escalation or lateral movement.
A Kubernetes cluster role was created for the first time by the identity
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation: Additional Container Cluster Roles (T1098.006) |
| Severity | Low |
**Description**
A Kubernetes cluster role was created for the first time by the identity.
**Attacker's Goals**
* Create overpermissive cluster roles to escalate privileges within the Kubernetes cluster.
**Investigative actions**
* Check the permissions granted to the newly created Kubernetes cluster role.
* Check whether this cluster role was bound to an identity via a ClusterRoleBinding or RoleBinding.
* Verify whether the identity that created the cluster role is authorized to perform RBAC operations.
* Review subsequent API calls made by the same identity for signs of privilege escalation or lateral movement.
---
# 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/a-kubernetes-cluster-role-was-created.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.