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

# Identity Access Management

| Rule Name                                                                                                                                                    | AppSec Rule ID    | Severity |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------- | -------- |
| [2FA is not enforced in SCM](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-1.md)                                                       | APPSEC\_CICD\_1   | HIGH     |
| [Unrotated deploy keys](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-6.md)                                                            | APPSEC\_CICD\_6   | LOW      |
| [Unrotated GitLab deploy keys](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-7.md)                                                     | APPSEC\_CICD\_7   | LOW      |
| [Unrotated access keys detected](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-8.md)                                                   | APPSEC\_CICD\_8   | LOW      |
| [Inactive SCM user accounts](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-16.md)                                                      | APPSEC\_CICD\_16  | MEDIUM   |
| [Jenkins provides full access to anonymous visitors](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-17.md)                              | APPSEC\_CICD\_17  | CRITICAL |
| [Jenkins provides full access to authenticated user accounts](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-18.md)                     | APPSEC\_CICD\_18  | HIGH     |
| [User account is missing 2FA](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-22.md)                                                     | APPSEC\_CICD\_22  | HIGH     |
| [Permissive organization base permissions](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-29.md)                                        | APPSEC\_CICD\_29  | LOW      |
| [Outside collaborators have admin access to a repository](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-35.md)                         | APPSEC\_CICD\_35  | HIGH     |
| [Deploy key has a weak SSH signature](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-36.md)                                             | APPSEC\_CICD\_36  | LOW      |
| [Weak authentication service in use](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-49.md)                                              | APPSEC\_CICD\_49  | MEDIUM   |
| [Jenkins provides read access to anonymous visitors](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-50.md)                              | APPSEC\_CICD\_50  | MEDIUM   |
| [No authentication is configured](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-51.md)                                                 | APPSEC\_CICD\_51  | HIGH     |
| [Access key with a weak SSH signature was detected in SCM](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-70.md)                        | APPSEC\_CICD\_70  | LOW      |
| [Excessive user permissions to a repository](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-89.md)                                      | APPSEC\_CICD\_89  | HIGH     |
| [Excessive user permissions to a project](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-95.md)                                         | APPSEC\_CICD\_95  | HIGH     |
| [Excessive user permissions to a BitBucket repository](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-96.md)                            | APPSEC\_CICD\_96  | HIGH     |
| [User account credentials (access token and/or SSH Keys) are inactive in GitHub](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-105.md) | APPSEC\_CICD\_105 | HIGH     |
| [Any organization member can create internal repositories](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-184.md)                       | APPSEC\_CICD\_184 | LOW      |
| [Any organization member can create private repositories](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-185.md)                        | APPSEC\_CICD\_185 | LOW      |
| [Default branch does not require signed commits](/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-206.md)                                 | APPSEC\_CICD\_206 | LOW      |


---

# 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/identity-access-management.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.