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

# Jenkins provides full access to anonymous visitors

## Rule Details

|                       |                  |
| --------------------- | ---------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_17 |
| Category              | IAM              |
| Severity              | CRITICAL         |

## Impact

Jenkins is configured to allow full access to anonymous visitors. Any visitor with network access to the system is granted with full administrative permissions, providing abilities as accessing secrets, creating, modifying and deleting pipelines, and managing user accounts. This permission model puts the system at risk, as any attacker that achieves access to the system automatically controls every part of it.

## Recommended Solution - Buildtime

Implement a secure authentication mechanism which provides security controls that meet the industry best practices, such as integrating with the organization’s SSO solution. For more on Authentication refer to <https://cheatsheetseries.owasp.org/cheatsheets/Authentication\\_Cheat\\_Sheet.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 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/appsec-cicd-17.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.