> 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/ci-cd-security/credential-hygiene/appsec-cicd-148.md).

# Secrets found in webhook URL

## Rule Details

|                       |                    |
| --------------------- | ------------------ |
| Cortex AppSec Rule ID | APPSEC\_CICD\_148  |
| Category              | Credential Hygiene |
| Severity              | HIGH               |

## Impact

Including secrets in a webhook URL comes with risks: • Apps and actors with access to the webhook URL will have access to the secret • Third party systems logging webhook URLs could gain access to the secrets included in the URL • When part of an unencrypted HTTP request, a webhook URL exposes the secret to anyone with access to the traffic such as cache servers and firewalls • Placing secrets in a webhook URL makes it more difficult to rotate them.

An attacker could use these secrets to gain unauthorized access to services that are used to authenticate the webhook against.

## Recommended Solution - Buildtime

To secure your webhook recipient’s service from unauthorized access, remove secrets from webhook URLs, and use alternative methods to authenticate against 3rd party systems.

For example, you can use a GitHub secret token in the webhook mechanism by including it in the request header. This ensures that the secret is not exposed in the URL.

For more information refer to: <https://docs.github.com/en/developers/webhooks-and-events/webhooks/securing-your-webhooks>.


---

# 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/ci-cd-security/credential-hygiene/appsec-cicd-148.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.