Managing CI policy

Semgrep App provides infrastructure for managing Semgrep across many projects. Gather related rules together in "policies" and apply those policies to projects in a many-to-many mapping. A policy is simply a collection of rules, and a definition of what to do with their results: send notifications to third-party services like Slack, post inline pull request comments on GitHub, and/or block the build by returning a non-zero status.

Policy to notify when results are found but not block the CI build

Creating a policy

To create a policy, visit Dashboard > Policies and select “Create New Policy.” To copy the contents of one policy into another, navigate to the existing policy, click "Copy", and then enter the name of the new policy when prompted.

Policies are often broken down by problem area (e.g., xss), application type (e.g., prod-python-backend), or blocking status (e.g., notify-only). There is no right way to group rules, and what makes the most sense will vary by team and organization.

Editing a policy

Any rule, ruleset, or pattern can be added to a policy. Look for the “Add to Policy” button when exploring pre-written rules and rulesets or customize your policies even further by adding rules you write yourself in the online playground.

A ruleset with an "Add to Policy" button visible

You can remove items from your policy by clicking the red x. To disable individual rules within a ruleset, click the right-caret under a ruleset and then select add a disabled rule.

Policy with disabled rules showing

Changing policy actions

Third-party notifications, posting inline pull request comments, and blocking the build are all configured on a per-policy basis.

  1. Visit Dashboard > Integrations to configure the services and name each of your integration channels. See Integrations for detailed instructions.
  2. From Dashboard > Policies, select the policy you’d like to configure and add one or more integration channels from the Integrations drop-down menu.

You can also check or uncheck the boxes to post pull request comments (which requires a GitHub Token) or to block the build on findings. Don't forget to click Save when you are finished editing!

Changing the integrations and actions of a policy

If you wish to take different actions for rules on the same project, create two different policies, and then attach both policies to the project in question on Dashboard > Projects.

Downloading a policy

To locally test and run a policy, select your policy at Dashboard > Policies and use the “Download YAML” button. This YAML file can then be run locally via:

semgrep --config <path/to/yaml> <path/to/code>


See Getting started for instructions on downloading and running Semgrep locally.