> 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/potential-kubelet-impersonation-attempt.md).

# Potential kubelet impersonation attempt

### Synopsis

| Field                | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| Activation Period    | 14 Days                                                    |
| Training Period      | 30 Days                                                    |
| Test Period          | 10 Minutes                                                 |
| Deduplication Period | 1 Day                                                      |
| Required Data        | XDR Agent with eXtended Threat Hunting (XTH)               |
| Detector Tags        | Kubernetes - AGENT, Kubernetes Credentials Theft Analytics |
| ATT\&CK Tactic       | Credential Access (TA0006)                                 |
| ATT\&CK Technique    | Unsecured Credentials: Credentials In Files (T1552.001)    |
| Severity             | Low                                                        |

### Description

A process accessed both the Kubelet credentials and the Kubernetes CA certificate, indicating an attempt to impersonate the node agent and communicate with the API server.

### Attacker's Goals

Impersonate the node agent to gain control over the cluster.

### Investigative actions

* Look for additional suspicious activities.
* Verify if the exposed credentials were used to access the API server.
* Investigate which operations were used against the Kubernetes cluster with the exposed credentials.

### Variations

<details>

<summary>Potential kubelet impersonation attempt by an unusual process</summary>

**Synopsis**

| Field             | Value                                                   |
| ----------------- | ------------------------------------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006)                              |
| ATT\&CK Technique | Unsecured Credentials: Credentials In Files (T1552.001) |
| Severity          | Medium                                                  |

**Description**

A process accessed both the Kubelet credentials and the Kubernetes CA certificate, indicating an attempt to impersonate the node agent and communicate with the API server.

**Attacker's Goals**

Impersonate the node agent to gain control over the cluster.

**Investigative actions**

* Look for additional suspicious activities.
* Verify if the exposed credentials were used to access the API server.
* Investigate which operations were used against the Kubernetes cluster with the exposed credentials.

</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 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/potential-kubelet-impersonation-attempt.md?ask=<question>&goal=<endgoal>
```

`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.
