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

# Unrotated access keys detected

## Rule Details

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

## Impact

Access keys associated with projects have not been rotated for more than 180 days. An attacker who obtains such a key gains direct access to the repository, and if the key has write permissions, can modify the repository content. The longer a key remains active, the higher the risk that a leaked or compromised key could be used maliciously.

## Recommended Solution - Buildtime

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

1. Create a new private key on the server intended to use it.
2. Create a new access key using the matching public key in the same project that the current key was created on.
3. Direct the server to use the new key instead of the key in use.
4. Delete the older access key from the Bitbucket project.

There are two options for creating and deploying keys:

* Create and delete access keys using the console: Browse to the **Access Keys** tab under the repository settings.
* Create and delete deploy keys using the API. Refer to the Bitbucket API documentation: <https://docs.gitlab.com/ee/api/deploy\\_keys.html>.


---

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