Set up the Prisma Cloud App Files for GitHub

Set Up Your Prisma Cloud Configuration File for IaC Scan.
Create the .prismaCloud/config.yml in the root directory of your repository branch. This file is required, and it must include the template type, version, and the template specific parameters and tags you use in your environment.
Create the prisma-cloud-config.yml file to support the ability to scan IaC templates.
Select
Create new file
.
Add a new folder called .github, and name the file prisma-cloud-config.yml. The path should be
<your repository name>
/.github/prisma-cloud-config.yml.

Copy the template for this new file.
Copy and paste the following contents into .github/prisma-cloud-config.yml.
# Please update with the respective environment values and commit
# to master branch under the .github folder before performing scans

# Define the failure criteria for creating checks. If the criteria 
# matches a check will be created. The template for the checks can 
# becustomized in the "/.github/prisma-template-for-scan-results" 
# file.
failure_criteria_for_creating_checks:
  high: 1
  medium: 1
  low: 1
  operator: or

# Define the failure criteria for creating issues. If the criteria 
# matches an issue will be created. The template for issues can be 
# customized in the "/.github/prisma-template-for-scan-results" 
# file.
failure_criteria_for_creating_issues:
  high: 1
  medium: 1
  low: 1
  operator: or

# Define github asset name
github_asset_name: "Github Asset Dev"

# Define tags
tags:
- phase:testing
- env:QA
Define the parameter values in prisma-cloud-config.yml.
The parameters in prisma-cloud-config.yml define the failure criteria for pull requests. You can set
failure_criteria_for_creating_checks
to define the number and severity of security policy check failures that need to occur to trigger a merge request failure. The syntax for the
failure_criteria_for_creating_checks
value is as follows.
  high: x
  medium: y
  low: z
  operator: op
In the syntax above, x is a count of high-severity policy check failure, y is a count of medium-severity policy check failures, and z is a count of low-severity policy check failures. The
operator
value determines what combination of High/Medium/Low counts should result in a merge request failure. The default for each count is 0. The value for operator, op, can be either OR or AND. The default is OR. Some examples of settings for
failure_critieria_for_creatings_checks
are as follows.
The setting below would result in a failed merge request security check for any detected policy check failure

  high: 0
  medium: 0
  low: 0
  operator: OR

The setting below would result in merge requests never failing a security check.

  high: 1000
  medium: 1000
  low: 1000
  operator: AND
You can also use failure_criteria_for_creating_issues to define the number and severity of security policy check failures that need to occur to trigger creation of a GitHub issue, during a pull request. The syntax of the variable value is the same as that for failure_criteria_for_creating_checks. The value includes
high
,
medium
, and
low
counts and includes an
operator
whose possible values are
AND
and
OR
.
Prisma Cloud uses the asset name to track results. Some example names are creditapp_server and ConsumerBU_server.
Prisma Cloud tags enable visibility on the Prisma Cloud administrator console.