Fine Tune Your Configuration Settings

Edit on GitHub

Once your code repositories are integrated, you can modify your configuration to specify how Prisma Cloud scans your code. This includes:

Exclude Paths from Code Security scans

Enable Notifications

Exclude Paths from Code Security scans

Configure your code security scan by adding rules to an integrated repository. New rules are scanned only for a single defined repository. However, you can configure multiple repositories to a defined rule.

By default, Prisma Cloud scans all paths in all repositories. You can add a rule to specify which repository paths to exclude when scanning. Before you begin adding rules, disable the default configuration for all repositories.

Select Settings > Code Configuration
to configure your integrated repository.

Enable repositories to scan.

Select specific repositories From Repositories
.

Enter paths to exclude from the repository.

Type paths to exclude within the selected repository.

Use comma (,) to list more than one file or path.

In this example, On Enter Paths, type test, _test, \/test\/ this will exclude any path or file with the specified context.

Select Add Rule
to add the rule with excluded paths to your code configuration.

Select Save
to save your new rule of paths to be excluded during a code security scan.

Enable Notifications

Enable Prisma Cloud to send notifications for Code Security scan results to an external integration. Prisma Cloud Code Security supports notifications to Microsoft Teams, Slack, Splunk, JIRA, ServiceNow and Webhooks only.

Prisma Cloud Code Security sends notifications to the supported integrations for all new findings detected in periodic scans, on-demand scans triggered using Scan Now
, and CI/CD scans. This means that when you configure notifications for a repository that has already been scanned, you will not get notifications for the issues that currently exist, but you will get notifications for new issues on subsequent scans.

VCS pull request scans do not trigger notifications, because PR scans already get notifications in the PR itself in the form of comments and pipeline scans. However, when a PR gets merged and introduces new findings on the default branch, then those findings generate alerts on the next periodic scan.

By default, Notifications are disabled. See Configure External Integrations on Prisma Cloud to set up an integration. After you have set it up, you must first enable notifications, modify the default rule that scans all paths in all repositories and add new rules for your notification preferences.

Select Settings > Code Security Configuration
and enable Notifications
.

Set up your notification preferences.

Enable repositories you want to scan.