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

# User account credentials (access token and/or SSH Keys) are inactive in GitHub

## Rule Details

|                       |                   |
| --------------------- | ----------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_105 |
| Category              | IAM               |
| Severity              | HIGH              |

## Impact

User account programmatic credentials including personal access tokens (PAT) and SSH keys authorized by SAML SSO, are inactive for more than 90 days. Although not in use, these credentials are still valid, enlarging the attack surface.

## Recommended Solution - Buildtime

Minimize potential risks by deleting user account programmatic credentials that are not in use:

* Request the users to de-authorize or delete PATs and SSH Keys that are not in use
* Admins can delete credentials through the GitHub API

### Delete Credentials

* **Delete Credentials from the GitHub web interface**
  * **SSH Keys**: In your GitHub account select **Settings** > **SSH and GPG keys** > deauthorize or delete the SSH key
  * **PAT**: In your GitHub account select **Settings** > **Developer Settings** > **Personal access tokens** > deauthorize or delete the personal access token
* **Delete Credentials using the Admin API**: Refer to the Admin API: <https://docs.github.com/en/rest/orgs/orgs#remove-a-saml-sso-authorization-for-an-organizatio◊n>


---

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