> 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-19.md).

# Hex High Entropy String detected in code

## Rule Details

|                       |                       |
| --------------------- | --------------------- |
| Cortex AppSec Rule ID | APPSEC\_SECRET\_19    |
| Category              | Environment Variables |
| Severity              | LOW                   |
| Framework             | Git                   |

## Impact

A Hex High Entropy String indicates the presence of a highly random, unstructured secret (e.g., a token, API key, or password component).

Exposure is a High Risk that grants an attacker unauthenticated access to the associated system once the secret's format is identified.

## How to Fix

To remediate a generic or high-entropy secret:

1. Identify the service or resource protected by this secret (investigate variable names or surrounding code for context).
2. Log in to the identified service and rotate the credentials.
3. If the service cannot be identified, treat the secret as critical: check if it matches internal passwords or keys and rotate them as a precaution.
4. Update your application configuration with the new value.

Next, remove the secret from your codebase:

1. Locate the exposed string in your codebase.
2. Remove it or replace it with a secure variable or reference.

Finally, clean your version control history:

1. Permanently remove the sensitive data from your version control history to ensure it cannot be retrieved.


---

# 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-19.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.