For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex CloudApplication Security

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/

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.

Last updated

Was this helpful?