> 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/appsec-rules/secrets-security/appsec-secret-384.md).

# Elasticsearch API Key detected in code

## Rule Details

|                       |                     |
| --------------------- | ------------------- |
| Cortex AppSec Rule ID | APPSEC\_SECRET\_384 |
| Category              | API Keys            |
| Severity              | HIGH                |
| Framework             | Git                 |

## Impact

An Elasticsearch / Elastic Cloud API key in its encoded form (base64 of id:api\_key) is used in the Authorization ApiKey header to authenticate to an Elasticsearch cluster. Exposure allows an attacker to read, write, or delete indices and documents and to perform any cluster operation permitted by the key's role descriptors, leading to data exfiltration, tampering, or service disruption.

## How to Fix

Invalidate the exposed API key via the Elasticsearch Security API (DELETE \_security/api\_key) or Kibana Stack Management. Generate a new least-privilege key, distribute it via a secrets manager, and purge the leaked value from git history.


---

# 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/appsec-rules/secrets-security/appsec-secret-384.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.