> 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/kubernetes-rbac-enumeration.md).

# Kubernetes RBAC enumeration

### Synopsis

| Field                | Value                                                                                                                            |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                                                          |
| Training Period      | 30 Days                                                                                                                          |
| Test Period          | N/A (single event)                                                                                                               |
| Deduplication Period | 1 Day                                                                                                                            |
| Required Data        | <p>Requires one of the following data sources:<br>AWS Audit Log OR Azure Audit Log OR Gcp Audit Log OR Kubernetes Audit Logs</p> |
| Detection Modules    | Cloud                                                                                                                            |
| Detector Tags        | Kubernetes - API                                                                                                                 |
| ATT\&CK Tactic       | Discovery (TA0007)                                                                                                               |
| ATT\&CK Technique    | Permission Groups Discovery (T1069), Permission Groups Discovery: Cloud Groups (T1069.003)                                       |
| Severity             | Informational                                                                                                                    |

### Description

An identity read Kubernetes RBAC objects for the first time.

### Attacker's Goals

* Map the permissions granted in the cluster to plan privilege escalation or lateral movement.
* Identify over-permissive roles that can be bound to a controlled service account.

### Investigative actions

* Check whether {identity\_name} is expected to read RBAC roles and bindings.
* The event was originated from {caller\_ip} using {user\_agent} - verify the source is a known administrative tool.
* Review whether the identity subsequently created, patched or deleted any role or binding.
* Review other operations performed by the identity in the cluster around the same time.

### Variations

<details>

<summary>Kubernetes RBAC enumeration by an unfamiliar client that also modifies RBAC</summary>

**Synopsis**

| Field             | Value                                                                                      |
| ----------------- | ------------------------------------------------------------------------------------------ |
| ATT\&CK Tactic    | Discovery (TA0007)                                                                         |
| ATT\&CK Technique | Permission Groups Discovery (T1069), Permission Groups Discovery: Cloud Groups (T1069.003) |
| Severity          | Medium                                                                                     |

**Description**

An identity read Kubernetes RBAC objects for the first time.

**Attacker's Goals**

* Map the permissions granted in the cluster to plan privilege escalation or lateral movement.
* Identify over-permissive roles that can be bound to a controlled service account.

**Investigative actions**

* Check whether {identity\_name} is expected to read RBAC roles and bindings.
* The event was originated from {caller\_ip} using {user\_agent} - verify the source is a known administrative tool.
* Review whether the identity subsequently created, patched or deleted any role or binding.
* Review other operations performed by the identity in the cluster around the same time.

</details>

<details>

<summary>Kubernetes RBAC enumeration by an unfamiliar client</summary>

**Synopsis**

| Field             | Value                                                                                      |
| ----------------- | ------------------------------------------------------------------------------------------ |
| ATT\&CK Tactic    | Discovery (TA0007)                                                                         |
| ATT\&CK Technique | Permission Groups Discovery (T1069), Permission Groups Discovery: Cloud Groups (T1069.003) |
| Severity          | Low                                                                                        |

**Description**

An identity read Kubernetes RBAC objects for the first time.

**Attacker's Goals**

* Map the permissions granted in the cluster to plan privilege escalation or lateral movement.
* Identify over-permissive roles that can be bound to a controlled service account.

**Investigative actions**

* Check whether {identity\_name} is expected to read RBAC roles and bindings.
* The event was originated from {caller\_ip} using {user\_agent} - verify the source is a known administrative tool.
* Review whether the identity subsequently created, patched or deleted any role or binding.
* Review other operations performed by the identity in the cluster around the same time.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/kubernetes-rbac-enumeration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
