> 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/identity-access-management/appsec-cicd-6.md).

# Unrotated deploy keys

## Rule Details

|                       |                 |
| --------------------- | --------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_6 |
| Category              | IAM             |
| Severity              | LOW             |

## Impact

Deploy keys associated with code repositories have not been rotated in over 180 days. The longer a deploy key remains active, the greater the potential for it to be compromised or leaked. An attacker who obtains a deploy key gains direct access to the repository's code. If the key is assigned 'write' permissions, the attacker can also edit the code.

## Recommended Solution - Buildtime

To minimize the risk of a stolen deploy key being used by an attacker, it is recommended to rotate deploy keys within a maximum period of 180 days after creating the key.

1. Create a private key on the server that will consume the key.
2. Create a deploy key using the matching public key in the same repository the current key was created on.
3. Direct the server to use the new key.
4. Delete the old deploy key from the GitHub repository.

There are two options for creating and deploying keys:

* Through the console: browse to the **Deploy Keys** tab under the repository **Settings** and select **Add Deploy Key**.
* Through the API: refer to the GitHub API documentation: <https://docs.github.com/en/rest/reference/repos#deploy-keys>


---

# 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/ci-cd-security/identity-access-management/appsec-cicd-6.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.