Jenkins Maven project
Create a Maven project that builds a Docker image and then scans it for vulnerability and compliance issues.
- Go to the Jenkins top page.
- Click Manage Jenkins.
- Select Global Tool Configuration.
- Scroll down to the Maven section (Not Maven Configuration), and click Add Maven.
Setting up a Maven project for container images
Set up a Jenkins Maven project.
- Go to the Jenkins top page.
- Create a new project.
- ClickNew Item.
- InItemname, enter a name for your project.
- SelectMaven project.
- Add a build step.
- Scroll down to thePre stepssection.
- In theAdd pre-build stepdrop-down list, selectExecute shell.
- In theCommandtext box, enter the following:echo "Creating Dockerfile..." echo "FROM imiell/bad-dockerfile:latest" > Dockerfile echo 'docker build --no-cache -t test/test-image:0.1 .' > build_image.sh chmod +x build_image.sh echo "Creating POM file..." cat > pom.xml << EOF <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>groupId</groupId> <artifactId>artifactid</artifactId> <version>1.0-SNAPSHOT</version> <packaging>jar</packaging> <name>projectName</name> <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> </properties> <build> <plugins> <plugin> <artifactId>exec-maven-plugin</artifactId> <groupId>org.codehaus.mojo</groupId> <executions> <execution> <id>Build Image</id> <phase>generate-sources</phase> <goals> <goal>exec</goal> </goals> <configuration> <executable>build_image.sh</executable> </configuration> </execution> </executions> </plugin> </plugins> </build> </project> EOF
- Add a build step that scans the container image(s) for vulnerabilities.
- In theAdd build stepdrop-down list, selectScan Prisma Cloud Images.
- In theImagefield, select the image to scan by specifying the repository and tag.Use pattern matching expressions. For example, enter test/test-image*.If the image you want to scan is created outside of this build, or if you want to scan the image every build, even if the build might not generate an new image, then clickAdvanced, and selectIgnore image creation time.
- Add a post-build action so that image scan results in Jenkins directly.This post-build step depends on a file generated by the previous scan build step, which holds the scan results. This step specifically makes the results available for review in the Jenkins build tool. Note that the previous scan step already published the results in Console, and they’re ready to be reviewed there.
- Scroll down toPost-build Actions.
- In theAdd post-build actiondrop-down menu, selectPublish Prisma Cloud analysis results.
- In theScan Result Filesfield, accept the default.Scan result files aren’t deleted by the publish step. They stay in the workspace.
- ClickBuild Now.
- After the build completes, examine the results. Scan reports are available in the following locations:
- Prisma Cloud Console: Log into Console, and go toMonitor > Vulnerabilities > Images > CI.
- Jenkins: Drill down into the build job, then clickImage Vulnerabilitiesto see a detailed report.
Setting up a Maven project for serverless functions
The procedure for setting up Jenkins to scan serverless functions is similar to the procedure for container images, except you should use the
Scan Prisma Cloud Functionsbuild step.
- Function Path— Path to the ZIP archive of the function to scan.
- Function Name— (Optional) String identifier for matching policy rules in Console with the functions being scanned. When creating policy rules in Console, you can target specific rules to specific functions by function name. If this field is left unspecified, the plugin matches the function to the first rule where the function name is a wildcard.
- AWS CloudFormation template file— (Optional) Path to CloudFormation template file in either JSON or YAML format. Prisma Cloud scans the function source code for AWS service APIs being used, compares the APIs being used to the function permissions, and reports when functions have permissions for APIs they don’t need.
After a build completes, you can view the scan reports in the following locations:
- Prisma Cloud Console: Log into Console, and go toMonitor > Vulnerabilities > Functions > CI.
- Jenkins: Drill down into the build job, then clickVulnerabilitiesto see a detailed report.