> 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/pipeline-based-access-controls/appsec-cicd-52.md).

# Jobs are allowed to run on the Jenkins Controller

## Rule Details

|                       |                                |
| --------------------- | ------------------------------ |
| Cortex AppSec Rule ID | APPSEC\_CICD\_52               |
| Category              | Pipeline Based Access Controls |
| Severity              | HIGH                           |

## Impact

The Jenkins instance allows jobs to run on the Jenkins Controller. The Jenkins Controller is the original node in the Jenkins installation. The Controller is responsible for administration operations on the Jenkins instance, such as job orchestration, node management, and authentication. Jenkins jobs can be run on the Jenkins Controller or on dedicated agents. Jobs are processes which can access the file system of the underlying execution environment, with the permissions of the operating system user account running the Jenkins process. Jobs that run on the Jenkins Controller can access the Controller's file system. Attackers executing a malicious build that runs on the Controller can perform impactful malicious actions on the Jenkins instance, such as getting stored credentials, managing authorization configurations, and executing jobs. Information regarding isolating the Jenkins Controller can be found in the Jenkins documentation: <https://www.jenkins.io/doc/book/security/controller-isolation/>

## Recommended Solution - Buildtime

Prevent Jenkins jobs from running on the Controller:

1. On the Jenkins instance, under **Manage Jenkins**, browse to **Configure System**.
2. Set **# of executors** to **0**.

**📌 NOTE**\
Ensure that agents that fit the builds’ needs are configured on the instance.


---

# 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/pipeline-based-access-controls/appsec-cicd-52.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.