> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cases-and-issues/customize-cases-and-issues/set-up-case-scoring.md).

# Set up case scoring

Configure how Cortex Cloud calculates case scores.

To set up case scoring you need to define scoring rules.

## **Enable and define scoring rules**

1. Select Cases & Issues → Case Configuration → **Case Scoring** → **Scoring Rules** and enable **User Scoring Rules**.

   The **Scoring Rules** table displays the user-defined rules and sub-rules.
2. Click **Add Scoring Rule**.
3. In the **Create New Scoring Rule** dialog, define the rule criteria:

   1. Under **Rule Name**, enter a unique name for your rule.
   2. Under **Score**, define the score that Cortex Cloud should apply to issues that matching the rule criteria.
   3. Under **Base Rule**, select whether to create a top-level rule (labeled **Root**) or a sub-rule (labeled ***Rule Name (ID:#)***). By default, rules are defined at the root level.
   4. Select or deselect **Apply score only to first issue of case**.

      By selecting this option you choose to apply the score only to the first issue that matches the defined rule. Subsequent issues of the same case will not receive a score from this rule. By default, a score is applied only to the first issue that matches the defined rule and sub-rule.
   5. In the issue table, use the filters to define the attributes you want to include in the rule match criteria. For example, you can select issues with High severity, issues by category, or issues associated with certain assets or asset providers.

      <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Tip</h3><p>Right-click an issue field to add it as match criteria.</p></div>

   **Example**:

   With this rule, Cortex Cloud assigns a score of 30 to any XDR BIOC issues with a severity level of Critical:

   * Score = 30
   * Base Rule = Root
   * Filters:

     `Issue Source=XDR BIOC AND Severity=Critical`
4. Click **Create**.

   You are automatically redirected to the **Scoring Rules** table.
5. In the **Scoring Rules** table, click **Save** to save your scoring rule.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>For scoped users, a small lock icon indicates that you don't have permissions to edit a rule.</p></div>

## **Revise existing scoring rules**

In the Scoring Rules table, take the following actions to review your rules and sub-rules:

* Use the arrows to rearrange rule priorities. Make sure to click **Save** after any changes.
* Select one or more rules and right-click to see the available actions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cases-and-issues/customize-cases-and-issues/set-up-case-scoring.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.