Component policies

Use component policies to notify Organization Admins when components with specific properties are detected in a SCA test.

Component policy overview

Organization Admins and Organization Application Managers can create and manage component policies on the Policies page. Component policies are comprised of Rules and Actions.

Rules

You can add up to five rules to each component policy. Rules control what actions occur when test results violate a policy (when components with specific properties are detected in an SCA test). Set up rules to monitor tests for components with any combination of the following properties:

  • Components that are included or excluded from your SBOM.
  • Components with licenses in different license families.
  • Components that are direct or transitive dependencies.
  • Components with different security risks.
  • Components that are subject to specific licenses.
  • Components with specific names.
  • Components with specific match scores.

Actions

You can assign the following actions to each rule in a component policy:

Note: You can add any action to a rule, but actions only function as expected when the prerequisites are met, and only run after a test is complete.
Table 1. Actions and action prerequisites
Action Description Prerequisites
Send Notification Send an email notification to Organization Admins when components with specific properties are found in a test. Each email includes the names of one or more violated component policies, the violated rules in each policy, the total quantity of violating components for each rule, and helpful links. Click a component quantity to view the components that violate the rule in .
Note: Email notifications for issue and component policies are only sent to Organization Admins. One email is sent each time a test's results violate one or more policies, and each email can include components that violate more than one of each policy's rules. If a test's results violate issue and component policies, violated issue and component policies are listed in the same email.
 Notifications must be enabled for the organization, and your personal notification settings must allow Policy notifications.

Example component policy

For example, say you create a component policy with the following rule:

Table 2. Example component policy
Rule Component properties Actions
Rule one Components with Permissive, AGPL, or Unknown licenses with a Security Risk of Critical or High. Send Notification

In tests subject to this example component policy:

  • An email notification is sent to Organization Admins when critical or high-risk components with permissive, AGPL, or unknown licenses are detected in a test.

View a component policy's details

  1. Go to Policies and open the Component Policies tab.
  2. Click the options icon at the end of the policy's row and select View.


Create a component policy

Tip: Instead of creating a new component policy, you can use a preexisting policy as a starting point (and adjust the policy as you wish). Click the options icon at the end of a policy's row and select Duplicate.
  1. Go to Policies and open the Component Policies tab.
  2. Click + Add Policy. The Add Component Policy screen appears.


  3. Enter a Policy Name (required) and Short Description (optional).
    Note: Policy names are limited to 255 characters. Policy descriptions are limited to 512 characters.
  4. (Optional) Set up the policy's rules:
    1. Under Add Rule, select Add More.
    2. Select issue properties that trigger notifications with the dropdown in the If... column:
      • SBOM: Select Included, Excluded or both.
      • License Family: Select one or more of Permissive, Reciprocal, AGPL, Restricted Third Party Proprietary, Unknown, or Weak Reciprocal.
      • Match Type: Select Direct Dependency, Transitive Dependency or both.
      • Security Risk: Select one or more of Critical, High, Medium, or Low.
      • License: Select one or more licenses.
        Note: This field accepts partial matches and is case-sensitive. After you enter a license name, select licenses with the checkboxes. Up to 20 licenses appear at a time.
      • Component: Find a specific component by name (for example, Apache Log4j 1.2.17).
        Note: This field is limited to 100 characters, does not accept fuzzy or partial matches, and only allows a single component.
      • Match Score: Set a numerical range for component match scores. Separate entries with commas (5-10, <=70).
        Note: Precise match scores only appear for components identified in signature analysis tests; the match score for a component identified in a package manager test will always be 100%. This field is limited to 100 characters.
    3. Select Send notification using the dropdown in the then... column.
    4. To add additional rules to the policy, repeat these steps.
      Note: You can add up to five rules to each component policy. You can deactivate rules with the slider in the Status column. Dropdown menus in the If... and then... cannot be empty.
  5. (Optional) Assign the component policy to applications and/or projects.
    Note: Up to five component policies can be assigned to a project or branch.
  6. Click Save.

Modify a component policy

  1. Go to Policies and open the Component Policies tab.
  2. Click the options icon at the end of the policy's row and select Edit.
  3. Modify the policy, as required.
  4. Select Save.

Change your organization's default component policy

  1. Go to Policies and open the Component Policies tab.
  2. Click the options icon at the end of the policy's row and select Set as default.
    A confirmation appears.
  3. Click OK to change the default policy.
    Important: Changing your organization's default component policy won't change the policies assigned to your existing projects.

Delete a component policy

  1. Go to Policies and open the Component Policies tab.
  2. Click the options icon at the end of the policy's row and select Delete.
    A confirmation appears.
  3. Click OK to delete the policy.
    CAUTION: Policies you delete cannot be recovered. Each component policy can be assigned to multiple projects and branches.