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

# Encrypted Private Key detected in code

## Rule Details

|                       |                     |
| --------------------- | ------------------- |
| Cortex AppSec Rule ID | APPSEC\_SECRET\_224 |
| Category              | Encryption Keys     |
| Severity              | MEDIUM              |
| Framework             | Git                 |

## Impact

An Encrypted Private Key is a private key protected by a passphrase.

Exposure is a High Risk because the passphrase may be weak, compromised, or discoverable. If the passphrase is leaked separately, the attacker gains full authentication and decryption capabilities.

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