For more information about advanced options, see here.
Add a post-build action to publish the 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 to
Add post-build action
drop-down menu, select
Publish Prisma Cloud analysis results
Scan Result Files
, accept the default.
Scan result files aren’t deleted by the publish step.
They stay in the workspace.
After the build completes, examine the results.
Scan reports are available in the following locations:
Prisma Cloud Console:
Log into Console, and go to
Monitor > Vulnerabilities > Images > CI
Drill down into the build job, then click
to see a detailed report.
Setting up a Freestyle 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 Functions
— Path to the ZIP archive of the function to scan.
— (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.