Integrate CI tools

By integrating CI tools, you get two main benefits: code scans and streamlined security workflows. This is achieved by inserting code snippets directly into your existing CI workflows, which then use the Cortex CLI to trigger automated security checks:

• Code scans:

  • Code scanning for IaC (Infrastructure as Code): Finds misconfigurations in your IaC files, ensuring your cloud and infrastructure environments are secure from the start
  • Software Composition Analysis (SCA) scans: Identify vulnerabilities in open-source libraries and third-party components, along with license misconfigurations and package operational risks
  • Secrets detection: Finds hardcoded secrets, such as API keys and passwords, in your code and pipelines to prevent unauthorized access and data breaches
• Streamlined workflows: By integrating security scans directly into your CI/CD pipelines, you achieve a shift-left security model, moving security from a final check to an early, continuous process within the development lifecycle.

  • Early threat detection: You can identify and fix security threats as soon as they are introduced
  • Automated and seamless integration: The use of code snippets and a unified CLI makes the security checks a seamless part of your existing CI process, requiring no manual intervention

You can integrate your CI tools and systems through the platform wizard or by directly adding a code snippet to your pipelines in supported systems.

Supported CI tools

Cortex Cloud Application Security supports the following CI tools for onboarding via the UI wizard:

• AWS CodeBuild
• CircleCI for code scans (For CircleCI CI/CD pipeline scans, refer to CI/CD)
• Cortex CLI. For information about using the Cortex CLI, refer to Cortex CLI
• GitHub Actions
• Jenkins for code scans (For Jenkins CI/CD pipeline scans, refer to CI/CD)
• Terraform Cloud (Run Tasks)
• Terraform Enterprise (Run Tasks)

You can also integrate CI scans by adding snippets to your pipeline. See CLI pipeline code snippets.

Manage CI tools

Instance-level actions

1. Navigate to Settings → Data Sources & Integrations and search for the CI tool.
2. Select the matching result.
3. Locate your instance from the displayed list. Right-click it, then select an option:

   • Edit instance: Opens the onboarding wizard, where you can change the instance configuration.
   • Delete instance: Deletes the instance and previous scan data.
   • Copy entire row: Copies all row values to the clipboard.

Repository-level actions

Right-click a connected repository to Set Scanned Branches, run a manual scan through Scan Repository, modify the Scan Configuration, or Remove Repository. In Scan Configuration, you can toggle scanners and manage pull request behavior.

1. Locate your instance. See Instance-level actions.
2. Select the instance. A list of connected repositories appears.
3. Right-click a repository, select the required action, then select Save.