Fortinet black logo

Online Help

CI/CD Integration Policy Configuration

Copy Link
Copy Doc ID cf00dcb1-0886-11ed-bb32-fa163e15d75b:83375

CI/CD Integration Policy Configuration

Jenkins integration allows Container Protection to scan and evaluate the newly generated images for vulnerability before they are deployed. If a vulnerability is found, the image will be failed and blocked from deployment.

A FortiCNP Jenkins plugin will be installed along with Kuberenetes agent to allow communication between the client side Jenkins server and Container Protection.

Port Requirement

As the FortiCNP Jenkins plugin work as a client, not a server. There is no port requirement for using the Jenkins plugin.

Prerequisite

  1. Jenkins version needs to be 2.190.1 or higher to install the FortiCNP Jenkins plugin.
  2. Kubernetes cluster needs to be setup with Container Protection and CI/CD policy needs to be configured.

Steps to Deploy Jenkins Integration

  1. Add Kubernetes Cluster
  2. Add Policy to CI/CD Integration
  3. Jenkins Configuration

CI/CD Integration Policy Configuration

Jenkins integration allows Container Protection to scan and evaluate the newly generated images for vulnerability before they are deployed. If a vulnerability is found, the image will be failed and blocked from deployment.

A FortiCNP Jenkins plugin will be installed along with Kuberenetes agent to allow communication between the client side Jenkins server and Container Protection.

Port Requirement

As the FortiCNP Jenkins plugin work as a client, not a server. There is no port requirement for using the Jenkins plugin.

Prerequisite

  1. Jenkins version needs to be 2.190.1 or higher to install the FortiCNP Jenkins plugin.
  2. Kubernetes cluster needs to be setup with Container Protection and CI/CD policy needs to be configured.

Steps to Deploy Jenkins Integration

  1. Add Kubernetes Cluster
  2. Add Policy to CI/CD Integration
  3. Jenkins Configuration