> For the complete documentation index, see [llms.txt](https://docs.arnica.io/arnica-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings.md).

# Code Risk Policy Settings

## Overview

Arnica's policies unlock the power of real-time code risk scanning and ChatOps utilization as part of the developers' day to day work. This section will highlight the different capabilities of the policy, guide you on setting up the policies, and provide insights into the most common policies used by Arnica's customers.

## Policy structure

All policies can be configured in the [Policies page](https://app.arnica.io/#/admin/policy-v2). These policies are comprised of general configurations and event-driven behavior.

The [Global policy](https://docs.arnica.io/arnica-documentation/platform-operations/global-policy-conditions.md) rules are applied before the rules on this page: a finding that matches none of them never reaches these rules.

<figure><img src="https://4035514934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMxc1Ek3qoIZi5t2Sx7do%2Fuploads%2Fgit-blob-22cd9d987f51f56b3dd9ecc8034976c3ce124e64%2Fcode-risk-policy-overview-2026-03.webp?alt=media" alt=""><figcaption><p>Code Risk policy section in the Policies page</p></figcaption></figure>

### Configurations

The configurations are the advanced settings that each customer can tweak across the tenant.

#### General

This section contains the settings that are applicable for all code risks:

1. **Custom instant message footer**: add a Markdown-enabled footer to ChatOps messages sent via Slack or Microsoft Teams.
2. **Custom pull request (PR) comment footer**: add a Markdown-enabled footer to PR comments posted by Arnica.

<figure><img src="https://4035514934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMxc1Ek3qoIZi5t2Sx7do%2Fuploads%2Fgit-blob-fc1ec67ba0c92adb3e6fffa73a5bb9f1bfc8d14a%2Fcode-risk-policy-general-config-2026-03.webp?alt=media" alt=""><figcaption><p>General configuration section in the Code Risk policy</p></figcaption></figure>

#### Static Application Security Testing (SAST)

This section allows customers to configure [custom SAST rules](https://docs.arnica.io/arnica-documentation/code-risks/static-application-security-testing-sast/custom-sast-rules.md) and enable or disable default SAST detections.

#### Licenses

Arnica automatically classifies licenses based on [Google's open source guidance](https://opensource.google/documentation/reference/thirdparty/licenses#types). This policy configuration enables operators to [override license classifications](https://docs.arnica.io/arnica-documentation/code-risks/3rd-party-package-licenses.md#override-forbidden-and-approved-licenses) and their associated risk levels.

#### Software Composition Analysis (SCA)

This section includes package risk settings for SCA, including whether to include pre-release package versions (alpha, beta, rc, etc.).

#### Dismissals

The dismissals configuration controls whether dismissals always require operator review. Tenant-wide dismissal behavior — including review enforcement, the `No Capacity` dismissal status, and the [Snooze](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/dismissal-settings.md) workflow — is managed from the [Dismissal Settings](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/dismissal-settings.md) tab.

#### AI SAST Execution Conditions

This section controls where AI SAST agents run: **On Push**, **On Pull Request**, and **On Routine Scan**. You can also configure the global prompt via the AI Configuration page and product-level prompts via the Products page. See [AI SAST](https://docs.arnica.io/arnica-documentation/code-risks/static-application-security-testing-sast/ai-sast.md).

### Rules

Arnica's rules are executed when **triggers** are configured, such as git push or pull request creation. The identification of the code risks is scoped with specific **conditions**, such as a specific code repository with at least high severity vulnerability. When these conditions are met, Arnica executes the selected **actions**, such as sending an instant message to the code pusher.

{% hint style="info" %}
By default, Arnica's policy uses a git push trigger with a condition that is always "true" and has no associated actions.
{% endhint %}

#### Triggers

The supported triggers are:

1. **Code risk detected on push**: every time a developer pushes code with 1 or more commits, they are analyzed in real-time.
2. **Code risk detected on pull request**: every time a pull request is created, the HEAD of the source branch is scanned. In addition, if the source branch is updated with new commits, Arnica analyzes the new HEAD of the source branch.
3. **Code risk resolved on pull request**: triggered when previously fixed code risks are included in a pull request.
4. **Code risk detected during a routine scan**: triggered when a routine scan identifies a code risk.
5. **Code risk detected from a container scan**: triggered when a container scan identifies a code risk.
6. **User created issue**: triggered when a user manually creates an issue from a finding (see [Jira integration mapping](https://docs.arnica.io/arnica-documentation/getting-started/ticket-management/creating-issues/automated-issue-creation.md#product-mapped-configuration)).
7. **User dismissed finding via ChatOps**: triggered when a user clicks `Dismiss` in ChatOps (Slack or Microsoft Teams), so operators can respond quickly based on policy conditions.
8. **Code risk detected during an API initiated SBOM scan**: triggered when an API-initiated SBOM scan identifies a code risk.
9. **Pull request created**: triggered when a pull request is created.

<figure><img src="https://4035514934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMxc1Ek3qoIZi5t2Sx7do%2Fuploads%2Fgit-blob-a0040ea4ec3f5122e23a4a361bf4157f4c587a21%2Fcode-risk-policy-trigger-options-2026-03.webp?alt=media" alt=""><figcaption><p>Trigger picker in the current Code Risk policy UI</p></figcaption></figure>

#### Conditions

The supported conditions are:

1. **Always (TRUE)**: This condition will always evaluate to true. A good use of this policy is to see all real-time results as developers push code.
2. **Any of (OR)**: a logical operator that is set to true if any of the sub-conditions (any of the conditions on this list) are matched in the context of the executed trigger.
3. **All of (AND)**: a logical operator that is set to true if all of the sub-conditions (any of the conditions on this list) are matched in the context of the executed trigger.
4. **Reverse (NOT)**: this condition allows to negate a specific sub-condition (consider false if the sub-condition is true and vice versa).
5. **Source Code Management**: if multiple source code management platforms are integrated into Arnica, such as Github and Azure DevOps, a specific platform can be selected.
6. **Organization**: if multiple organizations or workspaces are integrated, this condition can select a specific organization.
7. **Project**: the condition allows to select a specific project in the organization. Note: this only applies to SCMs with project hierarchy. If the SCM does not support a project hierarchy, the condition will always return `true`.
8. **Repository**: the condition allows to select a specific source code repository.
9. **Branch**: the condition allows to select the impacted branch (regular expression) of the triggered event. In case of a pull request trigger, the branch is matched against the source branch (where the vulnerability is introduced).
10. **Product**: the condition allows to select a specific product as defined in [Product ownership](https://docs.arnica.io/arnica-documentation/inventory/identities.md#security-championship-product-ownership-and-memberships).
11. **File Path:** the condition allows to specify a regular expression of the path. It is useful when different actions should be taken based on different paths in the same repository, such as in mono-repos.
12. **Severity**: selects the minimum risk severity of a finding. For example, if all risks with a medium severity and above should be matched against this condition, select "Medium" only.
13. **Finding Type**: the supported finding types are [IaC](https://docs.arnica.io/arnica-documentation/code-risks/infrastructure-as-code-security-iac.md), [License](https://docs.arnica.io/arnica-documentation/code-risks/3rd-party-package-licenses.md), [Reputation](https://docs.arnica.io/arnica-documentation/code-risks/3rd-party-package-reputation.md), [SAST](https://docs.arnica.io/arnica-documentation/code-risks/static-application-security-testing-sast.md) and [SCA](https://docs.arnica.io/arnica-documentation/code-risks/software-composition-analysis-sca.md).
14. **Exceeded SLA** (pull request triggers only): Arnica starts the SLA clock when code risks are detected on an [SLA branch](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/sla-branches.md), either after code reaches that branch or during [scheduled jobs](https://docs.arnica.io/arnica-documentation/platform-operations/scheduled-jobs.md). The condition matches findings whose **SLA Start** is older than the configured number of days.
15. **SCA Finding Has a Fix**: SCA findings may not have a fix, mainly due to not having a fixed version available, but also when the used package is internal. This condition matches only SCA findings with a fix available.
16. **Repository Business Importance**: filters findings by the selected repository business-importance level.
17. **Topic**: filters findings by the selected repository/topic metadata.
18. **Product Business Importance**: filters findings by the selected product business-importance level.
19. **Has product matching labels**: matches findings in products that have the selected labels.
20. **Git Blame Property**: matches findings by git blame metadata using provided expressions.
21. **SAST Property**: matches SAST findings by a property of the rule or result that produced them, such as **Category**, **CWE**, or **Class**, using one or more regular expressions. This replaces the former **SAST Rule ID** condition, which is now the **Rule ID** property. Available on Enterprise plans. See [SAST Property](#sast-property).
22. **Is AI SAST**: matches findings detected by AI SAST.
23. **Package Name and Version**: matches findings by package name/version expressions.
24. **Package Manager**: matches findings by selected package manager.
25. **Package Release Date**: matches findings by package release date range.
26. **Latest Version Release Date**: matches findings by latest package release date range.
27. **CVSS Score**: matches findings by CVSS score thresholds/ranges.
28. **EPSS Score**: matches findings by EPSS score thresholds/ranges.
29. **Has KEV**: matches findings based on Known Exploited Vulnerability (KEV) status.

<figure><img src="https://4035514934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMxc1Ek3qoIZi5t2Sx7do%2Fuploads%2Fgit-blob-745ea6045d374ee7c744fb59017ddd561891f049%2Fcode-risk-policy-condition-options-2026-03.webp?alt=media" alt=""><figcaption><p>Condition picker showing asset, product, finding, SAST, package, and SCA options</p></figcaption></figure>

#### Conditions that don't apply to a finding

Some conditions only make sense for certain finding types: **CVSS Score** applies only to SCA findings, and **SAST Property** only to SAST findings. When a condition doesn't apply to the finding being evaluated, it is skipped:

* On its own, a skipped condition never runs the rule's actions, and Arnica moves on to the next rule.
* Inside **All of (AND)** or **Any of (OR)**, a skipped condition is ignored, and the other conditions in the group decide. If every condition in the group is skipped, the whole group is skipped.
* **Reverse (NOT)** of a skipped condition is also skipped. It does not become a match.

{% hint style="warning" %}
A rule like **All of** \[**Severity** High, **SAST Property** Category `security`] also fires on High and Critical SCA, IaC, License, and Reputation findings. The SAST Property check is skipped for those, so Severity alone decides. To keep a rule to the findings a condition was written for, add the matching **Finding Type** to the same **All of** group. For **AI SAST Confidence**, add **Is AI SAST** instead, because **Finding Type** SAST also lets rule-based SAST findings through, and AI SAST Confidence is skipped for them.
{% endhint %}

<table><thead><tr><th width="240">Applies only to</th><th>Conditions</th></tr></thead><tbody><tr><td>SAST findings</td><td>SAST Property, Is AI SAST</td></tr><tr><td>AI SAST findings</td><td>AI SAST Confidence</td></tr><tr><td>SCA findings</td><td>CVSS Score, EPSS Score, Has KEV, SCA Finding Has a Fix, and on the Finding Changed trigger: CVE count changed, EPSS score changed, KEV status changed, Fix status changed</td></tr><tr><td>SCA, License, and Reputation findings</td><td>Package Manager, Package Name and Version, Package Release Date, Latest Version Release Date</td></tr><tr><td>License findings</td><td>License Classification, License - Original, License - Standardized SPDX</td></tr><tr><td>Reputation findings</td><td>OpenSSF Score</td></tr><tr><td>IaC findings</td><td>IaC property</td></tr></tbody></table>

Some conditions are also skipped for findings they do apply to: **File Path** when the finding has no file path or the expression is invalid, and **Package Release Date** and **Latest Version Release Date** when Arnica doesn't know the package's release date.

#### SAST Property

**SAST Property** matches a SAST finding when a property you choose matches any of the regular expressions you provide. It isn't offered on the **Code risk detected from a container scan** or **Code risk detected during an API initiated SBOM scan** triggers.

Most properties come from the `metadata` section of the SAST rule that produced the finding. They follow Opengrep's rule conventions, and not every rule sets every property. To make a [custom SAST rule](https://docs.arnica.io/arnica-documentation/code-risks/static-application-security-testing-sast/custom-sast-rules.md) easy to target, set them in the rule's `metadata` section.

<table><thead><tr><th width="200">Property</th><th>What it matches</th><th width="200">On AI SAST findings</th></tr></thead><tbody><tr><td><strong>Category</strong></td><td>The broad concern the rule addresses. Opengrep's conventions use values such as <code>security</code>, <code>correctness</code>, and <code>performance</code>.</td><td>Always <code>security</code></td></tr><tr><td><strong>Sub Category</strong></td><td>A narrower designation within the category. Within <code>security</code>, the common values are <code>vuln</code> and <code>audit</code>, and some rules use others, such as <code>guardrail</code>. Many rules set none.</td><td>Not set</td></tr><tr><td><strong>Class</strong></td><td>The vulnerability classes the rule lists. The <strong>Vulnerability Class</strong> column on the Code Risks page shows one of them, or <code>Other</code> when the rule lists none. In that case <strong>Class</strong> is not set, so it matches nothing, not even <code>Other</code>.</td><td>Set</td></tr><tr><td><strong>CWE</strong></td><td>The CWE entries the rule maps to, written <code>CWE-89: ...</code> or <code>CWE 89: ...</code></td><td>Set, written <code>CWE 89: ...</code></td></tr><tr><td><strong>OWASP</strong></td><td>The OWASP categories the rule maps to, such as <code>A03:2021 - Injection</code>. Codes are not written the same way in every rule.</td><td>Set, as a name only, such as <code>Injection</code></td></tr><tr><td><strong>Confidence</strong></td><td>The rule author's confidence that a match is a real issue, such as <code>HIGH</code>, <code>MEDIUM</code>, or <code>LOW</code></td><td>Not set. Use <strong>AI SAST Confidence</strong></td></tr><tr><td><strong>Technology</strong></td><td>Languages or frameworks the rule targets</td><td>Not set</td></tr><tr><td><strong>References</strong></td><td>Links the rule lists for further reading</td><td>Not set</td></tr><tr><td><strong>Source</strong></td><td>A link to the rule's source</td><td>Not set</td></tr><tr><td><strong>Origin</strong>, <strong>Rule Version ID</strong></td><td>The rule's registry origin and version</td><td>Not set</td></tr><tr><td><strong>Rule ID</strong></td><td>The rule's identifier</td><td>Arnica-generated</td></tr><tr><td><strong>Description</strong></td><td>The finding's description as shown in Arnica. For many default rules this is Arnica's own description, not the rule's original message.</td><td>Set, ending with an AI Confidence line</td></tr><tr><td><strong>Code</strong></td><td>The matched source lines</td><td>Set</td></tr><tr><td><strong>Fingerprint</strong></td><td>The finding's fingerprint</td><td>Set</td></tr></tbody></table>

**How matching works**

* Matching is always case-insensitive, and an expression matches anywhere in the value, so `vuln` also matches `Vuln` and `vulnerable`.
* The condition matches if any one expression matches.
* To require an exact value of a single-value property such as **Category**, anchor the expression, as in `^security$`.
* Properties that can hold several values, such as **Sub Category**, **Class**, **CWE**, **OWASP**, **Technology**, and **References**, are joined into one string with commas and no spaces, such as `CWE-89: ...,CWE-79: ...`, and each expression is tested against that whole string. An expression that matches one value matches the finding. `^` and `$` mark the start and end of the whole list, so to match one value exactly, use `(^|,)vuln(,|$)`.
* If the rule doesn't set the chosen property, the finding does not match, so **Reverse (NOT)** of the condition does match. Unlike a skipped condition, a missing property blocks an **All of** group.
* The policy editor flags expressions that are invalid or too complex to evaluate safely. A condition with no expressions is skipped for any finding that has the chosen property, so it doesn't narrow the rule at all. A newly added condition can be saved before you type in its expression box, so check that it isn't empty.

{% hint style="info" %}
AI SAST findings are evaluated too. Their **Category** is always `security` and they have no **Sub Category**, so a Sub Category condition never matches them, and **Reverse (NOT)** of one always does. Rule-based findings write CWEs as `CWE-89: ...` or `CWE 89: ...`, and AI SAST uses `CWE 89: ...`, so use `CWE[- ]89\b` to match both. For OWASP, match on the category name, such as `Injection`, which works for both. To include or exclude AI SAST findings, combine this condition with **Is AI SAST**.
{% endhint %}

**Examples**

To alert only on rules marked as vulnerabilities. This also leaves out AI SAST findings, because they have no Sub Category:

* **All of (AND)**
  * **Finding Type**: SAST
  * **SAST Property**: Sub Category matches `vuln`

To alert on SQL injection found by rule-based SAST, but not by AI SAST:

* **All of (AND)**
  * **Finding Type**: SAST
  * **SAST Property**: CWE matches `CWE[- ]89\b`
  * **Reverse (NOT)**: Is AI SAST

#### Actions

Actions are unique per trigger and can be executed only when the conditions within the policy rule are met.

For a **git push trigger**, Arnica can send instant messages to one or more of the following:

1. **Recipient(s) lookup**: Arnica can lookup users based on the trigger context. For push-based rules, common recipient lookups include **Code Pusher** and **Code Author**. Arnica can also select remediation owners as defined in [Product ownership](https://docs.arnica.io/arnica-documentation/inventory/identities.md#security-championship-product-ownership-and-memberships).
2. **Specific recipient**: Arnica can send a direct message to a user or channel.

<figure><img src="https://4035514934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMxc1Ek3qoIZi5t2Sx7do%2Fuploads%2Fgit-blob-c8f8e760e26d4c0a2a3a8e12fbed515e35f946f6%2Fcode-risk-policy-action-recipients-2026-03.webp?alt=media" alt=""><figcaption><p>Example action recipients in a push-based Code Risk rule</p></figcaption></figure>

{% hint style="info" %}
If the instant messaging channel doesn't appear in the specific recipients list, invite the bot named `arnica` to your channel on Slack or team on Microsoft Teams.
{% endhint %}

An example of an instant message notification can be found in the [Developer Feedback on Push page](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/developer-feedback-on-push.md).

When a **pull request trigger** is configured in the policy, Arnica can do the following:

1. **Send an instant message**, similarly to the description in the git push trigger above.
2. **Comment on pull request**: Arnica can add a comment inline with the code (similarly to comments in a code review) or as separate comments in the PR. The location of the comment depends on the conditions - see the different scenarios in [0 New High Severity Vulnerabilities](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/0-new-high-severity-vulnerabilities.md) and [Enforce Remediation SLA](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/enforce-remediation-sla.md) pages. Additionally, Arnica can mention specific members in the relevant messages - select the `mention a user or a group` checkbox and add the relevant members similarly to the description in the git push trigger above.
3. **Fail status check**: Arnica creates a full report of all outstanding findings on every status check execution. If there are no outstanding findings, the status check will succeed. Otherwise, Arnica will fail the status check.

{% hint style="info" %}
To rescan a pull request without pushing an empty commit, post `[a] rerun` as a standalone PR comment. See [Rerun Arnica Status Check](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/rerun-arnica-status-check.md).
{% endhint %}

**Product-mapped actions at enterprise scale**

`Product Mapped` actions let one policy dynamically route workflows by product/team ownership instead of hard-coding one static destination.

* **`Create Issues (Product Mapped)`**: routes findings to team-specific ticketing configurations (project, required fields, and workflow mapping) based on the matched product.
* **`Send Instant Message (Product Mapped)`**: routes notifications to the right people/channels for each product, so the correct team is engaged automatically.

Example:

* **Team X** findings can be routed to Jira project `ABC` with Team X-specific fields/workflow.
* **Team Y** findings can be routed to Jira project `DEF` with different fields/workflow.
* The same single policy can also notify different people/channels dynamically per product mapping.

This is a powerful way to scale governance across the enterprise while keeping policy management centralized.

<figure><img src="https://4035514934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMxc1Ek3qoIZi5t2Sx7do%2Fuploads%2Fgit-blob-563325093a2860dadbc4a6303d13db33a71e657c%2Fcode-risk-policy-actions-push-2026-03.webp?alt=media" alt=""><figcaption><p>Action picker for a push-triggered rule</p></figcaption></figure>

`Comment on Pull Request` action fields include:

* `Mention a user or a group`
* `Dismissals require review`
* `Include AI-powered code suggestion`

<figure><img src="https://4035514934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMxc1Ek3qoIZi5t2Sx7do%2Fuploads%2Fgit-blob-7b6a9d944cdfef2cdf3e3ddf64cb16dd188cc363%2Fcode-risk-policy-action-fields-pr-comment-2026-03.webp?alt=media" alt=""><figcaption><p>PR comment action fields in a pull request trigger rule</p></figcaption></figure>

{% hint style="info" %}
PR comments include a **View in Arnica** link to the finding when one is available. See [Code Risk Magic Links](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-magic-links.md#magic-links-in-pull-request-feedback) for how that link is chosen.
{% endhint %}

{% hint style="info" %}
Arnica doesn't block pull request merges by default (a.k.a. "soft" security gate). To enforce the block (a.k.a. "hard" security gate) follow the "view unenforced branches" link in the policy and then select the relevant repositories and branches.
{% endhint %}

More information about the **Create Issue** action can be found in the [Jira Integration page](https://docs.arnica.io/arnica-documentation/getting-started/ticket-management/jira-integration.md).

### Rules execution order

Customers are encouraged to define multiple rules. The rules in the policy are executed in order - if there is a match in the trigger and conditions, Arnica will execute the action and stop processing other rules.

{% hint style="info" %}
To better illustrate how rules are executed, consider the following example. Assume the following rule definitions:

* Rule #1: Notify developers on Medium severity in the product "GitGoat"
  * Trigger: `git push`
  * Conditions: `All of` (`severity` = `medium`, `project` = `GitGoat`)
  * Actions: `send instant message` to a `recipient lookup` of the `code pusher`
* Rule #2: Comment on pull request and fails status check if the developer introduced new Medium severity security vulnerabilities in a feature branch in the project "GitGoat", and tag the relevant remediation owners
  * Trigger: `pull request`
  * Conditions: `All of` (`severity` = `medium`, `project` = `GitGoat`)
  * Actions: `comment on pull request` and `mention a user or a group` with the `mention lookup` of `product owners` and `fail status check`.
* Rule #3: Notify the security team on Critical severity vulnerabilities in pull requests
  * Trigger: `pull request`
  * Conditions: `severity` = `critical`
  * Actions: `send instant message` to a `specific recipient` with the name `#security-channel`.

The following scenarios will be handled by the specific rule numbers above:

* A High severity vulnerability is pushed to a feature branch in the product GitGoat -> Rule #1.
* A High severity vulnerability is pushed to a feature branch in any product other than GitGoat -> No match.
* A new Medium severity vulnerability is identified in the source branch in the product "GitGoat" -> Rule #2.
* A new High severity vulnerability is identified in the source branch in any product other than "GitGoat" -> No match.
* A new Critical severity vulnerability is identified in the source branch in the product "GitGoat" -> Rule #2 (it matches Rule #3 as well, but the processing stops beforehand).
* A new Critical severity vulnerability is identified in the source branch in a product other than "GitGoat" -> Rule #3.
  {% endhint %}

### Troubleshooting policy behavior

#### Finding matched a policy but expected action did not run

Arnica executes only the first matching rule. If a finding does not create the expected ticket, PR comment, or ChatOps message, verify there is no broader rule above it that matches first.

#### `Create Issue` action is unavailable

Available actions are trigger-dependent. If you do not see `Create Issue`, switch to a trigger that supports issue creation and then re-open the action selector.

#### Stock policies are too broad

If a built-in policy does not match your workflow, clone the policy, adjust the clone by adding additional conditions to address severity, repository scope, etc, then disable or remove the original.

#### Dismissal flow is not behaving as expected

If developers can no longer directly dismiss findings, verify whether **Dismissals always require review** is enabled in the policy configuration.

#### Status or severity changes are queued instead of applied

If a Collaborator, Collaborator-Product, or Maintainer-Product user reports that a status or severity change moved the finding to **Pending Review** rather than taking effect, check whether **Require Review for Status and Severity changes made from Arnica UI** is enabled under [Dismissal Settings and Snooze](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/dismissal-settings.md). Severity requests are approved from the finding's **Timeline** tab — see [Manual Severity Changes](https://docs.arnica.io/arnica-documentation/code-risks/manual-severity-changes.md#requiring-review-for-severity-changes).

## Policy considerations

### Detect on git push, then on pull requests

Developers open pull requests when a bulk of functionality is ready for review. Many commits tend to be pushed before the pull request is opened, which means that the code author may no longer have the context of the specific changes in the feature branch, or it may be too late to change. Therefore, it is worth considering sending an [instant message to the author if a new vulnerability is introduced](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/developer-feedback-on-push.md). If there is no response on the event, flag the remaining issues in the pull request in comments and status checks.

### Refine Conditions and Actions

Certain products may have a higher business importance than others. Arnica's policy supports granular conditions to support the different needs for each product. For example, a product with high business importance may implement [0 new high severity vulnerabilities](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/0-new-high-severity-vulnerabilities.md) policy and [enforce remediation SLAs](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/enforce-remediation-sla.md), while less important products may have less strict policy.

Additional example of a use case we observed is with the legal team, which might be interested in reviewing risky 3rd party package licenses. Since legal teams typically don't interact with the source code management platform, narrow down the conditions to the specific findings types and add actions to send instant messages to the legal team.

### Cleanup code risks exceeded SLA before enabling condition

Arnica can [comment on pull requests with the outstanding code risks that exceeded SLA](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/enforce-remediation-sla.md), alongside other conditions. In some cases, the condition may catch too wide set of findings, which may cause unnecessary confusion by the pull request reviewers. Therefore, it is recommended to ensure that all issues on [SLA branches](https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/sla-branches.md) are reviewed before applying such policy.

## Common use cases

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Provide developer feedback on push</td><td><a href="https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/developer-feedback-on-push.md">Developer Feedback On Push</a></td></tr><tr><td>Dismissal settings and Snooze</td><td><a href="https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/dismissal-settings.md">Dismissal Settings and Snooze</a></td></tr><tr><td>Require review before dismissal</td><td><a href="https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/require-review-before-dismissal.md">Require Review Before Dismissal</a></td></tr><tr><td>Rerun Arnica status check</td><td><a href="https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/rerun-arnica-status-check.md">Rerun Arnica Status Check</a></td></tr><tr><td>0 new high severity vulnerabilities</td><td><a href="https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/0-new-high-severity-vulnerabilities.md">0 New High Severity Vulnerabilities</a></td></tr><tr><td>Enforce remediation SLA</td><td><a href="https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/enforce-remediation-sla.md">Enforce Remediation SLA</a></td></tr><tr><td>SLA branches</td><td><a href="https://docs.arnica.io/arnica-documentation/code-risks/code-risk-policy-settings/sla-branches.md">SLA Branches</a></td></tr></tbody></table>
