Jenkins for CI/CD pipeline scans - Administrator Guide - Cortex Cloud Posture Management - Cortex CLOUD

Cortex Cloud Runtime Security Documentation
Product
Cortex Cloud Application Security > Cortex CLOUD
License
Cloud Runtime Security
Creation date
2024-12-24
Last date published
2026-06-04
Category
Administrator Guide

Integrate Cortex Cloud Application Security CI/CD Security with your Jenkins servers to enable automated and continuous scanning of your CI/CD pipelines. This integration provides proactive security checks, triggered by pipeline events or configuration changes, ensuring security issues are detected and remediated throughout the entire deployment lifecycle.

Pipeline scans are executed using the Cortex CLI, and include automated actions based on scan results to enforce security policies and prevent vulnerable deployments.

Note

Jenkins onboarding offers both code and CI/CD scanning. A single integrated instance supports either code or CI scanning, but not both. If you require both code and CI scanning for your Jenkins servers, you must create two separate integrations, selecting the appropriate scanning type for each. To onboard Jenkins for code scans, refer to Jenkins for code scans.

Danger

Prerequisite

  • In Jenkins:

    • To install and configure the Cortex plugin in Jenkins, you must be a Jenkins Administrator with Overall/Administer permissions

    • Ensure the build server allows outbound HTTPS (Port 443 traffic to the Cortex API URL

Onboarding steps

  1. On the Cortex Cloud console:

    2. Search for and hover over Jenkins and click Add, or Add Another Instance if an instance is already onboarded.

  2. On the Select Integration step of the wizard, select CI/CD System Scan → Next.

  3. On the Create Instance step of the integration wizard: Provide a Jenkins plugin connector name → Next.

  4. On the Plugin installation step of the wizard:

    1. Click Download to download the Cortex Cloud Application Security Jenkins Cortex.Cloud.hpi plugin file.

    2. Copy and save the generated JWT token.

    3. Click Done.

      Note

      The integration is added on the console but integration is pending, and will only be completed after completing step 5 below. You can view the pending integration on the Jenkins Instances page: Select Data Sources → Jenkins → View Details. The type of integration is Pipeline Risks

  5. Install and configure the Cortex Cloud plugin on your Jenkins server:

    1. Open Jenkins and select: Manage Jenkins → Plugins (under System Configuration) → Advanced settings.

    2. Select Choose File (under the Deploy Plugin section) → browse for the Cortex.Cloud Plugin.hpi file → Upload → Deploy.

    3. Configure the plugin:

      1. Open Jenkins → Select Manage Jenkins → System (under System Configuration) → Cortex Cloud.

      2. Fill in the provided fields:

        • Cortex JWT Token: Paste the JWT token copied in step 4b above.

        • Cortex Reports Recurrence Period (Value: minutes): The frequency with which reports are generated. We recommend that you do not change the default value

      3. Click Save.

        The Cortex Cloud Application Security plugin is integrated with your Jenkins system.

  6. Verify integration and confirm that the your integrated Jenkins instance has a status of Connected.

    1. On the Data Sources & Integrations page, search for Jenkins.

    2. Hover over and select the resulting entry.

    3. Locate and verify that the status of your instance is Connected.

  7. Next step: View scan results and mitigate issues.

Note

Always refer to the official Jenkins documentation when installing plugins on Jenkins servers.

Manage data source integrations

Manage integrations to align with evolving requirements and ensure they remain current.

  1. Navigate to Settings → Data Sources & Integrations and use the Vendor filter to located the required integration.

  2. Select your vendor from the list.

    The integrated instances for the selected vendor are displayed.

  3. Right-click on an instance and select an option:

    • Edit instance: Redirects to the Select Repositories step of the integration wizard, where you can modify configurations for the selected instance. For more details, refer to the relevant integration guide

    • Delete instance: When confirmed, deletes the instance, including data from previous scans

    • Copy entire row – Copies all column values for the selected row to the clipboard.